# D365 Finance and Supply Chain Go-Live Cutover Readiness Checklist > Source: https://netray.co/tools/d365-fno-cutover-readiness-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Checklist of data, environment, integration, user and support items to confirm before a D365 Finance and Supply Chain go-live. ## Category microsoft-dynamics ## Erp Microsoft Dynamics 365 Finance and Supply Chain ## Audience - D365 F&O project manager - Cutover lead - Consultant ## Tool **Kind:** checklist **Groups:** #### Data and finance **Items:** **Text:** At least one full dress rehearsal of data load completed with timings **Critical:** true **Text:** Opening balances reconciled to legacy trial balance and subledgers **Critical:** true **Text:** Open purchase and sales orders validated by business owners **Critical:** true **Text:** On-hand inventory counted or confirmed against opening journal **Critical:** true Fiscal calendar periods open for the first posting dates Number sequences configured and continuity confirmed where required Exchange rates loaded and rate types confirmed Master data freeze date communicated and enforced #### Environment and technical **Items:** **Text:** Production environment deployed and configuration copied from the golden configuration **Critical:** true **Text:** Customizations and ISV packages deployed through the release pipeline, not manually **Critical:** true Batch jobs, recurrence and batch groups configured and tested Email, printer and document management settings verified in production Performance test run with realistic user and data volume Backup, restore and disaster recovery responsibilities documented Service update schedule agreed and update window set to avoid go-live week #### Security and compliance **Items:** **Text:** Security roles assigned to all users and tested by process owners **Critical:** true **Text:** Segregation of duties conflicts reviewed and signed off **Critical:** true Privileged and admin access limited and recorded Audit trail and database logging settings agreed with internal audit Legal entity tax registration and e-invoicing settings confirmed for each country Data retention and personal data requirements reviewed #### Integrations **Items:** **Text:** Every integration tested end to end against production endpoints **Critical:** true **Text:** Service principals, credentials and secrets rotated and stored securely **Critical:** true Error handling and retry behavior documented for each interface Throttling and API limits reviewed for expected volumes Legacy interface shutdown and switch-over steps sequenced in the runbook Monitoring and alerting configured for failed messages #### People and support **Items:** **Text:** End users trained and attendance recorded **Critical:** true **Text:** Business sign-off on user acceptance test results **Critical:** true **Text:** Go and no-go criteria agreed and decision meeting scheduled **Critical:** true Hypercare roster, escalation path and ticket process published Cutover runbook with owners, durations and rollback decision points rehearsed Process documentation and quick reference guides available to users Month-end and year-end close plan for the first period after go-live drafted **Scoring Note:** 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. ## Content **Intro:** 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. **Sections:** #### How to use the checklist **Body:** 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. **Bullets:** - 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 **Body:** 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 **Body:** 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 **Body:** 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. **Bullets:** - 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. **Cta:** If you are cutting over from another ERP and need help with data profiling, reconciliation queries or interface testing, Netray can support the planning. **Faq:** #### How many dress rehearsals should a D365 go-live have? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms d365 go live checklist, dynamics 365 cutover plan template, d365 f&o go live readiness, erp cutover checklist, d365 production readiness, d365 go live support plan, d365 cutover runbook, d365 finance go live checklist --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json