Dynamics 365 to Zoho CRM Migration: Mapping and Cutover Plan

What moves from Dynamics 365 to Zoho CRM, and what has to be rebuilt?

Records move. Logic does not. Accounts, contacts, leads, opportunities, activities, notes, products and most sales documents can be exported and imported with their relationships intact if you keep the Dynamics record IDs.

Business logic has to be rebuilt in Zoho terms. Power Automate flows and classic workflows become workflow rules, Blueprints or Deluge functions. Business process flows usually become Blueprints. Dynamics views, charts and dashboards become Zoho CRM custom views, reports and dashboards, or Zoho Analytics for cross-app reporting. Security roles and business units become Zoho CRM roles, profiles and, on editions that include it, territory management.

How do Dynamics 365 entities map to Zoho CRM modules?

Use this as a starting map, then confirm each field in a mapping sheet with the source column, target field, data type and any transformation.

Can Zoho CRM's migration tool import Dynamics data directly?

Yes, with preparation. In Zoho CRM, an administrator goes to Setup, then Data Administration, then Import, and chooses MS Dynamics as the source. Zoho's help page says the tool accepts CSV files only, either several CSVs or one zip file with no sub-folders. If you have a Dynamics backup in .BAK format, Zoho asks you to contact its migration team to convert it first.

The tool proposes module mappings, which you can change or point at a new module. It then lets you map fields, use Auto Map, replace empty mandatory values, set default values, and create new fields. The number of fields you can create depends on your edition, and autonumber and formula fields cannot be created this way. Only the first 10 tags per record are kept. If more than 5,000 records in a module are skipped, the migration pauses for your decision, and you can undo a migration from Import History.

Zoho's page lists users, leads, accounts, contacts, deals, campaigns, notes, activities, attachments, cases, solutions, products, quotes, sales orders, invoices, purchase orders, vendors and price books. It does not cover Dynamics custom entities, so plan those as custom modules loaded through the standard import. For larger or messier datasets, a Zoho CRM data migration project adds cleansing, test loads and reconciliation reports around this tool.

What happens to Outlook, Teams and email history?

Dynamics users are used to tracking email from Outlook. Zoho CRM has its own Microsoft options: an Outlook add-in, plug-ins for Outlook on Windows and Mac, synchronisation with Office 365, and a Microsoft Teams integration. Test the one you choose with a pilot group before cutover, and switch off Dynamics server-side synchronisation on the cutover day so emails are not tracked in both systems.

• Decide whether old email activities need to be searchable in Zoho CRM or only kept in an archive export.
• Agree a cut-off date, for example the last two years of email history, to keep the import manageable.
• Make sure each user's mailbox is connected in Zoho CRM before go-live, not after.

What does a safe cutover plan look like?

1. 1Freeze the Dynamics schema and agree the final mapping sheet.
2. 2Build Zoho CRM modules, fields, layouts, roles and profiles in a sandbox if your edition includes one.
3. 3Run a test import of a sample from every entity and reconcile record counts and totals.
4. 4Rebuild automation and run user acceptance testing with real scenarios.
5. 5Set a go or no-go point: counts match, key reports match, and no blocking defects remain.
6. 6On cutover day, set Dynamics to read-only for users, export the final delta and import it.
7. 7Keep Dynamics read-only for an agreed period, then take a full archive export before the licences end.

What should US, UK, EU, Gulf and Canadian teams plan for?

• Data location: Zoho hosts data in several regions, including the US, EU, India, Australia, Canada, Saudi Arabia, Japan and the UAE. Confirm which data centre your Zoho account uses before you load any data, and record it for your compliance file.
• UK and EU: under GDPR, migrate only the personal data you still have a reason to keep, and record the decision. Old leads and contacts with no lawful basis are better left in the archive.
• Licence overlap: Dynamics and Zoho licences usually run side by side during testing. Check your Microsoft renewal date early so the overlap is short.
• Gulf: if Arabic names or addresses are stored in Dynamics, test that the CSV export keeps UTF-8 encoding before the full import.

What mistakes should you avoid, and how does Flowpeak help?

• Importing everything, including years of dead leads and duplicate accounts.
• Loading child records before parents, which breaks lookups.
• Copying Dynamics logic step by step instead of redesigning it for Zoho.
• Leaving Outlook tracking until after go-live.

Flowpeak is a registered Zoho partner with Zoho certified consultants, delivering remotely from Chennai. We build the mapping sheet with you, run test loads, rebuild automation and handle the cutover weekend. Most Zoho CRM projects go live within two weeks; large data sets, integrations, complex workflows and Blueprints add time, and the quote says so in writing after a free scoping call. To review your Dynamics data before deciding, Book a free call.

Frequently asked questions