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.