Writing a Business Central cutover plan for the switch from your old system
A Business Central cutover plan is the ordered list of tasks that moves your company from the old system to the new one. It says what stops, what is loaded, who checks it and when trading restarts. You write it well before launch and rehearse it. This guide explains what belongs in the plan, the usual sequence and how to decide whether to proceed.
Last updated
What a Business Central cutover plan contains
The plan is a task list with an owner and a sequence for every line. It differs from a go-live checklist, which confirms readiness. The cutover plan is the run sheet for the switch itself. It covers closing the old system, loading the final data, checking it and opening the new system to users.
Each task names one person, the task it depends on and how completion is confirmed. Tasks belong to the client as often as to the consultant. Counting stock, approving balances and telling customers about new remittance details are business jobs. One shared sheet that everyone can see works better than anything elaborate.
Talk through your cutover →
- ✓Task, owner and sequence
- ✓Dependencies between tasks
- ✓Evidence that a task is done
- ✓Contact list for the period
- ✓Decision points
Freezing the old system and preparing the ground
Choose a cutover date that finance can live with. A period end keeps opening balances clean. Avoiding your busiest trading stretch keeps pressure down. Then agree the freeze. This is the point after which nothing new is entered in the old system, so the figures you extract do not move under you.
Before the freeze, reduce what has to be moved. For example, ship and invoice what you can. Receive and match what has arrived. Apply cash, reconcile bank accounts and post the final payroll journal. Every open document closed in the old system is one fewer to load and check in Business Central.
Ask about freeze timing →- ✓Cutover date agreed
- ✓Freeze point announced
- ✓Open orders reduced
- ✓Bank accounts reconciled
- ✓Stock count scheduled
The loading sequence in a Business Central cutover plan
Master data goes first, because transactions depend on it. That means customers, vendors, items, the chart of accounts and their posting groups, usually through configuration packages. Most of this loads ahead of time. Only records created since the last trial migration need a top-up. Open sales and purchase orders follow.
Balances come last. Open customer and vendor entries, bank balances, fixed assets and inventory quantities with their cost are all posted. So is the general ledger trial balance. You post them through journals dated at the cutover point. Balancing accounts used during loading should net to zero when everything is in. Our opening balances guide covers the mechanics.
Get help with loads →- ✓Master data top-up
- ✓Open sales and purchase orders
- ✓Open receivables and payables
- ✓Inventory quantity and value
- ✓Trial balance last
Reconciliation checks before users are let in
No one should start working until the numbers agree. Compare the aged receivables and aged payables totals with the final reports from the old system. Do the same for the inventory valuation and the trial balance. Explain and fix any difference now. However, differences become much harder to find once new postings begin.
Then run a smoke test in production. Post one sales invoice, one purchase invoice and one payment. Also print a document. Confirm that integrations, the job queue and each user's permissions work. Record who signed off each figure. That record is what auditors and your own finance team will ask for later.
Have us check balances →- ✓Aged receivables total
- ✓Aged payables total
- ✓Inventory valuation
- ✓Trial balance by account
- ✓Bank balances to statements
Rehearsing your Business Central cutover plan and the fallback
Think of a rehearsal as the full plan run against a sandbox with a fresh data extract. It shows how long each load really takes. It also shows which tasks were forgotten, and which depend on a person who is on leave. Plans that have been rehearsed tend to be dull on the day. That is the goal.
Decide the fallback in advance. Name who makes the go or no-go call. List the conditions that would stop the launch, such as balances that cannot be reconciled. Describe what returning to the old system would involve. After launch, keep the old system available read-only for lookups. We can help write and rehearse the plan.
Rehearse it with us →- ✓Timings for each task
- ✓Missing steps found
- ✓Go or no-go criteria
- ✓Named decision maker
- ✓Old system kept read-only
Business Central cutover plan questions
How is a cutover plan different from a go-live checklist?
Think of the go-live checklist as the readiness check. That means testing signed off, users trained and permissions set. The Business Central cutover plan is different. It is the ordered task list for the switch itself, from freezing the old system to opening the new one. So you need both, and you use them one after the other.
When is the best time to cut over?
The usual choice is a period end, because opening balances then match a closed set of books. Within that, pick a quieter trading period. Pick a point when key finance and warehouse staff are available, too. So the date is a mix of accounting and people. Ask your finance lead to propose two or three options.
Do we need to migrate transaction history?
Usually not. Most companies bring open documents and balances, plus summary ledger figures for comparison reporting. They keep the old system or an export for detailed history. Loading full history adds work and risk for limited benefit. A short list of the reports you need from history decides what you must keep.
Should we run the old and new systems in parallel?
Running both in parallel for long doubles the workload and rarely finishes cleanly. A rehearsed cutover with reconciled balances and a short smoke test gives more confidence. Keeping the old system read-only covers the need to look things up. So most teams in a Business Central cutover plan choose rehearsal over a parallel run.
Who should own the cutover plan?
One named person on the client side, normally the project lead, owns it with the consultant's support. Individual tasks have their own owners. But a single person tracks progress during the switch and calls the go or no-go decision. Name that person early, and make sure they are free on the cutover days.
Book a discovery call
Let's talk through your move to Business Central.
A focused call with a senior consultant. We learn how your business runs today, give you an honest view on whether Business Central fits, and outline scope and next steps before you commit to anything.
What happens after you send the form