+1 480 485 7373
Microsoft Teams
How does a Business Central migration path differ by source system?
The destination is the same, but the starting point changes the work. Small accounting packages hold a simple ledger and lists, so the effort goes into cleaning customers, vendors and items and deciding how much history to bring. Mid-market ERP systems carry segmented accounts, dimensions, projects, warehouses and custom code, so the effort goes into translating those structures and deciding what to rebuild.
Older Dynamics products sit in between. Dynamics GP and NAV have Microsoft tools and a known route to Business Central, while Dynamics AX usually points to Dynamics 365 Finance instead. Whatever you run, the same discipline applies: decide what moves, clean it before extraction, load it in order and reconcile every balance before go-live.
What takes the most care when leaving an accounting package or spreadsheets?
A short view of where the effort lands for smaller packages. Each linked page below goes further.
What takes the most care when leaving an older Dynamics product?
GP and NAV have a known route into Business Central, while AX usually points somewhere else.
What takes the most care when leaving another mid-market ERP?
Business Central migration paths from these systems turn on translating their structures, not on volume alone.
Which accounting systems and spreadsheets have a migration path?
Packages that small and growing companies tend to outgrow first.
QuickBooks migration →
Move from QuickBooks Online or Desktop to Business Central with clean master data, open items and balances that tie out.
QuickBooks Enterprise migration →
From QuickBooks Enterprise to Business Central: sites, bins, lots, assemblies, price levels and multiple company files carried across.
Sage 50 migration →
Sage 50 (US) to Business Central: masked accounts split into dimensions, open jobs carried as projects, balances proven at cutover.
Sage 100 migration →
Sage 100 to Business Central for distributors and manufacturers: modules, enhancements, work orders and valuation handled one by one.
Sage 300 to Business Central →
Moving from Sage 300 (Accpac): segments to dimensions, optional fields, account sets and multicurrency open items carried into Business Central.
Xero migration →
Leave Xero and its add-on apps for Business Central: contacts split, tracking categories redesigned, apps replaced or reconnected.
MYOB to Business Central →
MYOB to Business Central for Australian and New Zealand subsidiaries of US groups: localization, GST, cards and jobs, then consolidation into the parent.
Excel spreadsheets to Business Central →
From Excel workbooks to Business Central: cleaning, deduplication, configuration packages, templates and a counted-stock cutover.
Which ERP systems, including older Dynamics, can move to Business Central?
Mid-market systems and older Dynamics releases, plus the guides that go with them.
Dynamics GP migration →
Dynamics GP to Business Central using Microsoft's cloud migration, plus the posting groups, reports and ISV products it leaves to you.
Dynamics NAV migration →
Dynamics NAV to Business Central by technical upgrade or fresh start, with C/AL modifications sorted into keep, replace and retire.
Dynamics SL to Business Central →
Moving from Dynamics SL: account and subaccount split into accounts and dimensions, Project Controller budgets, labor and billing rebuilt as Business Central projects.
Dynamics AX to D365 Finance →
Dynamics AX 2012 to Dynamics 365 Finance and Supply Chain Management: data upgrade, code to extensions, reports and integrations, or a right-sized move to Business Central.
Sage Intacct to Business Central →
Sage Intacct entities become companies, dimensions stay dimensions, inter-entity postings become intercompany, and reports are rebuilt in Business Central.
NetSuite to Business Central →
Leaving NetSuite: subsidiaries to companies, classes and departments to dimensions, saved searches and SuiteScript rebuilt the Business Central way.
Acumatica to Business Central →
Acumatica subaccounts, business accounts, classes, open items and generic inquiries mapped into Business Central and reconciled.
SAP Business One to Business Central →
Moving from SAP Business One: business partners, item groups, UDFs, warehouses, BOMs and cost distribution rules mapped into Business Central.
Epicor to Business Central →
Epicor Kinetic, Prophet 21 and Eclipse to Business Central: parts, methods, jobs, price matrices and open orders mapped with a shop-floor-aware cutover.
Dynamics GP end of life →
What Microsoft has announced about Dynamics GP, the realistic options for GP companies, and how to plan a move without rushing it.
Dynamics NAV end of support →
What NAV end of support means in practice, the routes to Business Central, and how custom C/AL code and history shape the choice.
Data migration checklist →
A practical checklist for moving data into Business Central: cleanup, what moves, load order, reconciliation and the mistakes to avoid.
Which decisions repeat on every Business Central migration path?
Some choices do not depend on the old system at all. Pick a cutover date at the end of an accounting period, so opening balances come from a closed month. Decide how much detail to bring: most companies load open documents and balances, then keep the old database or an export as a read-only archive for lookups and audits.
Name one person in the business to own each list, such as customers, vendors, items and the chart of accounts. That person approves the cleaned version before it is loaded, and again after it lands. Agree who signs off the trial balance, open receivables, open payables and inventory value, and what difference counts as acceptable.
Finally, list every system that talks to the old one: the web store, the bank, payroll, shipping, tax and any reporting tool. Each one needs a new connection or a planned replacement, and each needs testing against Business Central before the cutover weekend, not after it.
What do people ask before choosing a migration path?
What if the system we use is not listed here?
The same method still applies. We look at how your system stores the ledger, lists, open documents and history, then map each one into Business Central. Send us the product name and version and we will tell you what the export options look like.
Do we have to move all of our history into Business Central?
No. Most companies bring opening balances, open documents and a chosen amount of summarized history, and keep the old system or an export as a read-only archive. The data migration checklist explains how to decide.
Where should we start if we have not chosen Business Central yet?
Start with the comparison pages and a readiness conversation. A Business Central migration path only makes sense once the destination is settled, and some companies are better served by Dynamics 365 Finance or by staying where they are.
Can a group move several entities on different dates?
Yes, and it is often safer. A group can bring one entity live first, learn from that cutover, then follow with the others at later period ends. Each entity still needs its own clean lists and signed-off balances, and intercompany accounts need a plan for the months when some entities post in Business Central and others still post in the old system.
Talk to us about your project.
Tell us what you run today and what has to change. A senior consultant replies with a written next step.