Power BI
25 min
Moving your business data into a new ERP system requires careful planning, especially when financial records, customer information, inventory, and supplier details are involved. Business Central data migration is more than transferring files from one platform to another. It involves reviewing existing information, deciding what should move, preparing data for the new system, and confirming that everything works correctly after migration.
Microsoft Dynamics 365 Business Central brings finance, sales, purchasing, inventory, and other business processes into one environment. A well-managed migration helps your team use accurate information from the beginning and reduces the risk of errors that can affect daily operations.
Whether you are moving from an older ERP platform, spreadsheets, or another business application, the following checklist can help organize the process and support a smoother transition.
Define the Migration Scope and Objectives
Before extracting any data, decide what your organization needs to move into Business Central. Transferring every historical record is not always necessary. Some information may be outdated, duplicated, or no longer useful for current operations.
Start by identifying the business areas included in the migration:
- Finance: General ledger accounts, opening balances, accounts receivable, accounts payable, and fixed assets.
- Customers and vendors: Names, addresses, contact details, payment terms, tax information, and account references.
- Inventory: Item numbers, descriptions, units of measure, costing methods, and inventory quantities.
- Sales and purchasing: Open sales orders, purchase orders, sales quotes, and relevant transaction details.
- Projects and jobs: Active project records, budgets, resources, and outstanding costs, where applicable.
- Historical records: Previous transactions and documents required for reporting, audits, or business reference.
Set clear objectives for migration. These might include improving financial reporting, reducing manual data entry, consolidating information from separate systems, or preparing the business for more accurate inventory management.
Document which records will be migrated, archived, or left behind. This decision helps control project effort and avoids moving unnecessary information. It also helps establish realistic migration timelines and ensures that important business and record-retention requirements are considered.
Audit and Clean Existing Data
Poor-quality source data is one of the most common causes of migration problems. If customer records contain duplicate names, supplier accounts have missing tax details, or inventory quantities are incorrect, transferring them without review can create confusion in Business Central.
Conduct a data audit before extraction. Review each source system and identify incomplete, outdated, inconsistent, and duplicated records.
Pay particular attention to the following:
- Duplicate customer and vendor accounts.
- Missing addresses, contact details, or payment terms.
- Inconsistent item numbers and product descriptions.
- Incorrect units of measure or inventory classifications.
- Invalid tax identification or registration details, where applicable.
- Unreconciled financial balances.
- Old records that no longer need to remain active.
Agree on data-cleaning rules with the departments responsible for the information. Finance should validate financial records, while inventory teams should confirm inventory details and item classifications.
Keep a record of the changes made during cleaning. This creates an audit trail and helps explain differences between the original system and the migrated records. It also provides a reference if discrepancies arise during testing or after the new system goes live.
Map Source Data to Business Central
Data mapping defines where each source field will be stored in Business Central. A customer record in an older application may contain information in a different format from the corresponding customer card in Business Central.
For example, one system may store a customer’s full address in a single field, while Business Central uses separate fields for street, city, postal code, and country or region.
Create a mapping document that identifies:
- The original system and source field.
- The corresponding Business Central table or field.
- Required formatting changes.
- Default values, if needed.
- Validation rules.
- Any fields that require manual review.
Pay attention to dependencies between records. Customer and vendor records may need posting groups, payment terms, currencies, and tax settings. Items may require item categories, costing methods, and units of measure.
The mapping process should also account for custom fields and extensions. If your existing ERP uses customized information, confirm whether Business Central can support it through standard functionality, configuration, or an extension.
Review the mapping with the relevant department owners before importing data. This helps identify missing fields, incompatible formats, and dependencies that could otherwise cause errors during migration.
Prepare the Business Central Environment
Do not begin importing data until the target environment is ready. Business Central needs the correct company setup, accounting structure, and operational configuration before migrated records can be validated properly.
Review the following areas:
Company and financial setup: Confirm company details, accounting periods, fiscal year settings, general ledger accounts, currencies, and number series.
Posting configuration: Check general posting groups, VAT posting groups where applicable, sales tax setup for US companies, customer posting groups, vendor posting groups, and inventory posting groups.
Inventory setup: Configure locations, units of measure, item tracking requirements, and costing methods where relevant.
User permissions: Assign suitable roles and access rights to employees responsible for migration and validation.
Extensions and integrations: Identify required extensions, external applications, and connections with systems such as CRM, payroll, e-commerce, or warehouse management systems.
Configuration should be reviewed with the relevant business teams. Incorrect posting setup can affect financial transactions even when the imported records appear complete.
For US-based organizations, pay particular attention to sales tax areas, tax jurisdictions, sales tax groups, and related configurations required for the company’s operations.
Extract and Import Data in the Correct Sequence
Once the data is cleaned and mapped, plan how it will move into Business Central. Microsoft provides configuration packages and data migration capabilities that can support imports for suitable records. Other migration requirements may need APIs, integrations, extensions, or specialist migration tools.
The appropriate method depends on data volume, complexity, source system structure, and the records being transferred.
Available migration approaches may include configuration packages, Excel-based imports, assisted data migration, and cloud migration tools for supported source systems. For more complex requirements, APIs, integrations, or third-party migration solutions may be appropriate.
Configuration packages can support the import of master data and certain transactional records. However, posted ledger entries have specific migration limitations and cannot simply be imported into their corresponding posted-entry tables using configuration packages. Opening balances and other financial information may need to be transferred through general journals or other appropriate posting processes, depending on the migration requirements.
A typical import sequence may include:
- Company and financial configuration.
- General ledger accounts and posting setup.
- Customers, vendors, and related records.
- Items, units of measure, and inventory locations.
- Opening balances and outstanding receivables or payables.
- Open sales orders and purchase orders.
- Other required operational or historical information.
The sequence matters because some records depend on other records already existing in the target environment. For example, an imported transaction may refer to a customer, item, or posting group that must be created first.
Do not assume that a successful file upload means the migration is complete. Review import messages, rejected records, field-level errors, and records that require manual correction.
Maintain an import log that records successful imports, failed records, corrections, and any manual adjustments. This makes it easier to track migration progress and investigate issues during validation.
Test the Migration Before Go-Live
Testing is essential because data can appear correctly in a new system while still producing incorrect business results.
Perform a trial migration in a test or sandbox environment before moving production data. Use representative records from different departments, including complicated transactions and unusual data cases.
Check the following:
- Customer and vendor records contain the correct information.
- Item descriptions, quantities, and units of measure match source records.
- Opening balances agree with approved financial statements and the source system’s trial balance.
- Accounts receivable and payable totals reconcile.
- Inventory quantities and values are accurate.
- Open orders show the correct items, quantities, and outstanding amounts.
- Users can access the records required for their roles.
- Reports display expected figures and classifications.
For financial validation, compare the trial migration results with the source system’s approved trial balance and relevant subsidiary ledgers. Also verify that accounts receivable, accounts payable, and inventory balances reconcile with their supporting records. Investigate differences rather than adjusting figures simply to make totals match.
Record each issue, assign responsibility, and repeat the test after corrections. Business users should approve the results for their respective departments before the final migration.
Testing should also cover key business processes, such as posting invoices, receiving inventory, processing payments, and generating financial reports. This confirms that the migrated data supports normal operations, not just that the records have been imported successfully.
Plan the Final Migration and Go-Live
A successful trial does not remove the need for controlled production migration. You need a clear plan for the final data extraction, import, validation, and transition to Business Central.
Create a go-live schedule that includes:
- A cutoff date for entering new transactions in the legacy system.
- A final backup of source data.
- The extraction and import sequence.
- Assigned responsibilities for each migration task.
- Financial and operational reconciliation checks.
- A process for handling failed imports.
- Approval from department leads before users begin working in the new system.
Consider how open transactions will be handled during the transition. If users continue entering orders, payments, or inventory movements in the old platform after the final extraction, the two systems may no longer show the same position.
Communicate the cutover date clearly. Employees should know when to stop using the legacy system and where to report problems.
It is also important to establish a contingency plan in case critical migration issues arise. Define who will make the go-live decision, how unresolved issues will be handled, and what steps should be taken if the transition needs to be delayed.
Validate Data After Migration
Post-migration validation confirms that information is accurate in the live Business Central environment. Do not rely only on import completion messages.
Finance teams should reconcile opening balances, customer accounts, vendor accounts, and general ledger totals. Inventory teams should compare quantities and values against approved inventory records. Sales and purchasing teams should review outstanding orders and customer or supplier information.
Also check that integrations, scheduled tasks, reports, and user permissions work as expected.
Confirm that connected applications are exchanging information correctly and that users can complete their regular tasks without unexpected errors.
Maintain a migration issue log during the initial operating period. Give each issue an owner, priority, and resolution status. This makes it easier to address problems before they affect more transactions.
Schedule follow-up reviews during the initial weeks of operation to identify recurring issues, confirm data accuracy, and make any necessary adjustments to the new environment.
Train Users and Maintain Migration Records
Employees need to understand how their work changes after the migration. Even accurate data may be underused if employees do not know where to find information or how to complete familiar tasks in Business Central.
Provide role-based training for finance, sales, purchasing, warehouse, and management teams. Use practical examples based on daily activities, such as posting an invoice, receiving inventory, reviewing customer balance, or creating a purchase order.
Keep important migration documents, including:
- Source-to-target mapping files.
- Data-cleaning records.
- Import logs and error reports.
- Reconciliation results.
- Testing approvals.
- Final migration sign-off.
- A list of known issues and resolutions.
These records support future audits, troubleshooting, and system improvements.
Make sure employees also know where to access training materials, user guides, and internal support resources. This helps them become familiar with Business Central and reduces dependence on external assistance for routine tasks.
How Cambay Solutions Can Support Business Central Migration
A successful ERP migration requires coordination between data preparation, application configuration, financial validation, and user readiness. Businesses must consider how information will move and how the new system will support their everyday processes.
Cambay SolutionsΒ provides Microsoft-focused services that include Dynamics 365 Business Central, implementation support, cloud solutions, data and analytics, and business application services. Its capabilities can help organizations assess their requirements and plan the technical and operational work involved in moving to Business Central.
From understanding existing data structures to planning the migration approach and preparing the new environment, businesses need a structured process that addresses both technical requirements and operational priorities. Working with an experienced Microsoft solutions partner can help organizations identify potential challenges, coordinate migration activities, and prepare their teams for the transition.
A structured business central data migration process gives your organization a stronger starting point. With clean records, tested imports, reconciled balances, and trained users, your team can begin using the system with greater confidence.
Planning to move your business data to Microsoft Dynamics 365 Business Central? Contact Cambay Solutions to discuss your migration requirements and explore how our Microsoft-focused services can support your ERP transition.
FAQs
- What data should be migrated to Business Central?
Common records include customers, vendors, items, chart of accounts, opening balances, outstanding invoices, open orders, and required historical information. The final scope depends on business needs.
- Can data be migrated from Excel to Business Central?
Yes. Suitable records can be imported from Excel using supported import methods, including configuration packages where applicable. Data must follow the required structure and validation rules.
- How do you prevent data errors during migration?
Clean source records, prepare accurate mapping documents, test imports in a sandbox, review error logs, and reconcile financial and inventory information before go-live.
- Should you migrate all historical transactions?
Not necessarily. Many businesses migrate essential opening information and outstanding transactions while retaining older records in an accessible archive. Retention and audit requirements should guide the decision.
- How long does Business Central data migration take?
The timeline depends on data volume, source system complexity, customizations, integrations, data quality, and testing requirements. A detailed assessment is needed to estimate the work accurately.
- What should you check after migration?
Verify financial balances, customer and vendor records, inventory quantities, open orders, user permissions, reports, and integrations. Obtain approval from the relevant department owners.