top of page

Business Central Data Migration: What Should You Move, Clean or Leave Behind?

53 minutes ago
14 min read

You're moving to Microsoft Dynamics 365 Business Central.


You've chosen the system.


You're looking forward to better reporting, fewer spreadsheets and more connected financial processes.


Then someone asks:


"What are we doing with all our existing data?"


Suddenly, the project becomes more complicated.


There are thousands of customers.


Years of supplier transactions.


Duplicate records.


Old product codes.


Historical invoices.


Spreadsheets that nobody fully understands.


And everyone assumes all of it needs moving into the new system.


But does it?


One of the most important decisions in a Business Central data migration is understanding what information the business actually needs.


Moving everything may seem like the safest option.


In reality, it can increase implementation costs, create unnecessary complexity and carry old problems into your new environment.


A successful migration isn't about transferring the largest possible amount of information.


It's about starting Business Central with accurate, useful data that supports how your business needs to operate.


Why does Business Central data migration matter so much?


Data migration is often treated as a technical task.


Export the information.


Clean up a spreadsheet.


Upload it into Business Central.


Job done.


Except the information being migrated affects almost everything your business does afterwards.


Consider what happens if:


  • A customer has three different records.

  • A supplier's payment terms are incorrect.

  • A product code doesn't match the operational process.

  • An outstanding invoice is missing.

  • Opening balances don't reconcile.

  • An inactive customer is accidentally treated as active.


These aren't simply data problems.


They can affect invoicing, payments, reporting, customer service and financial control.


📊 Your new ERP will only be as reliable as the information you put into it.


That is why data migration deserves attention before the implementation reaches its final stages.


What data should you migrate to Business Central?


The answer depends on your business and the agreed implementation scope.


A company moving from Sage or Xero into core financial management will have different requirements from a distributor implementing inventory and warehousing.


But several categories usually need consideration.


Customer records


Your customer information may include:


  • Customer names

  • Addresses

  • Contact information

  • Payment terms

  • Credit limits

  • Currency

  • VAT information

  • Customer references


The key question is whether each record is accurate and still required.


If a customer hasn't traded with you for eight years, do they really need to become an active customer in Business Central?


Not necessarily.


That historical information may need retaining, but it doesn't automatically need to be part of your live operational system.


Supplier records


Supplier information deserves the same attention.


Review:


  • Supplier names

  • Addresses

  • Payment terms

  • Contact details

  • Currency

  • VAT information

  • Relevant payment details


Duplicate suppliers can create purchasing confusion and increase the risk of payment errors.


Migration is an opportunity to establish a cleaner supplier list.


Chart of accounts


Your chart of accounts is the foundation of financial reporting.


But an existing chart of accounts may have developed gradually over many years.


It might contain:


  • Unused accounts

  • Duplicate categories

  • Inconsistent naming

  • Accounts created for one-off reporting requirements

  • Structures that no longer reflect the business


Rather than copying everything automatically, consider whether the existing structure still supports the reporting you need.


A new financial system is an opportunity to improve how financial information is organised, not simply reproduce an outdated structure.


Opening balances


Opening balances are essential for establishing the financial position at the agreed migration date.


Depending on the migration approach, this may involve:


  • General ledger balances

  • Customer balances

  • Supplier balances

  • Bank balances

  • Inventory balances

  • Other relevant balance-sheet accounts


These figures must be carefully reconciled.


If the balances brought into Business Central don't agree with the approved closing position in the previous system, the business begins with a reporting problem.


Outstanding transactions


The business may also need to migrate or recreate open transactions.


For example:


  • Unpaid customer invoices

  • Outstanding supplier invoices

  • Customer credit notes

  • Supplier credit notes

  • Unallocated payments

  • Open sales orders

  • Open purchase orders


Exactly which transactions are included depends on the implementation scope and migration method.


Not every migration tool handles every transaction type in the same way.


That needs agreeing before data preparation begins.


Do you need to migrate all your historical transactions?


This is one of the most important questions to ask.


Many businesses assume that moving to a new accounting system means transferring every transaction from the old one.


Ten years of invoices.


Every supplier payment.


Every journal.


Every historical adjustment.


Every closed customer order.


That might be appropriate in some circumstances.


But it isn't automatically necessary.


Understand the difference between historical access and live migration


Your business may need access to historical records for:


  • Audit

  • Tax

  • Customer queries

  • Financial comparisons

  • Legal or regulatory obligations


That doesn't always mean those records must be imported into the live Business Central environment.


An alternative may involve retaining a secure, searchable archive of the old system's records.


The appropriate retention and access arrangements should be agreed with your finance team and relevant advisers.


Why moving everything can create unnecessary work


Historical transactions may contain information structured differently from your new system.


Bringing them across can require additional:


  • Data mapping

  • Validation

  • Reconciliation

  • Testing

  • Configuration

  • Consultancy


The business needs to decide whether that effort creates sufficient value.


👉 Keeping access to historical information is important. Importing every historical transaction into your new ERP is a separate decision.


Why data cleansing should happen before migration


Imagine your existing accounting system contains 12,000 customer records.


Of those:


  • 2,000 are inactive.

  • 600 are duplicates.

  • 400 contain incomplete information.

  • Several hundred use outdated addresses or contact details.


If you migrate everything without reviewing it, Business Central inherits the same problems.


The software has changed.


The quality of the information hasn't.


That is why data cleansing matters.


Remove duplicate records


Look for customers or suppliers that appear more than once.


For example:


ABC Engineering Ltd

ABC Engineering Limited

ABC Eng Ltd


These might be three legitimate records.


Or they might represent the same customer.


The business needs to establish which is correct.


Care is required where records have outstanding transactions or important historical relationships.


Don't simply delete or combine records without understanding their financial impact.


Review inactive information


Identify records that are no longer used.


Ask whether they need to be:


  • Migrated as active records

  • Retained but blocked from use

  • Preserved in an archive

  • Excluded from the live migration


The decision should reflect operational and record-retention requirements.


Standardise important fields


Review consistency across:


  • Customer names

  • Supplier names

  • Postcodes

  • Payment terms

  • Item codes

  • Units of measure

  • Financial categories

  • Reporting dimensions


Consistent information makes the new system easier to use.


Correct known errors


If the business already knows certain records are incorrect, address them before the migration.


⚠️ Don't use a new ERP implementation to preserve data problems your employees have been working around for years.


What happens if you migrate poor-quality data?


The immediate consequences may not be obvious.


Business Central goes live.


Employees start using it.


Then the problems begin appearing.


Customer invoices need correcting


Duplicate or outdated customer information creates billing errors.


Finance spends time investigating.


Supplier payments require additional checking


Supplier information is inconsistent.


Employees need to verify records manually.


Reports don't match expectations


Financial categories or opening balances are incorrect.


Management questions the figures.


Employees return to spreadsheets


Users don't trust the migrated information.


They begin maintaining separate records.


Implementation costs increase


Problems that could have been identified during preparation now require correction after go-live.


The business may need additional consultancy, reconciliation and testing.


The result is frustrating.


You've invested in a new system, but employees are still dealing with many of the problems that existed before the migration.


Why opening balances need particular attention


Opening balances are one of the most commercially important parts of an accounting system migration.


They establish where the business starts financially.


If they're wrong, your reports may be wrong from day one.


Consider a simple example.


Your old accounting system shows:


Outstanding customer balances: £185,000


After migration, Business Central shows:


Outstanding customer balances: £181,500


There's a £3,500 difference.


That might represent:


  • A missing invoice

  • An incorrectly migrated credit note

  • An unallocated payment

  • A duplicated adjustment

  • A transaction recorded after the agreed cut-off


The difference needs investigating before the figures are approved.


Don't rely on the overall trial balance alone


A trial balance may reconcile while individual customer or supplier balances are still incorrect.


For example, amounts might have been allocated to the wrong customer.


The total receivables figure could still agree.


But collecting the money would become more difficult.


That's why migration validation should consider both:


Financial totals


and


The individual transactions supporting those totals.


💷 Accurate opening balances protect more than financial reporting. They support credit control, supplier payments, cash flow and management decisions.


Why your migration date matters


A data migration needs a clearly defined point at which the business moves from one system to another.


This is often called the cutover.


The business needs to agree:


  • When the old system stops accepting routine transactions

  • Which transactions belong in the old system

  • Which transactions belong in Business Central

  • When final balances will be extracted

  • Who validates the transferred information

  • When employees can begin working in the new environment


Without a clear cutover plan, transactions can be missed or duplicated.


Example: a supplier invoice arrives during migration


Imagine the business receives a supplier invoice on the day before go-live.


Finance enters it into the old system.


The data migration has already been prepared.


If the invoice isn't included in the final reconciliation, Business Central may begin without that liability.


Alternatively, if the invoice is transferred and entered manually again, the business could record it twice.


Neither outcome is desirable.


A clear process for transactions arriving around cutover helps prevent these problems.


Should you change your chart of accounts during migration?


Sometimes.


But the decision needs careful planning.


Your existing chart of accounts may not support the reporting your business now requires.


For example, management may want to understand profitability by:


  • Department

  • Business unit

  • Project

  • Location

  • Product group


The existing system might use separate general ledger accounts for information that could be structured differently in Business Central.


Business Central supports dimensions that can help analyse financial information without creating an unnecessarily complicated chart of accounts.


However, redesigning the financial structure introduces additional decisions.


Ask these questions first


  • Which reports does management actually need?

  • Which financial categories are no longer useful?

  • Which accounts are duplicated or inactive?

  • Do departments need separate reporting?

  • How should historical comparisons work?

  • Who will approve the new structure?


The aim should be clearer financial information.


Not changing the chart of accounts simply because the software allows it.


How do you prepare data for a Business Central migration?


You don't need to understand every technical detail.


But your business should take responsibility for the accuracy of the information being moved.


A practical preparation process looks like this.


Step 1: Decide what needs migrating


Separate information into three categories.


Essential for go-live


Data required to operate the business immediately.


Potentially useful later


Information that may support future processes or reporting.


Historical information


Records that need retaining but may not need to be part of the live ERP.


This prevents unnecessary work.


Step 2: Assign data owners


Finance should not automatically be responsible for every type of information.


For example:


Finance


  • Chart of accounts

  • Opening balances

  • Customer and supplier financial information


Sales


  • Customer details

  • Commercial terms

  • Relevant customer classifications


Purchasing


  • Supplier information

  • Purchasing references


Operations


  • Product information

  • Stock details

  • Operational records


Each area should have someone responsible for reviewing and approving its information.


Step 3: Clean the data


Remove unnecessary duplication.


Correct known errors.


Identify inactive records.


Standardise important information.


Keep a record of significant changes.


Step 4: Agree the migration method


The correct method depends on your existing system and Business Central requirements.


Microsoft provides different import and migration approaches, including tools for importing information from Excel and supported accounting applications.


For a migration from Sage or Xero, the specific approach should be confirmed against the source product, available tools and agreed data scope.


Don't assume every finance system supports the same migration process.


Step 5: Complete a test migration


Where the project scope warrants it, use a test environment or migration rehearsal before the final cutover.


This helps identify:


  • Missing information

  • Invalid records

  • Incorrect mappings

  • Unexpected financial differences

  • Process problems


It is better to identify those issues before employees begin using the new system.


Step 6: Validate the results ✅


Check that the important information agrees.


For example:


  • Customer records are correct.

  • Supplier records are correct.

  • Opening balances reconcile.

  • Outstanding invoices are accurate.

  • Relevant stock figures agree.

  • Financial reporting produces expected results.


Don't rely solely on the number of records imported.


A successful upload doesn't automatically mean the data is correct.


What should you test before going live?


Migration testing should reflect how the business will actually operate.


Finance


Can employees:


  • Find customer balances?

  • Review supplier balances?

  • Process a customer invoice?

  • Record a supplier invoice?

  • Reconcile relevant accounts?

  • Produce expected financial reports?


Sales


Can employees:


  • Find active customers?

  • Confirm payment terms?

  • Create relevant transactions?

  • Access the information they need?


Purchasing


Can employees:


  • Find the correct supplier?

  • Use agreed purchasing terms?

  • Complete routine purchasing tasks?


Inventory and operations


Where included in the implementation:


  • Are item records correct?

  • Do quantities agree?

  • Are units of measure accurate?

  • Are relevant locations configured?

  • Can employees complete normal stock transactions?


The exact tests will depend on the scope.


The important principle is straightforward.


Don't just check whether the data arrived. Check whether employees can use it to run the business.


Why moving from Sage or Xero doesn't have to become a huge project


Businesses sometimes delay moving to Business Central because they expect data migration to be complicated and expensive.


That concern is understandable.


The existing system may contain years of information.


There may be uncertainty about historical records.


Employees may worry about losing access to important transactions.


But the implementation doesn't always need to involve moving everything.


For businesses with relatively straightforward financial requirements, a focused approach may involve:


  • Agreeing the essential data

  • Cleaning active records

  • Preparing opening balances

  • Identifying outstanding transactions

  • Retaining appropriate historical access

  • Testing the new environment

  • Going live with core financial processes


More complex businesses may need additional migration work.


For example, a manufacturer with multiple locations, significant stock and complex costing requirements will generally have different needs from a professional services company moving its core accounts.


The migration should reflect those differences.


How does Dynamics Fanatics approach Business Central implementation?


At Dynamics Fanatics, our approach is built around getting the essentials right first.


We help growing UK businesses move from accounting systems such as Sage, Xero and QuickBooks to Microsoft Dynamics 365 Business Central.


Our KickStart service provides a fixed-scope, fixed-price approach for businesses that want to get their core system operational without an unnecessarily long implementation project.


The approach includes defined setup, data imports, training and support.


Rather than assuming every historical record and advanced requirement needs to be addressed immediately, the implementation is focused on the agreed business priorities.


Additional functionality can then follow as required.


That doesn't mean every business will be suitable for a rapid implementation.


Complex data migration, significant customisation or extensive integrations may require a different scope.


The important part is choosing an approach that reflects the actual requirements of the business.


What does a good migration look like in practice?


Consider a growing professional services business moving from Sage to Business Central.


Before migration


The business has:


  • 4,000 customer records

  • 2,500 supplier records

  • Eight years of financial transactions

  • Several separate reporting spreadsheets

  • Duplicate customer entries

  • An outdated chart of accounts


Management initially assumes everything needs transferring.


During preparation


The business reviews the data.


It identifies:


  • Inactive customers

  • Duplicate suppliers

  • Unused nominal accounts

  • Historical transactions that can remain accessible through an appropriate archive

  • Current balances that need migrating

  • Outstanding invoices requiring reconciliation


The scope becomes clearer.


At go-live


Business Central starts with:


  • Clean customer and supplier records

  • An agreed chart of accounts

  • Validated opening balances

  • Relevant outstanding transactions

  • Core financial processes ready for use


Employees receive training on the activities they need to complete.


The previous system's historical information remains available through the agreed retention arrangements.


What improves?


The new system begins with more consistent information.


Finance spends less time correcting inherited records.


Management has a clearer reporting structure.


Employees don't need to work around years of unnecessary data.


The business has also avoided making the project larger simply to transfer information it doesn't need for everyday operations.


Business Central data migration checklist


Before starting your migration, work through the following questions.


📋 Data preparation


  • Have we identified the information required for go-live?

  • Have we reviewed duplicate customer and supplier records?

  • Have we identified inactive information?

  • Are important fields complete and consistent?

  • Have we agreed the future chart of accounts?

  • Do we understand which historical records need retaining?


Financial information


  • Have we agreed the migration cut-off date?

  • Are opening balances accurate?

  • Have outstanding customer invoices been reviewed?

  • Have outstanding supplier invoices been reviewed?

  • Have we considered bank reconciliation requirements?

  • Have we agreed how balances will be validated?


Operational information


  • Are relevant product and item records accurate?

  • Have we agreed which open orders need transferring?

  • Are stock quantities and valuations understood?

  • Have we identified any important system dependencies?


Go-live readiness


  • Is someone responsible for each data category?

  • Has the migration approach been agreed?

  • Have necessary tests been completed?

  • Have important financial totals been reconciled?

  • Do employees know how to access historical information?

  • Is the cutover process understood?

  • Have the appropriate people approved the final data?


If several of these questions remain unanswered, it's worth resolving them before the migration begins.


What are the biggest data migration mistakes to avoid?


Several mistakes appear repeatedly in ERP projects.


Moving everything without reviewing it


More data doesn't automatically create a better implementation.


Focus on business value and operational requirements.


Leaving cleansing until the last minute


Poor-quality information can delay migration and create unnecessary correction work.


Start preparing early.


Assuming all systems migrate data in the same way


Different source systems and migration tools support different types of information.


Confirm what can be transferred before finalising the scope.


Failing to reconcile opening balances


Financial totals and supporting transactions need checking.


Don't assume a completed import guarantees accuracy.


Forgetting about historical access


Decide how employees will retrieve older records before the previous system becomes unavailable.


Not involving the people who use the data


Finance may understand the balances.


Sales understands customer information.


Operations understands stock and product records.


Each team has a role in validating the information relevant to its work.


How can you measure whether data migration was successful?


Migration success shouldn't be judged only by whether the import completed.


Look at practical outcomes.


Data accuracy


Are customer, supplier and operational records correct?


Financial reconciliation


Do opening balances and relevant outstanding transactions agree with the approved source position?


User confidence


Can employees find and use the information they need?


Manual corrections


Are employees spending less time fixing duplicate or inaccurate records?


Reporting reliability


Can management produce the required financial information with confidence?


Business continuity


Can essential transactions be processed correctly after go-live?


These outcomes matter more than the number of rows transferred.


Why clean data supports better Business Central adoption


Employees quickly form opinions about a new system.


If they log in and discover incorrect customer details, missing balances or duplicated suppliers, confidence can fall.


They begin questioning the information.


They check the old system.


They maintain spreadsheets.


They ask colleagues to confirm transactions.


The business now has additional administration.


But when the information is accurate and employees understand how to use it, the transition becomes easier.


Users are more likely to trust the system.


Routine tasks become more consistent.


Reporting becomes easier to validate.


That is why data migration and user adoption are closely connected.


A technically successful migration can still deliver poor business results if employees don't trust the information.


Final thoughts


Moving to Microsoft Dynamics 365 Business Central is an opportunity to improve how your business operates.


But the quality of the information you bring with you matters.


If you transfer every duplicate customer, outdated supplier, inconsistent product code and unnecessary historical transaction, the new system may inherit much of the complexity you wanted to leave behind.


A better approach starts with clear decisions.


What information is essential?


What needs cleaning?


What should remain accessible historically?


What must reconcile?


And what does the business actually need to operate successfully from day one?


The goal isn't to move the maximum amount of data.


It's to start Business Central with information your employees can trust and your business can build on.


People Also Ask


What is Business Central data migration?


Business Central data migration is the process of transferring relevant business information from an existing system into Microsoft Dynamics 365 Business Central. This may include customer and supplier records, financial accounts, opening balances and operational data.


Can you migrate data from Sage to Business Central?


Yes. Businesses can migrate relevant information from Sage into Business Central. The method depends on the Sage product, the data required and the agreed implementation scope.


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


Not necessarily. Some businesses migrate essential records and opening balances while retaining historical transactions in a separate accessible archive. The approach should reflect reporting, audit and record-retention requirements.


How long does Business Central data migration take?


The timeframe depends on data quality, volume, complexity and the migration method. Straightforward migrations can be included within a rapid core implementation, while larger or more complex requirements may take longer.


What should you clean before migrating to Business Central?


Review duplicate customers and suppliers, inactive records, incomplete information, inconsistent codes, financial structures and known data errors before migration.


How do you know whether a Business Central data migration was successful?


A successful migration should produce accurate records, reconciled financial balances and reliable information that employees can use to complete everyday business processes.


Further Reading


bottom of page