Should you go live on Business Central on January 1? How to pick a cutover date
It's November, and the plan says Business Central goes live on January 1. It's a clean date: new year, new system, no split between old and new books. Everyone agreed to it in the spring.
Now testing is behind, the payroll integration isn't finished, and your team is about to start the busiest six weeks of the year. Is January 1 still the right date? Often it isn't, and moving it is less painful than people fear.
Why January 1 is so popular
A year-start go-live has real advantages, and we're not against it:
- One system per fiscal year. Auditors and tax preparers deal with one set of books for the year.
- Simpler opening balances. You bring over a closed balance sheet instead of a mid-year trial balance.
- Clean comparisons. Year-over-year reporting starts fresh in the new system.
If your project is genuinely ready, with a tested migration, trained users and working integrations, January 1 is a good date.
Why it so often backfires
The problem is what else is happening in January.
Your finance team is closing December and closing the year in the old system. They're preparing for the audit, issuing 1099s and W-2s, and answering year-end questions from the business. A January 1 go-live asks the same people to learn a new system, check migrated balances and run the first month-end in Business Central, all at once.
That's when shortcuts happen. Opening balances get posted before the old year is final. Someone posts December invoices into the new system "just for now." The first close in Business Central slips into late February, and confidence in the project drops before it has had a fair chance.
There's a second trap. The old year isn't finished on January 1. Audit adjustments keep arriving into February or March. If your opening balances in Business Central were loaded from an unaudited trial balance, every adjustment has to be posted twice, once in the old system and once in the new, and the two have to agree.
The alternatives
Go live on the first day of a later month. February 1, March 1 or April 1 lets you close the old year in the old system, then cut over when the team has room. You load a mid-year trial balance as of the cutover date, plus open receivables, payables and inventory. Year-to-date detail stays in the old system or comes over as summary history. Your auditors deal with two systems for one year, which is common and manageable if you plan the reporting.
Go live January 1 on the general ledger, but stage the rest. Sometimes it makes sense to start the year in Business Central for finance while a difficult module, such as warehouse or manufacturing, follows a month or two later. This works only if the later piece doesn't feed the general ledger in ways you can't reconcile.
Go live at a quarter start. April 1 or July 1 gives you a natural reporting break and avoids the year-end crunch completely.
How to decide
Ask these five questions in the first week of December, honestly:
- Has a full test migration been run, and have the balances been reconciled to the old system? Not "mostly." Tied out.
- Has a full month been processed end to end in a sandbox, from orders and invoices through bank reconciliation and the financial reports the CFO signs?
- Are the integrations that create transactions (payroll, e-commerce, banking, expenses) working on real data?
- Can the people who close the books spend at least half their time on the new system in January?
- Is there a plan for audit adjustments to the old year after go-live?
If the answer to any of the first three is no, January 1 is a risk you're choosing to take. If the answer to question 4 is no, it's a risk your team will carry personally.
Features that help, whichever date you pick
Business Central has a few standard controls that make a cutover safer:
- Posting date limits. The Allow Posting From and Allow Posting To fields in General Ledger Setup, and per user in User Setup, stop entries from landing in the wrong period. Set them tightly from day one. (Microsoft's documentation.)
- Closing a year doesn't lock it. In Business Central, closing a fiscal year doesn't stop entries being posted to it. Use the posting date limits to control that. This matters when audit adjustments to your first Business Central year arrive.
- Sandboxes. Business Central Essentials and Premium include three sandbox environments alongside production, and you can create a sandbox with a copy of production data. Use one for a dress-rehearsal cutover a few weeks before go-live.
- Configuration packages are designed for setting up a company for the first time, not for loading data into a company that's already live. Plan your opening-balance loads before go-live, not as clean-up afterward.
An example
A 60-user specialty manufacturer moving from QuickBooks Enterprise was set to go live January 1. In mid-November, the inventory migration still didn't reconcile and the shipping integration hadn't been tested with real orders. We recommended moving to March 1. The team closed the year in QuickBooks, finished the audit with the books they knew, and spent February running a parallel month in a sandbox. Go-live was quiet, and the first close in Business Central took six working days.
Moving the date cost about two extra months of QuickBooks subscriptions and some consulting time. Rescuing a failed January go-live would have cost far more.
A word of honesty
Sometimes January 1 slips because the partner is behind. Sometimes it slips because the business couldn't free up the people who needed to test. Either way, the date doesn't fix the cause. If you move it, write down what has to be true before the new date, and who owns each item. Otherwise March 1 becomes the next January 1.
If your project is already behind and you're not sure whether it can recover, our article on the signs a Business Central implementation is in trouble is a good place to start. If you're coming from QuickBooks, see moving from QuickBooks to Business Central.
