Dynamics 365 to Zoho CRM migration
We migrate Accounts, Contacts, Leads, Opportunities, Quotes, and activity history from Microsoft Dynamics 365 Sales into Zoho CRM with the .BAK-to-CSV export bridge handled first, parent-record lookups resolved before import, and every Dynamics entity mapped to the correct Zoho module before cutover.
FlitStack AI migrates accounts, contacts, leads, potentials and quotes from Dynamics 365 to Zoho CRM, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 4-6 weeks.

What moves from Dynamics 365 to Zoho CRM?
Moving from Microsoft Dynamics 365 Sales to Zoho CRM requires navigating two structural incompatibilities that most migrations miss.
Read the full summary
First, Dynamics 365 exports database data in .BAK (SQL backup) format while Zoho CRM accepts only .CSV; we bridge this with a Dataverse-to-CSV export pipeline that flattens the relational schema into importable rows before any data lands in Zoho. Second, Dynamics 365 organizes activities as Dataverse activitypointer records with polymorphic PartyList fields (regardingobjectid), whereas Zoho Activity records require explicit activitytype, subform linkage, and no equivalent of the Regarding field. We resolve the parent-record chain (Contact to Account, Opportunity to Account, Activity to Regarding) before each batch inserts so no activity is orphaned. Territory hierarchies, custom tables above the Professional 15-table ceiling, and Power Automate workflows do not migrate; we deliver a written schema map for the admin to rebuild territories as Zoho Custom Fields or Tags and document every active Power Automate flow requiring Zoho Blueprint or custom function translation.
Account → Accounts
Dynamics 365 Account maps directly to Zoho CRM Accounts.
How it maps
The primarycontactid lookup resolves to a Zoho Contact that we insert after the Account using name-based matching on email domain and account name as deduplication keys. Address fields (postaladdress, shippingaddress) migrate as plain-text address fields in Zoho's address composite. Industry and Account type map to Zoho's Account Type and Industry picklist fields.
Contact → Contacts
Dynamics 365 Contact maps to Zoho CRM Contact.
How it maps
The parentaccountid lookup is resolved by matching the Dynamics accountid to the Zoho Account inserted in the previous phase. Email address is the primary deduplication key; duplicate contacts with matching email addresses receive a -migration-suffix and are flagged in the reconciliation report for admin review. Mobile phone, phone, title, and department map directly to Zoho standard fields.
Lead → Leads
Dynamics 365 Lead maps to Zoho CRM Leads with leadstatus, lead source, and industry preserved.
How it maps
The leadscore (if present as a custom field) migrates to a Zoho numeric field. Qualification status from Dynamics leadqualitycode maps to Zoho Lead Status. Unlike HubSpot, Dynamics does not auto-convert Leads to Contacts; the Lead object exists separately from Contact in both platforms, so no split logic is required.
Opportunity → Potentials (Deals)
Dynamics 365 Opportunity maps to Zoho CRM Potentials (the Deal module).
How it maps
The parentaccountid lookup resolves via account name match. The estimatedvalue and actualclosedate fields map to Amount and Closing Date. Pipeline stage from Dynamics stagecode maps to Zoho Stage using a migration-time lookup table built during scoping. Closed-Won and Closed-Loss reasons map to Zoho custom fields if they exist in Dynamics as custom attributes.
Quote → Quotes
Dynamics 365 Quote maps to Zoho CRM Quotes.
How it maps
The quotenumber, totalamount, and discount fields migrate directly. Quote status (draft, active, revised, closed-won, closed-lost) maps to Zoho Quote Status. If the Dynamics Quote has line items, each product reference is resolved to a Zoho Product record before the Quote is inserted. Quote PDFs do not migrate as files; they are flagged for regeneration in Zoho.
Order → Quotes (as Orders)
Microsoft Dynamics 365 Sales Order maps to Zoho CRM Quotes with a Quote Status set to Closed Won or a custom Order layout if configured.
How it maps
Zoho CRM does not have a native separate Orders module without Zoho Books integration. We set a custom field dyn_orderid__c to carry the Dynamics orderid for audit traceability. If the customer has Zoho Books enabled, Orders migrate to the Zoho Books Purchases or Sales module instead.
- AccountAccounts1:1
- ContactContacts1:1
- LeadLeads1:1
- OpportunityPotentials1:1
- QuoteQuotes1:1
- OrderQuotestransformed
+ 5 more in the mapping below
How Dynamics 365 and Zoho CRM differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Dynamics 365 | Zoho CRM |
|---|---|---|
| Lead lifecycle | Separate Lead and Opportunity entities with distinct qualification stages | Lead converts directly to Potential (Deal) with a conversion action and no intermediate Contact required |
| Commercial documents | Separate Quote, Order, and Invoice entities with explicit parent-child relationships | Single Quote module handles Quotes and Orders; Invoices require Zoho Books integration (separate product) |
| Custom tables | Professional tier caps at 15 custom tables; Enterprise and Premium allow unlimited | Custom Modules available from Standard tier; per-module field limits apply based on edition |
| Pricing model | Per-user-per-month with mandatory $15 increase from October 2024; implementation partner fees add 30-50% | Per-user-per-month starting at $50 Standard, $65 Enterprise, $80 Ultimate; no mandatory partner required |
| Activity linkage | Activitypointer with polymorphic Regarding (regardingobjectid) pointing to any entity | Activities tied explicitly to module records (Contacts, Accounts, Deals) via subform relationship |
| Data export format | Dataverse .BAK SQL backup format; Web API returns JSON | CSV import only; no native bulk JSON ingest endpoint |
| Territory model | Enterprise tier territory hierarchy with assignment rules | Custom Fields, Tags, or lookup modules to simulate geographic or team-based territory |
What to watch for in a Dynamics 365 to Zoho CRM migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Dynamics exports .BAK format; Zoho accepts only CSV
Dynamics 365 stores data in a Dataverse SQL database and exports via .BAK backup format, while Zoho CRM's native migration tool and API accept only .CSV files.
How we handle it
There is no direct pipeline between the two platforms. We resolve this by extracting data from Dynamics via the Dataverse Web API (JSON), transforming the relational schema (resolving lookups to display names or IDs) into denormalized CSV rows, and loading via Zoho's bulk import API with field mapping. We validate row counts and referential integrity after each module extraction before committing to the CSV layer.
Dynamics Professional 15-custom-table ceiling blocks migrations without Enterprise
Microsoft Dynamics 365 Sales Professional enforces a hard cap of 15 custom tables.
How we handle it
Organizations running more than 15 custom tables cannot extract and import records associated with tables above the limit without upgrading to Enterprise ($105/user/month) or consolidating the schema. We detect the exact table count during scoping. If the ceiling is exceeded, we present a consolidation plan (merge or drop tables) before migration begins, or advise an Enterprise license procurement as a prerequisite.
Activity Regarding field requires pre-resolution before Zoho insert
Dynamics 365 activities use a polymorphic regardingobjectid (activitypointer) that can reference any entity in the system.
How we handle it
Zoho CRM Activities must be explicitly linked to a WhatId (Account or Potential) or WhoId (Contact or Lead) at insert time. Without pre-resolution, activities insert with no parent linkage and appear orphaned in the Zoho timeline. We resolve the regardingobjectid chain by querying the target entity in Zoho by name or email match before each activity batch inserts, and we flag any activity whose parent record was not found in a migration-gap report.
Custom fields must be pre-created in Zoho before API writes
Zoho CRM does not create custom fields via its API during import; fields must exist in the Zoho layout before records referencing them can be inserted.
How we handle it
We coordinate with the customer's Zoho admin to pre-create all mapped custom fields during the staging window, or we document each missing field for addition before the production import run. Dynamics has the same requirement for custom fields through the UI, which we handle in parallel during the same staging phase.
Territory hierarchies have no direct Zoho equivalent
Microsoft Dynamics 365 Sales Enterprise territory management uses a hierarchical territory model with assignment rules that map Leads and Opportunities to geographic or team-based territories.
How we handle it
Zoho CRM does not have a native territory module. We map territory names to Zoho Custom Fields (text or picklist) or Tag assignments, and we document the full territory hierarchy as a written map so the customer's admin can configure Zoho's Blueprint or role-based views to simulate territory-based routing. If territory-based assignment rules are critical, they require Zoho custom functions or a Zoho Flow add-on.
How the migration runs
Discovery and environment assessment
We audit the source Dynamics 365 environment across tier (Professional, Enterprise, Premium), custom table count, active workflows and Power Automate flows, Dataverse entity relationships, and total record counts per entity.
What this step covers
We assess the target Zoho CRM edition and existing modules against the migration scope. The discovery output is a written migration scope document identifying the .BAK-to-CSV extraction complexity, the custom table consolidation requirement (if applicable), the activity regarding resolution scope, and the territory rebuild strategy.
Dataverse extraction and CSV transformation
We extract data from Dynamics 365 via the Dataverse Web API using batched GET requests with $select and $expand clauses to resolve lookup relationships during extraction rather than post-extraction.
What this step covers
Each entity (Account, Contact, Lead, Opportunity, Quote, Product, Activity) is extracted as a separate JSON payload, denormalized to flatten lookup GUIDs into display names or email addresses, and transformed into CSV files matching Zoho's import column headers. We validate row counts against Dynamics entity counts before proceeding.
Zoho schema pre-creation and staging import
We work with the customer's Zoho admin to pre-create all target custom fields, Custom Modules, and Price Books in the Zoho staging environment.
What this step covers
We then run a staging import of each module's CSV with mapping validation, record rejection analysis, and parent-lookup verification. Any missing custom fields or picklist values are added to Zoho and the staging import re-run. This phase runs in a non-production Zoho sandbox if available.
Activity parent-record resolution
We resolve the Dynamics activitypointer regardingobjectid chain before migrating activities.
What this step covers
For each activity record, we identify the referenced entity type and GUID, query the corresponding Zoho module (Accounts, Contacts, Potentials, or Leads) by the extracted name or email field, retrieve the Zoho record ID, and inject it as the WhatId or WhoId in the activity CSV. Activities whose parent record was not found (due to the parent record being excluded from migration) are written to a separate gap report for admin review.
Production migration in dependency order
We run production migration in record-dependency order: Accounts first (base for Contacts), Contacts (with Account name match), Leads, Potentials (with Account and Contact lookups resolved), Products and Price Books, Quotes and Orders, then Activities.
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins. We use Zoho's bulk import API with batch sizes of 1,000 records per request and configurable concurrency to stay within Zoho's API rate limits.
Cutover, validation, and automation rebuild handoff
We freeze Dynamics 365 write access during cutover, run a final delta migration of any records modified during the migration window, then enable Zoho CRM as the system of record.
What this step covers
We deliver the Power Automate and Workflow inventory document mapping each Dynamics automation to a Zoho Blueprint, Workflow Rule, or custom function equivalent. We support a one-week hypercare window for reconciliation issues. We do not rebuild Dynamics automations in Zoho as part of the standard migration scope; that work is documented for the customer's admin team.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, custom table count, and the complexity of the .BAK-to-CSV export pipeline needed to bridge Dynamics Dataverse to Zoho's import format. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Dynamics 365 to Zoho CRM →Why teams move from Dynamics 365 to Zoho CRM
- Cost predictability and licensing efficiency drive the switch. Microsoft Dynamics 365 Sales Professional at $65 per user per month with a mandatory $15 increase from October 2024 represents a 23% price shock that applies at renewal. Zoho CRM Standard at $50 per user per month with no mandatory implementation partner and no per-feature tier gates provides a lower total cost of ownership for SMB teams that do not require deep Microsoft ecosystem integration.
- Implementation partner dependency inflates Dynamics total cost. Reviewers on Reddit and Capterra consistently cite mandatory certified partner involvement for proper configuration as adding 30-50% to the total project cost beyond licensing fees. Zoho's UI-driven setup and self-service administration enable in-house teams to configure the system without certified implementation partners, reducing the upfront investment required to get the CRM operational.
- Simpler interface and faster workflow configuration attract teams migrating from Dynamics complexity. A Reddit reviewer in the r/CRM community noted that what took hours in Dynamics took minutes in Zoho for equivalent CRM tasks, citing workflow setup and pipeline management as the most dramatic differences. Zoho's drag-and-drop pipeline interface and Blueprint automation model require less specialized knowledge compared to Dynamics 365's role-based security model and Dataverse dependency.
- Outgrowing the Professional 15-custom-table ceiling forces an Enterprise upgrade or migration. Teams on Microsoft Dynamics 365 Sales Professional who have built more than 15 custom tables cannot migrate those records to another Professional-tier system without either upgrading to Enterprise ($105/user) or simplifying the schema. Zoho Standard tier provides Custom Modules with no hard table ceiling at a lower per-user price, making it a natural landing point for organizations exiting Dynamics Professional due to the table limit.
- Performance and adoption challenges push teams away from Dynamics at scale. Reviewers cite performance degradation with large datasets and complex customer journeys, particularly in multi-module Dynamics environments. Zoho CRM's lightweight architecture and consistent UI reduce the learning curve for sales teams without dedicated IT support, addressing the adoption friction that Dynamics' steep learning curve creates.
Questions, answered
Dynamics 365 to Zoho CRM migration questions
How long does a Microsoft Dynamics 365 Sales to Zoho CRM migration take?
Most migrations land between four and six weeks for accounts under 15,000 total records with no custom tables above the Professional ceiling and clean parent-child relationships. Migrations with 15+ custom tables (requiring schema consolidation or Enterprise procurement), large activity histories (over 200,000 rows), or multi-currency price list structures move to eight to twelve weeks because of Dataverse extraction overhead, CSV transformation complexity, and territory-rebuild documentation scope.
Do Power Automate workflows and business rules migrate to Zoho CRM?
No. Power Automate workflows and Dynamics 365 business rules are configured at the platform level and do not have a standard portable representation. Zoho CRM uses Blueprint and Workflow Rules as its automation model, which are architecturally different from Dynamics flows. We deliver a written inventory of every active Power Automate flow and business rule with its trigger, conditions, and actions, along with a recommended Zoho Blueprint or Workflow Rule equivalent. The customer's admin team or a Zoho partner rebuilds them post-migration.
Why is the .BAK export format a problem for Zoho migration?
Dynamics 365 stores data in a Dataverse SQL database. The standard export path produces a .BAK SQL backup file, which is a binary database snapshot that requires a SQL Server instance to restore and query. Zoho CRM accepts only .CSV files for import. We resolve this by using the Dynamics Dataverse Web API (not the .BAK file) to extract data as JSON, transform it into denormalized CSV rows with resolved lookup fields, and load via Zoho's bulk import API. The .BAK file is never used in our extraction process.
Do we lose activity history (tasks, emails, calls, meetings) during migration?
No, with one qualification. We migrate the full activity history from Dynamics 365 using the Dataverse Web API. The primary technical challenge is resolving the polymorphic regardingobjectid field that can point to any entity. We pre-resolve each activity's parent record by matching the referenced entity name or email against the Zoho Accounts, Contacts, or Potentials tables before inserting, so activities land in the correct Zoho subform. Any activity whose parent record was not migrated is written to a gap report for manual reassignment.
How do we handle territories when migrating from Dynamics Enterprise to Zoho?
Microsoft Dynamics 365 Sales Enterprise territory management uses a hierarchical territory model that has no direct Zoho CRM equivalent. We map territory names to Zoho Custom Fields (text picklist) or Tag assignments and deliver a written territory hierarchy map documenting the original parent-child territory relationships. The customer's admin can configure Zoho Blueprint stages or role-based layouts to approximate territory-based routing. If territory assignment rules are critical to the sales process, they require Zoho custom functions as a separate customization engagement.
What happens to our Dynamics 365 custom tables if we are on the Professional tier?
If your Microsoft Dynamics 365 Sales Professional environment has more than 15 custom tables, you cannot migrate records associated with tables above the 15-table ceiling without either upgrading to Enterprise ($105/user/month) or consolidating the schema. We identify the exact table count during scoping. If consolidation is required, we present a merge or drop plan before migration begins. If Enterprise procurement is the chosen path, we advise the license upgrade as a prerequisite and proceed with a full custom-table migration once the tier is confirmed.
Can we pilot Zoho CRM with a subset of data before full migration?
Yes. We recommend a staging import into a non-production Zoho environment as a validation step before production cutover. We run the full migration in staging first, reconcile record counts and field mapping with the Dynamics source, and provide a reconciliation report for the customer's admin to review. Only after written sign-off on the staging results do we proceed to production migration. This approach catches mapping errors (wrong field types, missing picklist values, custom field gaps) before any data lands in the live Zoho CRM.
Related migrations
Zoho CRM implementation
Set up Zoho CRM and migrate into it as one engagement.
See the service → Zoho CRM to Dynamics 365The same pair in reverse Insightly CRM to Zoho CRMMapping · history · rollbackOdoo CRM to Zoho CRMMapping · history · rollbackServiceTitan to Zoho CRMMapping · history · rollbackmonday CRM to Zoho CRMMapping · history · rollbackPipedrive to Zoho CRMMapping · history · rollbackActiveCampaign to Zoho CRMMapping · history · rollback Dynamics 365 to FreshsalesMapping · history · rollbackDynamics 365 to monday CRMMapping · history · rollbackDynamics 365 to Odoo CRMMapping · history · rollbackSources: official documentation
- How to Migrate from Salesforce to Zoho CRM — zoflowx
- Data Migration: An Introduction — Zoho CRM
- Standard Modules & Fields — Zoho CRM
- Custom Modules — Zoho CRM
- Dynamics 365 environment strategy — Microsoft Learn
- Import accounts, leads, or other data — Microsoft Learn (Dynamics 365)
- Import data (all record types) — Power Platform | Microsoft Learn
Get a quote
Moving from Dynamics 365 to Zoho CRM?
Tell us roughly how many records and objects you have. We scope the mapping and the Zoho CRM setup with you, then send a quote.
Get a quote