Now Reading: How to prepare for a QuickBooks to Business Central migration
-
01
How to prepare for a QuickBooks to Business Central migration
Preparing for a QuickBooks to Business Central migration means getting your data, your team and your decisions in order before the technical work starts, so the project runs to plan and people actually use the new system once it’s live.
Most migrations that disappoint don’t fail on technology. They fail on preparation and people. The software does what it says. The risk sits in everything around it.
- Decide who owns the project internally before you start
- Clean your data early, it’s the single most preventable cause of delay
- Choose your cutover approach on purpose, not by default
- Budget for internal time, not just the licence and the implementation fee
- Plan adoption from day one, not as an afterthought at go-live
Plan your implementation
Rushed implementation vs structured foundation
| Factor | Rushed implementation | Structured foundation |
|---|---|---|
| Data | Migrated as-is, duplicates and errors carried across | Cleaned and reconciled before anything moves |
| Ownership | No clear internal lead, decisions stall | Named owner with authority and time |
| Chart of accounts | Copied from QuickBooks, same reporting limits | Restructured with dimensions for better reporting |
| Adoption | Training bolted on the week before go-live | Users involved early, trained on real data |
| Result | People drift back to spreadsheets | The system becomes one version of the truth |
Still weighing up whether to move at all? Our QuickBooks to Business Central migration overview covers that decision. This guide picks up at the next step. You’ve broadly decided, and now you want the move to go well.
How do you know if your business is ready to migrate from QuickBooks?
Readiness has little to do with the software and everything to do with your business.
Before you migrate from QuickBooks to Microsoft Dynamics 365 Business Central, you need a named internal owner, time committed from finance and operations, data that’s in good enough shape to assess, and leadership behind the project. A business can genuinely need Business Central and still not be ready to start.
Wanting better software is not the same as being set up to deliver a project. The gap between those two things is where budgets and timelines slip.
Our simple readiness check
Run through this before you commit a date. You’ll be ready when you have:
- A named project owner, one person with the authority to make decisions and the time to do it
- Realistic time set aside from finance and operations, not just goodwill on top of the day job
- Data that’s tidy enough to assess, even if it still needs cleaning
- Leadership sponsorship, so decisions don’t stall halfway through
- A clear reason for moving now, written down in a sentence anyone can repeat
Signs you should wait
Hold off if no one internally owns the project, because a migration without an owner drifts.
Wait if a major trading peak lands near your planned go-live, since your team won’t have the time.
Be honest if you’re hoping software alone will fix broken processes. In our experience, it won’t. Business Central is a better tool, not a substitute for sorting out how you work.
How to build a business case for leaving QuickBooks
A solid business case compares the real, often hidden cost of staying on QuickBooks against the cost of moving.
The hidden costs includes workaround time, duplicated data entry, errors and rework and the hours spent rebuilding the same reports every month. For many organisations, quantifying the cost of staying persuades leadership better than a feature list ever will.
How to put a number on the cost of staying
Measure what the status quo actually costs. The method is simple:
- Add up the hours your team spends on month-end each period
- Count the time rebuilding reports that the system can’t produce on its own
- Estimate the cost of errors, corrections and chasing mismatched figures
- Include the duplicated data entry between QuickBooks and your spreadsheets or bolt-on tools
Here’s a worked example.
Say month-end takes your finance team three days, and two people are involved. That’s roughly six working days a month, or about 72 days a year. On a £35,000 salary, a working day costs somewhere around £160 once you account for holidays. That’s more than £11,000 a year, before you count report building or error correction. Suddenly the cost of moving looks different.
These figures are illustrative, and yours will vary. The point is the exercise, not the exact total.
Getting leadership and the team behind it
Bring sceptics in early rather than presenting a finished decision. Show leadership the cost of staying, not just the price of moving. Involve the people who’ll use Business Central every day from the start, because resistance later usually traces back to a team that felt the change was done to them.
What data migrates from QuickBooks and what doesn’t
Most businesses migrate master data and opening balances cleanly, while historical transactions and reconciliations take extra work, and things like open orders, custom reports and poorly structured data rarely come across cleanly. The goal of a QuickBooks to Business Central migration is an accurate, reconciled opening position, not a full copy of every transaction you’ve ever recorded.
Think of it as moving house. You take what you need and use well. You don’t box up rubbish and pay to store it in a nicer place.
| Data type | How it migrates |
|---|---|
| Usually migrates well | Customers and suppliers, chart of accounts, opening balances |
| Often requires work | Historical transactions, partial payments, reconciliations |
| Usually not migrated cleanly | Open sales orders, purchase orders, custom reports, poorly structured data |
In many cases, businesses migrate summary balances rather than full transaction history, and keep QuickBooks as a read-only archive they can refer back to if they ever need the detail.
How much data should you actually move?
Migrate balances and master data, and keep QuickBooks as an archive. That’s the pattern that works for most small and mid-sized businesses. Moving years of full transaction history into Business Central adds cost and complexity, and the payback is small. You can still look up an old invoice in QuickBooks on the rare occasion you need it. Migrating the lot to avoid that rare lookup is rarely worth the bill.
How to clean and prepare your QuickBooks data before migrating
Data cleansing is the single most underestimated and most preventable cause of migration delays. The work should start weeks before any data moves, not during the migration itself. Messy data doesn’t get cleaner by changing systems. It just becomes a more expensive mess in Business Central, with your team blaming the new software for problems they brought with them.
Nearly everyone wishes they’d started this process sooner.
Work through this in order before migration begins:
- Deduplicate customers and suppliers, so you don’t carry three versions of the same account across
- Archive inactive accounts and obsolete items you no longer trade or buy
- Standardise naming conventions, so records sort and search the way you expect
- Review the chart of accounts and remove codes nobody uses
- Reconcile bank and control accounts, so your starting numbers are trustworthy
- Write off uncollectable balances that will never be paid
- Agree what’s “good enough” to migrate, so cleansing has a finish line and doesn’t run forever
How long should data cleansing take?
Allow several weeks of part-time effort for a typical small business. The good news is this work can usually run in parallel with the early stages of the project, like discovery and configuration. It rarely needs to sit on the critical path if you start it early enough. If you leave it until the migration is underway it can hold everything up.
How to redesign your chart of accounts for better reporting in Business Central
A migration is the best chance you’ll get to restructure your chart of accounts. Copying your QuickBooks structure across unchanged is a common mistake and it locks in the same reporting limits you were trying to escape. If you want better numbers out of Business Central, you have to set up the foundations better at the start.
Mapping vs redesigning
Mapping moves what you already have. Redesigning improves how you’ll report. Mapping is fast and low effort; however, it carries your old limitations straight into the new system. Redesigning takes more thought up front, but it’s the difference between a chart of accounts that records what happened and one that explains it. Most businesses benefit from a tidy-up, not a wholesale rebuild.
How dimensions replace endless account codes
Business Central uses dimensions, which are tags like department, location or project that you attach to transactions and then report by. Instead of creating a separate account code for every combination of cost and department, you tag once and slice the data later. Microsoft’s guidance on working with dimensions explains that you can set up two global dimensions and eight shortcut dimensions, so it pays to choose the ones you report on most.
The result is a shorter, cleaner chart of accounts and far more flexible reporting. You can analyse data by dimensions to view, say, profit by region or cost by project without rebuilding your accounts every time the business changes shape.
The QuickBooks to Business Central migration process in detail
A migration runs as a sequence of planned stages, not a single event. Understanding what happens at each stage, and what’s expected of your team along the way, is how you avoid surprises and keep the project on track.
Here’s how a migration typically runs:
- Discovery and process mapping. We sit with you and map how your business actually works, not just your chart of accounts. Your job here is to be honest about what’s broken, not just what’s official
- Data cleanup. The cleansing checklist above happens now. This is bigger than most teams expect, and your involvement is what makes it accurate
- System configuration. We set up Business Central around your workflows, approvals, user roles and reporting. You’ll need to make decisions, so keep your owner available
- Data migration. We load your cleansed data into Business Central using configuration packages and import templates. Expect to answer questions as edge cases surface
- Testing and reconciliation. This is where user acceptance testing (UAT) matters. We reconcile balances back to QuickBooks, and your team tests real tasks. If numbers don’t match, they get fixed before go-live, not after
- Training. Your team learns the new system on their actual jobs, not a generic demo. The more they engage now, the smoother go-live feels
- Go-live and cutover. The planned switch from QuickBooks to Business Central, timed to suit your business cycle
- Post go-live support. The first weeks bring the most questions. We stay close. Same team, same people, no hand-off to a call centre
Parallel running vs a clean switch: choosing your cutover approach
You have two broad cutover options. You can run QuickBooks and Business Central in parallel for a short period, or switch cleanly on a set date. The right choice depends on your risk appetite, your team’s spare capacity, and where you sit in your financial year. Neither is automatically better, so choose it on purpose rather than letting it happen by default.
| Approach | Best for | Pros | Cons |
|---|---|---|---|
| Parallel running | Lower risk appetite, complex finances, teams that want a safety net | Confidence from comparing both systems, errors spotted before full reliance | Double the data entry for a period, heavier short-term workload |
| Clean switch (big bang) | Simpler setups, teams short on capacity, a clear period cut-off | No duplicated effort, faster, forces a decisive move | Less margin for error, more pressure on testing and preparation |
When to time your migration
Most businesses aim for the start of a financial period or year end, because a clean cut-off makes opening balances simpler and keeps your reporting tidy. Avoid your busiest trading weeks. A distributor going live the week before its Christmas peak, or an accountancy practice switching at the height of self-assessment season, is asking for a hard month. Pick the quiet stretch in your calendar.
How to plan for change management and team adoption
The most common reason a migration fails to deliver is not technical. It’s that people drift back to old habits and spreadsheets.
Adoption has to be planned from the first week of the project, not bolted on just before go-live. A brilliant Business Central setup that nobody uses properly is worth less than a modest one the whole team embraces.
A practical adoption plan
- Involve users in the design early, so the system reflects how they actually work
- Train on real workflows with real data, not a generic click-through
- Name internal champions, people who become the go-to in each team
- Give people time to learn, rather than expecting fluency on day one
- Expect a short productivity dip in the first few weeks, and say so openly, so nobody panics when it happens
Why training on your own data matters
Generic “here’s where to click” training fails because it doesn’t connect to anyone’s actual job. Training on your team’s real workflows and real data is what makes the new system stick, because people leave the session knowing how to do their own work, not someone else’s example. Software alone doesn’t change a business. but people do.
How to budget for a migration
The licence and implementation fees are the visible costs of a migration. The budget that can catch people out is the internal one: the staff time, process redesign, report rebuilding and training which rarely appears on a quote, but always shows up in reality. Plan for it up front and the project feels under control. If you ignore it, it will arrive as a nasty surprise halfway through the project.
To estimate the internal cost, work out how many hours your finance and operations people will spend in discovery, testing and training, then cost those hours at their day rate. Add a contingency, because something always takes longer than planned. And factor in the short productivity dip in the first month, when the team is learning.
For indicative price ranges and the breakdown of typical costs, see the our migration service page, which covers the headline figures.
What to ask a Business Central migration partner before you commit
The right questions reveal how a partner works, long before any contract. The signals to look for are a proper scoping process before any quote, the same team staying with you through go-live and support, and honest answers about data, timelines and what could go wrong. A partner who quotes after a 30-minute call is guessing, and you’ll pay for the guesswork later.
Ask these, and listen for the answer underneath the answer:
- Do you scope before quoting? A good answer involves time understanding your business, not a price off the shelf
- Who’s on my team, and do they stay through support? You want named people, not a hand-off to a separate helpdesk
- How do you reconcile data before go-live? Look for reconciliation back to QuickBooks as standard, not an optional extra
- What happens if the numbers don’t match? A confident partner fixes it before go-live and tells you how
- What support do I get in the first month? The busiest period needs quick access to someone who knows your system
Frequently asked questions
You can import bank transactions, for example via CSV, or use a bank feed or extension for automation, and if you already import statements in QuickBooks the process starts out similar. Automation can be added later once you’re settled in.
Business Central calculates VAT on transactions, produces VAT returns, and supports Making Tax Digital submissions to HMRC. Getting the VAT setup right from the start is what matters, because everything downstream depends on it.
You can usually reuse core configuration, processes and reporting structure if the businesses run in a similar way. You’ll still need to adjust for VAT rules, currency and local requirements, but it’s normally faster and cheaper than starting from scratch.
One named person with the authority to decide and the time to commit, usually finance-led with operational input. Without a clear owner, decisions stall and the project drifts.
More than most expect, especially from finance and operations during scoping, testing and training. The calendar timeline is often set by your team’s availability, not by the technical work itself.
Most businesses pick the start of a financial period or year end for a clean cut-off. Avoid your busiest trading weeks, when no one has the headspace to learn a new system.
What people often get wrong about migration preparation
The businesses that struggle with a QuickBooks to Business Central migration aren’t the ones with the most complex data. They’re the ones that treated preparation as paperwork and adoption as an afterthought. The technical migration is the easy part. The prep and the people decide whether it works, and that’s true almost regardless of how big or complicated your business is.
We hear the same reflections after go-live, again and again:
- “We didn’t realise how broken our processes were until we tried to map them”
- “Training took longer than expected”
- “The system is powerful, but only if we use it properly”
- “We wish we’d cleaned our data earlier”
Notice what’s missing from that list. Nobody says the software let them down. They talk about processes, training, habits and data. Those are the things you can sort out before a single record moves.
So if you do only three things before your migration, make them these: name an owner, clean your data, and plan how your team will adopt the system.
The post How to prepare for a QuickBooks to Business Central migration appeared first on All My Systems.
Check Pete Murray’s original post https://www.allmysystems.co.uk/how-to-prepare-for-a-quickbooks-to-business-central-migration/ on www.allmysystems.co.uk which was published 2026-06-18 10:14:00
