What we do
Tools
Industries
Department
How we workLet's talk →
Home/Dynamics 365/Dynamics 365 Data Migration Tools and Their Gaps
Dynamics 365

Dynamics 365 Data Migration Starts With What Microsoft's Tool Leaves Behind

Your GP company has twenty years of history, a reseller add-on that tracks equipment rentals, and a stack of user-defined fields the sales team relies on. Business Central's cloud migration brings over the accounts, customers, vendors and items, and runs a validation pass at the end. The rental add-on and those fields are a different job. Microsoft's tools for each path move the standard data model well. What you built on top of it needs its own plan.

Microsoft's migration route for each starting point

Moving from Microsoft's route What still needs its own plan
Dynamics GP, to Business Central online Cloud migration, set up per company on the GP Company Migration Configuration page and run from Cloud Migration Management. A validation step compares GP data with what arrived. Add-on and custom data outside GP's standard tables. GP's main account segment becomes the account number and the other segments become dimensions, and historical years arrive open, to be closed in Business Central.
Dynamics NAV or Dynamics SL, to Business Central online Microsoft's NAV and SL migrations to Business Central online. Customizations built into the old system. Business Central online takes extensions, so custom logic gets rebuilt, and the data it kept needs a target.
QuickBooks, to Business Central Microsoft's QuickBooks migration apps for Business Central. Confirm what the app brings over for your QuickBooks edition. Anything it skips, such as detailed history you still report from, needs a separate load or an archive.
An older ERP or homegrown system on SQL, to Business Central Custom migration from any SQL source, or configuration packages for setup and master data. The mapping is yours to design: which old table feeds which Business Central table, and what happens to records that don't fit.
Dynamics AX, to Finance and Operations The data management framework: data entities, data projects and packages, loaded through staging tables with field mapping. Custom AX tables and fields. An entity extended with new fields needs its mapping regenerated, and a custom table needs its own entity.
Salesforce or another CRM, to Dynamics 365 Sales No one-click path. The Configuration Migration tool moves configuration data between environments, not accounts, contacts and deals. Every record and custom field comes across through a mapped import, built for your old CRM's structure.

Data that goes missing without an error message

These don't fail the migration. They surface months later, in a report that no longer adds up.

Custom fields with no matching field

How you'll know: An old report or a saved view references a field nobody created in Dynamics 365.

Fix: List every custom field before cutover and give each one a home in Dynamics 365, or retire it on purpose with someone's sign-off.

Add-on data still sitting in the old database

How you'll know: The core ERP migrated, but rental, commission or service history from a reseller add-on didn't come with it.

Fix: Treat each add-on as its own source: find where its data lives, decide what Dynamics 365 needs, and load it with the main migration rather than after.

Rows an import skipped to keep going

How you'll know: Finance and Operations' data management can carry on with the good records and leave the rest in staging, and nobody went back for them.

Fix: Compare record counts per entity between source and target, and work through the staging errors before anyone signs off.

History whose meaning changed on the way

How you'll know: Reports built on GP's full account strings stop matching once the extra segments become dimensions in Business Central.

Fix: Rebuild those reports on accounts plus dimensions before go-live, and test them against last year's numbers.

Dynamics 365 migration questions before the cutover date

Does Microsoft provide a tool to migrate to Dynamics 365?

Yes, several, one per path. Business Central has cloud migration from GP, NAV, SL and Business Central on-premises, plus QuickBooks apps and a custom migration from any SQL source. Finance and Operations uses the data management framework. They handle the standard data model well; custom fields and add-on data need handling outside them.

Can I migrate from Salesforce or another CRM to Dynamics 365?

Yes, as a mapped migration project rather than a one-click import. Contact, account and deal structures rarely line up field for field between two CRMs, and years of custom fields need a home decided for each one.

What's the biggest risk in a Dynamics 365 migration?

Silent data loss: custom fields or non-standard records with no obvious place in Dynamics 365's default structure, dropped or mismapped without an error, and found months later.

What does the Configuration Migration tool move?

Configuration data for Dynamics 365's customer engagement apps, such as the custom entities that define how an app behaves, from one environment to another. Microsoft draws a line between that and end-user data like accounts and contacts.

Can we run the old system and Dynamics 365 at the same time during the switch?

Yes. n-frames can build a sync that keeps both systems in step during a phased cutover, which lowers the risk of moving everything at once. Our Dynamics 365 integrations page covers how that bridge runs and when it's retired.

Does n-frames do the Dynamics 365 data migration?

The part the standard tooling doesn't cover. n-frames maps your source system's custom fields and non-standard structures to Dynamics 365's model before anything moves, and verifies that the result matches. Microsoft's own migration paths and the Dynamics 365 setup itself stay with you and your Microsoft partner.

Let's talk

A Dynamics 365 cutover with nothing stranded in the old database

n-frames maps the custom fields and non-standard records your old system built up, moves them alongside Microsoft's standard migration, and checks the counts match before anyone signs off.

Custom data carried across →

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.