Employee CalculatingLast Updated: November 2026

Key Takeaways

The following covers what businesses moving to Microsoft Dynamics 365 Business Central need to know about data migration, common failure points, and how to set up a clean go-live:

  • Business Central data migration is one of the highest-risk phases of any implementation; data readiness is consistently cited as a leading cause of underperforming implementations, while well-executed projects have shown ROI of roughly 209% within three years, per Forrester research
  • The most common cause of migration failure is not the software; it is dirty source data that hasn’t been cleaned before migration begins
  • Data should be audited and cleaned in the source system first, before it is ever mapped to Business Central fields
  • A phased migration approach, migrating master data first and historical transactions second, reduces go-live risk significantly compared to attempting a single cutover
  • Testing in a Business Central sandbox environment with real data before go-live is non-negotiable; problems found in testing cost a fraction of what they cost in production

Most Business Central data migrations don’t fail because the software can’t handle the data. They fail because the data wasn’t ready before the migration started.

Data readiness is consistently cited as one of the leading causes of underperforming Business Central implementations, alongside scope creep and insufficient training. The flip side matters too: well-executed Business Central implementations deliver strong returns, with one Forrester study finding roughly 209% ROI within three years for organizations that got the foundation right. Data migration is one of the biggest factors separating those two outcomes.

For a Business Central implementation, the failure pattern almost always traces back to the same set of predictable, avoidable problems: duplicate records, inconsistent formats, unmapped fields, and decisions about what historical data actually needs to come across that nobody made until it was too late.

Here’s what those problems actually look like in a Business Central migration, and what to do about each one before you go live.

Why Does Business Central Data Migration Go Wrong So Often?

The short answer is that data migration gets underestimated. Teams focus on the software configuration, the training plan, and the go-live date, and they treat the data as something that will sort itself out once it’s imported.

It doesn’t sort itself out. Data from a legacy system, whether that’s Dynamics GP, QuickBooks, an old accounting package, or a collection of spreadsheets, reflects years of how that system was used. Duplicate customers. Vendors entered three different ways. Item numbers that were meaningful once and aren’t anymore. Account codes that don’t map cleanly to your new chart of accounts in Business Central.

The problems are almost always visible before migration starts and a proper data audit could easily surface them before migration. The trouble is that data audits feel like slow work when everyone is focused on the go-live timeline, and so they get compressed or skipped entirely. Then those problems show up in the new production system, which costs far more time to fix than the audit would have.

What Should You Audit Before Business Central Data Migration Begins?

The audit happens in your source system, before you touch Business Central. Its job is to identify everything that will cause problems in the migration, so you can fix it at the source rather than importing the problem and trying to clean it up after.

The areas that consistently surface issues in Business Central data migrations are:

Customer and vendor records. Duplicates are the most common problem. The same company entered under slightly different names, or the same vendor with two different account numbers from two different people who didn’t check the existing list. Merge and clean these before migration. Business Central will import what you give it.

Item master data. Units of measure mismatches, missing cost information, items that were discontinued but never marked inactive, and description of fields that are inconsistent across records. Every item that comes into Business Central needs to be accurate because it feeds purchasing, sales, inventory, and reporting from day one.

Chart of accounts. Your old chart of accounts and your new Business Central chart of accounts are almost certainly not a one-to-one match. This mapping needs to be done deliberately and reviewed by your finance team, not assumed. Account coding that comes over wrong creates reporting problems that take months to untangle.

Open transactions. Decide which open transactions come across and which don’t. Open AR, open AP, and open purchase orders are the most common candidates. Historical closed transactions are a separate decision entirely. Not everything needs to migrate, and trying to bring across ten years of transaction history is one of the most reliable ways to add weeks to a migration timeline.

Business Central Data Migration checklist

 

 

 

 

 

 

 

 

 

 

 

 

How Should You Structure a Business Central Data Migration?

A phased approach consistently produces cleaner go-lives than attempting to migrate everything at once.

The standard sequence CAL uses starts with master data: customers, vendors, items, and the chart of accounts. These records are the foundation everything else depends on, and getting them into Business Central first allows your team to validate them in a real environment before any transactions are attached.

Once master data is validated, open balances and open transactions come next. AR balances, AP balances, open purchase orders, and open sales orders. These are the records that affect day-to-day operations from the moment you go live, so they need to be right.

Historical transaction data is handled last and often selectively. Many organizations choose to keep their legacy system accessible for historical reference rather than migrating years of closed transactions into Business Central. That’s a legitimate choice, and in many cases it’s the right one. The decision should be made intentionally, not by default.

For teams moving from Microsoft Dynamics GP, CAL’s GP migration resources page covers the specific considerations that come with that transition, including what data typically migrates cleanly and what needs special handling.

Microsoft Dynamics GP Resources screen

 

 

 

 

 

 

 

 

How Do You Use Business Central Tools to Support Data Migration?

Microsoft Dynamics 365 Business Central includes built-in tools designed to support data migration that are worth understanding before you start.

The Business Central solutions page covers the platform’s capabilities in detail, but from a migration standpoint, the most relevant tools are the Configuration Packages (also called RapidStart Services) and the Excel import functionality available throughout the system.

Configuration Packages let you define a data template for a Business Central table, export it as an Excel file, populate it with your cleaned source data, and import it back. This works well for master data loads, including customers, vendors, and items, because it gives your team a structured format to work with and validates the data against Business Central’s field requirements before the records are created.

For transactions, Business Central also supports importing through the standard journal and document entry screens using Excel. This approach is more manual but gives you fine-grained control over each record and makes it easy to catch errors before posting.

One important note: whatever tool you use, always run your first import in a Business Central sandbox environment, not production. A sandbox gives you a copy of your Business Central configuration to test against without any risk to live data. Import your migration data there first, validate the results, fix any errors, and only then run the confirmed import in production.

 

 

 

 

 

 

What Are the Most Common Business Central Data Migration Mistakes at Go-Live?

Even the most well-planned migrations have go-live surprises. The goal is to make sure those surprises are minor and fixable, not operational.

The mistakes that most often create problems at go-live are: importing data that wasn’t fully validated in the sandbox, going live with a chart of accounts that hasn’t been reviewed by the finance team, failing to confirm opening balances against the legacy system before cutover, and not having a clear plan for what happens to the legacy system in the days immediately after go-live.

That last one matters more than most teams expect. Users will try to look something up in the old system. A customer will ask about an order that predates the migration. Someone will need a report that was built in the legacy system and hasn’t been recreated in Business Central yet. Having a clear plan for how long the legacy system stays accessible and who handles those requests in the transition period prevents a lot of confusion in the first two weeks.

For more on how Business Central handles operational workflows once the migration is complete, the Business Central approval workflows post is worth reading as a next step.

Frequently Asked Questions: Business Central Data Migration

How long does a Business Central data migration typically take?

Timeline depends on the volume and quality of source data and the complexity of the legacy system. For most mid-market implementations, the data migration phase, including audit, cleaning, mapping, testing, and go-live, runs four to eight weeks as part of an overall implementation that takes six to nine months from discovery to go-live. Organizations with very clean source data and straightforward chart of accounts mappings can move faster. Those with years of inconsistent data entry or complex legacy customizations should plan for the longer end of that range.

Do you need to migrate all historical data to Business Central?

No. Many organizations choose to migrate only open transactions and master data, keeping their legacy system available for historical reference during a transition period. This approach significantly reduces migration complexity and go-live risk. The decision about what historical data to bring across should be made deliberately based on operational need, not by attempting to migrate everything by default.

What is the biggest risk in a Business Central data migration?

Poor data quality in the source system is consistently the highest-risk factor. Duplicate records, inconsistent formats, incomplete fields, and unmapped account codes all create problems that are far easier and cheaper to fix before migration than after go-live. A thorough data audit in the source system, before any migration work begins in Business Central, is the single most effective way to reduce go-live risk.

How does Business Central handle data validation during import?

Business Central validates imported data against its field requirements and business rules during the import process. Records that fail validation are flagged with an error and not created, which means errors surface during testing rather than silently passing through. This is why testing imports in a sandbox environment with real data is so important: Business Central’s validation catches problems that a visual review of a spreadsheet might miss.

Getting Your Business Central Migration Right the First Time

Data migration is the phase of a Business Central implementation where cutting corners has the longest tail. Problems that go live with the system take months to work through, and they undermine confidence in the data at exactly the moment when your team needs to trust it most.

If you’re planning a Business Central implementation or evaluating your migration approach, contact CAL Business Solutions to talk through what a clean data migration looks like for your specific situation.

Contact Us

CAL Business Solutions is a Microsoft Dynamics 365 Business Central implementation partner serving distribution, manufacturing, brick & block, and professional services businesses across the United States. Our team has helped organizations plan and execute Business Central data migrations, from legacy system audits through go-live and beyond.