Microsoft DynamicsFree checklistPDF, Excel, Word exportMicrosoft Dynamics 365 Finance and Supply Chain

D365 Finance and Supply Chain Go-Live Cutover Readiness Checklist

Go-live readiness for D365 Finance and Supply Chain is mostly about the unglamorous items: reconciled data, tested security, working integrations and trained users. This checklist gives a common baseline you can adapt to your cutover runbook.

0%

0 of 34 items complete

13 critical items still open - these are the highest-risk gaps.

Download checklist:

Data and finance

Environment and technical

Security and compliance

Integrations

People and support

Every critical item should be complete before the go decision. Treat any open critical item as a risk that needs a named owner, a mitigation and an explicit acceptance by the steering group.

Get help with cutover testing

We can help with reconciliation queries and interface testing support ahead of your go-live.

Optional. The tool and every export work without this. No spam.

How to use the checklist

Assign each item to an owner and a due date in your project plan, then tick items as evidence is available. Treat tick marks as backed by evidence such as a reconciliation file, a test result or a sign-off email. Review the checklist in the weekly steering meeting from about six weeks before go-live, and use the critical items as the core of your go and no-go decision.

  • Owners should be named people, not teams.
  • Attach evidence for each completed critical item.
  • Re-run the review after each dress rehearsal.

What the groups cover

Data and finance protects the opening position of the business. Environment and technical focuses on the production deployment and operations. Security and compliance confirms that users can do their job and only their job. Integrations covers every interface to carriers, banks, EDI partners, MES and reporting. People and support looks at training, acceptance and the support model for the first weeks. Each group has items that can silently fail without anyone noticing until after go-live.

Reading your result

A project with all critical items done and a few non-critical open is typically ready, with the open items scheduled for hypercare. If two or more critical items are open in data, security or integration, consider whether a delay of a few days is cheaper than a failed start. Compare your current state against the dress rehearsal timings to confirm the cutover window is realistic.

Common mistakes

Cutover runbooks usually fail on timing and ownership, not on technology. Reconciliations take longer than the plan allows, and integrations are tested in sandbox but not against production endpoints.

  • No rehearsal of rollback decisions.
  • Security tested with admin accounts only.
  • Forgetting to switch off legacy interfaces and scheduled jobs.
  • Going live in the week of a platform update or month-end close.

Frequently Asked Questions

How many dress rehearsals should a D365 go-live have?

At least one full dress rehearsal that follows the runbook step by step, with timings and reconciliation. Many projects run two or three, especially with several legal entities, complex inventory conversion or multiple integrations.

Who makes the go or no-go decision?

The steering group, based on agreed criteria. The project manager prepares the evidence, but business owners for finance, supply chain and operations should sign off because they carry the operational risk if issues occur.

What should be in a cutover runbook?

A time-ordered list of tasks with owners, durations, dependencies, verification steps and rollback decision points. It covers legacy freeze, data extraction, loads, reconciliation, integration switch-over and user enablement.

How long should hypercare last?

Commonly two to six weeks, often extended through the first month-end close. Duration depends on project size, how many sites go live together and the quality of the training and data conversion.

If you are cutting over from another ERP and need help with data profiling, reconciliation queries or interface testing, Netray can support the planning.