Dynamics 365 Data Migration Checklist

Dynamics 365 Data Migration Checklist

Quick Summary

Data migration is often the riskiest workstream in a Dynamics 365 implementation. It succeeds when data is scoped, cleaned, mapped, loaded in rehearsals, and reconciled before cutover. This checklist takes you through each stage, with owners, tools, and checks, so finance, IT, and the project team can work from one plan.

Scope and Strategy

Start by deciding what the new system really needs.

  • ☐ List the data groups in scope: master data, opening balances, open transactions, and history.
  • ☐ Decide what to migrate, what to archive, and what to leave behind.
  • ☐ Agree on how long history must be available and where it will live.
  • ☐ Define the migration approach: one load at cutover or phases by entity or business unit.
  • ☐ Confirm the target Dynamics 365 apps, since tools and rules differ by app.
Data groupExamplesCommon approach
Master dataCustomers, vendors, items, accountsMigrate after cleansing
Opening balancesGeneral ledger, bank, customer, and vendor balancesMigrate and reconcile with finance
Open transactionsOpen orders, open invoices, open purchase ordersMigrate what is still active
HistoryClosed transactions, documentsOften archived, not migrated

For help deciding whether you need an implementation, a migration, or both, read our guide to implementation vs migration.

Data Inventory and Ownership

  • ☐ List every source system, file, and spreadsheet that holds data in scope.
  • ☐ Record volumes, formats, and known problems for each source.
  • ☐ Name a business owner for each data set, not only a technical owner.
  • ☐ Agree who approves decisions about the data.
  • ☐ Record data protection and access requirements for the migration itself.

Cleansing and Quality Rules

Cleansing usually takes longer than people plan. Start early.

  • ☐ Define quality rules for each data set: required fields, formats, valid values, and duplicates.
  • ☐ Profile the data to measure how much needs fixing.
  • ☐ Remove duplicates and inactive records as agreed with the owner.
  • ☐ Fix data in the source where possible so that fixes survive each load.
  • ☐ Track cleansing progress and sign-off for each data set.
  • ☐ Decide how to treat records that cannot be fixed in time.

Mapping and Transformation

  • ☐ Map every source field to a target field in Dynamics 365.
  • ☐ Record defaults for fields that have no source.
  • ☐ Define code translations, for example, old account codes to new ones.
  • ☐ Define transformation rules, such as splitting or combining fields.
  • ☐ Review the mapping with the process owners, not only with technical staff.
  • ☐ Keep the mapping document under version control.

Use a simple mapping table:

Source fieldTarget fieldRule or defaultOwnerStatus

Tools and Methods by Application

The right tool depends on the app and the data. Check current names and capabilities on Microsoft Learn before you decide, because tools change.

ApplicationCommon options
Finance and Supply Chain ManagementData management framework and data entities
Business CentralConfiguration packages and other import tools
Customer engagement apps (such as Sales and Customer Service)Dataverse import and integration tools

Choose the tool by volume, complexity, and the skills of your team. For very large or complex loads, teams often add an extract, transform, and load tool. Whatever you choose, make the load repeatable, so you can run it many times.

Mock Loads and Rehearsals

One load is rarely enough. Plan several rehearsals:

  1. Load a set of data into a test environment.
  2. Validate the results with counts, totals, and spot checks.
  3. Fix problems in the source, the mapping, or the load process.
  4. Repeat until results are stable and signed off.
  • ☐ Plan at least one full rehearsal with production-sized data.
  • ☐ Time each load to plan the cutover window.
  • ☐ Log every issue with an owner and a fix.
  • ☐ Involve business users in checking results.

Reconciliation and Sign-Off

Reconciliation proves that the data in the new system matches the old one.

  • ☐ Compare record counts for each entity.
  • ☐ Compare control totals and balances, including opening balances by account.
  • ☐ Reconcile customer and vendor balances to the ledger.
  • ☐ Check open transactions against source reports.
  • ☐ Have business owners sample records and run key reports.
  • ☐ Record results and obtain written sign-off for each data set.

Finance teams often feel most pressure around opening balances and open transactions. Agree the reconciliation method with them early.

Cutover

  • ☐ Agree on the freeze window, when users stop changing data in the old system.
  • ☐ Write the cutover plan with tasks, owners, timings, and dependencies.
  • ☐ Plan the final extract and load and how changes during cutover (the delta) will be handled.
  • ☐ Define rollback criteria and the steps to go back.
  • ☐ Rehearse the cutover at least once.
  • ☐ Confirm who makes the go or no-go decision.
  • ☐ Confirm who checks the results and signs them off.

After Go-Live

  • ☐ Monitor data quality and error logs in the first weeks.
  • ☐ Set up a way for users to report data problems, with owners.
  • ☐ Correct issues in a controlled way, not with uncontrolled edits.
  • ☐ Confirm that archived data can be found and read.
  • ☐ Set rules to keep data clean in the new system, with owners and checks.
  • ☐ Record lessons learned for the next wave or project.

Roles and Responsibilities

RoleMain responsibilities
Executive sponsorRemoves blockers, approves scope, and goes or no-go
Data owner (business)Decides what to migrate, owns quality, and signs off on results
Finance leadOwns balances, reconciliation, and sign-off for financial data
Migration leadPlans the workstream, manages rehearsals, and issues
Technical consultantBuilds and runs the load processes and tools
Functional consultantAdvises on target fields, setup, and dependencies
Test leadPlans validation with business users

Common Dynamics 365 Data Migration Problems and Fixes

  • Duplicates in the source. Customers or items exist twice. Fix in the source and agree on a rule for which record survives.
  • Missing required fields. The target needs data the source never had. Agree to defaults or collect the data.
  • Code mismatches. Old codes do not match new ones. Build and review a translation table.
  • Load errors that repeat. The same record fails in every rehearsal. Fix the root cause, not just the record.
  • Balances that do not reconcile. Check timing, rounding, currency, and posting rules, and involve finance early.
  • Data changed during cutover. Plan how to capture and load changes after the extract.
  • Loads that run too long. Time every rehearsal and adjust the method or the window.
  • No one owns the issue. Give every defect an owner and a due date.

How a Migration Workstream Is Usually Structured

Migration plans differ, but most follow the same stages: scope and inventory, cleansing and mapping, build and first load, rehearsals and reconciliation, final cutover load, and hypercare corrections. Put dates on each stage only after you know your data volumes and quality. Share the stages with your sponsor, and review them whenever a rehearsal shows a problem.

Questions to Ask a Partner About Data Migration

  1. Who does the cleansing, and what do you expect from our team?
  2. Which tools will you use for our apps, and why?
  3. How many rehearsals are included in the scope?
  4. How will you reconcile balances and who signs off?
  5. How will you handle changes during cutover?
  6. What happens if a rehearsal fails close to go-live?
  7. How do you treat history: migrate, archive, or leave behind?

If you are comparing partners, see our guide to choosing a Dynamics 365 partner.

What Your Own Team Must Do

Even with a partner, certain tasks belong to your team: deciding what to migrate, owning data quality, approving mapping, validating results, and signing off. A partner can design the process and run the tools, but only the business can say what the data should look like. Plan time for those people, because a shortage of business time is one of the common causes of delay.

For a broader view of project responsibilities and readiness, refer to our Dynamics 365 Implementation Checklist

What Drives the Cost of Data Migration?

Data work is often a major cost driver in an implementation. The main factors are the number of source systems, the volume and quality of the data, how much mapping and transformation is needed, the number of rehearsals, and how much history you bring. We do not quote prices here because each project differs. When you compare partner proposals, check that data cleansing, mapping, rehearsals, and reconciliation are included and clearly scoped.

Download the Checklist

Get this checklist as an editable spreadsheet with owner, status, and evidence columns for each step.

Next Step

Planning a Dynamics 365 project with a data migration? Talk to our team about Dynamics 365 implementation services.

Conclusion

Data migration succeeds when it is treated as a project of its own: scoped, owned, cleaned, rehearsed, and reconciled. The business owns the data, and the partner provides the method and the tools.

Start early, rehearse several times, and do not go live until balances reconcile and the owners have signed.

FAQs

How do I migrate data to Dynamics 365?

Plan the scope and inventory, clean your data, map it to the target fields, load it with the tools that suit your app, run several mock loads, reconcile each one, and then run a rehearsed cutover. Business owners should sign off the results.

What data should be migrated to Dynamics 365?

Usually master data such as customers, vendors, and items, opening balances, and open transactions. Whether to bring historical transactions depends on need, cost, and rules for retention. Many teams archive history instead of loading it.

What tools are used for Dynamics 365 data migration?

It depends on the app. Common options include the data management framework and data entities in Finance and Supply Chain Management, configuration packages in Business Central, and Dataverse tools for customer engagement apps. Verify current names and capabilities on Microsoft Learn.

How long does Dynamics 365 data migration take?

It depends on the volume of data, its quality, the number of source systems, how much mapping is needed, and how many rehearsals you run. Be cautious of any single number that ignores your data. Ask for an estimate with assumptions.

How do you validate migrated data?

Compare record counts and control totals and balances between source and target, then have business owners check samples and run key reports. Record the results and sign-off for each load.

What is a data migration cutover plan?

A cutover plan lists the steps, owners, and timings for the final data load: when the old system is frozen, how the last data is extracted and loaded, how changes made during the cutover are handled, how results are checked, and when to roll back.

Related Posts