Microsoft DynamicsFree checklistPDF, Excel, Word exportMicrosoft Dynamics 365 Business Central

Business Central Go-Live Readiness Checklist

Go-live is when small gaps in data, posting setup or security become real problems. This checklist covers the areas that most often cause delays or reconciliation pain in a Business Central implementation.

0%

0 of 34 items complete

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

Download checklist:

Data and opening balances

Setup and posting

Security and users

Integrations and reporting

Cutover and support

Do not go live with any critical item unchecked. Non-critical items can be planned as post go-live tasks with a named owner and date.

Independent go-live review

Optionally share your checklist result for a short written review of the risk areas.

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

How to use the checklist

Work through each group with the owner of that area: finance for balances and posting, operations for items and BOMs, IT for security and integrations. Tick an item only when there is evidence, such as a reconciliation, a test result or a sign-off. Critical items are those where a gap has financial or compliance consequences, so treat them as blockers. Export the result to share it with the steering group.

Opening balances done safely

Opening balances are normally posted with journals dated at the cutover, then reconciled to the legacy trial balance. Customer and vendor balances should be loaded as open entries so they can be applied later. Inventory should be loaded by quantity and value so the inventory account agrees with the G/L. Reconcile each subledger to its control account before release, and keep the reconciliation file as audit evidence.

  • Pick a cutover date at a period boundary
  • Reconcile subledger to G/L in the same session
  • Keep a dated copy of the legacy trial balance

Security and posting setup

Most post go-live incidents are caused by missing permissions or incomplete posting groups. Test every role with a real user, not an administrator. Create one item, customer and vendor per posting combination and run a full transaction through to the ledger. Confirm that dimensions flow as expected and that period restrictions prevent posting into closed periods.

Common mistakes

Teams often leave integration testing too late and discover mapping gaps in the final week. Another common mistake is not rehearsing the cutover, so the real run takes twice as long as planned. Skipping a rollback decision point is the third. Finally, avoid loading dirty master data on the assumption it will be cleaned later, because cleanup after posting is slow.

Frequently Asked Questions

How long before go-live should we start this checklist?

Start about eight to twelve weeks before cutover for most small and mid-size projects, and review it weekly. The data and security groups need the longest lead time, so they should be started first.

Which items are truly blockers?

Those marked critical: reconciled opening balances, tested posting setup, role-based permissions, working integrations, signed-off user acceptance testing and a rehearsed cutover. Any of these missing risks wrong financials or a stalled business on day one.

Should we run old and new systems in parallel?

Full parallel running doubles the workload and is rarely needed. A common approach is a short parallel check for one cycle of key reports, then set the legacy system read-only and keep it for reference.

Does this apply to NAV to Business Central upgrades?

Mostly yes. Upgrades add technical steps such as converting extensions and data, but security, posting setup, integrations and user acceptance still need the same discipline before users return to the system.

If you want an independent check of data quality before loading, we can profile your legacy data on-premises and list duplicates and gaps for your team to resolve.