Dynamics 365 Marketing to Zoho CRM migration
We migrate Contacts, Leads, Accounts, Potentials, and Activity history from Dynamics 365 Marketing into Zoho CRM with the Dataverse schema resolved to Zoho module equivalents, the BAK export format barrier handled before import, and every marketing email template and Customer Journey documented for rebuild in Zoho Marketing Automation.
FlitStack AI migrates lead or contacts, accounts, potentials, leads and products from Dynamics 365 Marketing 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 Marketing to Zoho CRM?
Moving from Dynamics 365 Marketing to Zoho CRM is a multi-layer migration: transactional CRM data (Contacts, Leads, Accounts, Opportunities) lives in Dataverse and maps directly to Zoho modules, while marketing-specific assets (email templates, Customer Journey definitions, segment memberships) are stored in msdynmkt-prefixed tables under Customer Insights and require separate export and rebuild in Zoho Marketing Automation.
Read the full summary
The primary export format from Dynamics is .BAK (SQL Server backup) or Dataverse bulk export; Zoho CRM's built-in migration tool accepts only CSV, so we handle the format conversion before any import. We sequence the migration as Accounts first, then Contacts and Leads, then Potentials, then Activities, with a separate pass for attachments and a documented handoff for marketing automation assets. Workflows, Customer Journey triggers, segment definitions, and marketing email assets do not migrate as code; we deliver a written rebuild guide for each.
Contact → Lead or Contact (split required)
Dynamics 365 CRM contacts map to Zoho CRM Lead or Contact depending on the lifecycle state.
How it maps
Contacts that represent active customers or sales-qualified records land as Zoho Contacts attached to an Account. Prospects and unqualified records land as Zoho Leads. We compute the split using the contact's statecode and statuscode from Dataverse and preserve the original status as a custom field original_contact_state__c on both Lead and Contact for audit. Account lookup must resolve before Contact import, so we sequence Accounts first.
Account (Company) → Account
Dynamics 365 Accounts map directly to Zoho CRM Accounts.
How it maps
The accountid becomes the Zoho Account lookup anchor. We preserve industry, address fields, annual revenue, number of employees, and account hierarchy where the destination Zoho edition supports parent-account lookups. Account is created before any Contact import so that Contact-to-Account lookups are satisfied at insert time.
Opportunity → Potential
Dynamics 365 Opportunities map to Zoho CRM Potential.
How it maps
StageName from Dynamics maps to Potential Stage, with the stage probability mapping adjusted to Zoho's percentage scale (Dataverse uses decimal; Zoho uses integer). EstimatedCloseDate, Amount, and OwnerId transfer directly. We configure the Zoho sales pipeline stage values before migration so that incoming Opportunity stages are whitelisted in the destination.
Lead (Dynamics CRM) → Lead
Dynamics 365 Leads (separate from Contacts, representing pre-qualification records) map directly to Zoho CRM Lead.
How it maps
Lead quality score, lead source, and any custom lead fields migrate to Zoho Lead custom fields. We map lead status from Dynamics lead status values to Zoho Lead Status values during the transform step before CSV generation.
Product → Product
Dynamics 365 Products map to Zoho CRM Products with Standard Price Book entries created during import.
How it maps
The product code, unit price, product category, and description migrate to Zoho Product fields. If Zoho uses a different currency model, we apply currency conversion at migration time using the customer's specified exchange rate.
Custom Field → Custom Field
Custom fields on any Dynamics 365 entity must be defined in the destination Zoho CRM schema before data values can be imported.
How it maps
We extract the custom field definitions from the Dataverse managed solution schema (not from UI exports), create equivalent Zoho custom fields via Setup > Customization > Fields, and map Dataverse field types (option set, two options, decimal, integer, text) to their Zoho type equivalents. Custom field creation happens in the Zoho Sandbox org before data migration begins.
- ContactLead or Contactsplit
- AccountAccount1:1
- OpportunityPotential1:1
- LeadLead1:1
- ProductProduct1:1
- Custom FieldCustom Fieldtransformed
+ 6 more in the mapping below
How Dynamics 365 Marketing 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 Marketing | Zoho CRM |
|---|---|---|
| Contact and Lead model | Separate marketing contacts (msdynmkt_) and CRM contacts (Dataverse) with lifecycle split across two systems | Leads and Contacts as separate CRM modules; marketing lists and campaigns as separate Marketing Automation product |
| Pricing model | Per-tenant Marketing at $1,500/month plus per-user CRM seats from $65/user/month | Per-user from $20/user/month; Marketing Automation is a separate product from $50/month |
| Custom objects | Custom Dataverse entities via managed solution schema; requires Configuration Migration Tool | Custom fields per module via Setup > Customization; custom modules available from Enterprise tier |
| Marketing automation | Customer Insights - Journeys with AI Copilot, segment builder, and Journey designer | Zoho Marketing Automation (separate product) with workflow automation, web forms, and email campaigns |
| Export format | Dataverse bulk export or SQL .BAK backup file; Configuration Migration Tool for schemas | Zoho built-in importer accepts CSV only; third-party tools required for non-CSV sources |
| Attachment storage | Annotations linked via objectid and objecttypecode; shareable via SharePoint integration | Attachments stored as Zoho CRM file uploads linked to record ID; no native SharePoint connector |
| Activity timeline | ActivityPointer with type-specific child tables (Email, Task, PhoneCall, Appointment) in Dataverse | Calls, Events, Tasks, and Emails as separate Zoho CRM modules with activity date preserved |
What to watch for in a Dynamics 365 Marketing 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 export format is incompatible with Zoho's CSV-only importer
Dynamics 365 Marketing exports transactional data as Dataverse bulk export files or SQL .BAK backup files, while Zoho CRM's built-in migration tool (Setup > Data Administration > Import) accepts only .CSV format.
How we handle it
Third-party migration tools such as Skyvia can bridge the format gap, but the Zoho native importer requires manual CSV preparation. We handle the format conversion using Dataverse export utilities to generate properly typed CSV files before any import begins. Migrations that attempt to use Zoho's built-in Microsoft Dynamics import connector directly without format preparation encounter data type mismatches and rejected rows.
Marketing automation is a separate product with no direct asset migration
Dynamics 365 Customer Insights - Journeys and Zoho Marketing Automation are separate products with incompatible workflow engines, segment builders, and email template formats.
How we handle it
Email templates, Customer Journey definitions, segment memberships, and marketing list logic cannot be imported as data into Zoho Marketing Automation. We export these assets as written specification documents for the customer's marketing team to rebuild. Teams that rely heavily on Customer Insights Journeys should budget additional time for the marketing automation rebuild phase after the CRM migration is complete.
Marketing Contact billing exposure at migration time
Dynamics 365 Marketing charges per tenant for Marketing Contacts regardless of whether the contact is actively used in a Journey.
How we handle it
Any Contact record that qualifies as a Marketing Contact based on email domain or interaction history counts against the tenant billing meter. When migrating Contacts into Zoho CRM, we flag records that should be classified as non-marketing during the scoping phase to prevent unintended Dynamics billing exposure after the migration window closes. We recommend a billing review before the migration cutover date.
Custom Dataverse entities require managed solution schema, not UI export
Custom entities created in Dynamics 365 require the managed solution ZIP or Configuration Migration Tool schema export to capture field types, relationship metadata, and validation rules.
How we handle it
A UI-based export from Dynamics 365 Marketing does not include these properties and will produce an incomplete schema definition. We require the customer to provide the managed solution file or schema export before custom entity mapping begins. Zoho CRM custom fields are created per module in Setup > Customization, and the field types must match the Dataverse types to avoid import rejection.
Dataverse and Zoho use different lookup resolution models for attachments
Dynamics 365 Annotations use a polymorphic objectid reference (pointing to any CRM entity via objecttypecode), while Zoho CRM uses module-specific attachment endpoints.
How we handle it
Attachment records in Zoho must specify the parent module name and record ID at the time of attachment. We resolve the Dataverse objecttypecode-to-Zoho module mapping and the Dataverse objectid-to-Zoho record ID mapping before uploading attachments. Attachments for records that fail to migrate (rejected rows) are held in a quarantine queue and retried once the parent record issue is resolved.
How the migration runs
Discovery and format assessment
We audit the source Dynamics 365 Marketing environment: Dataverse entities in use (Contacts, Leads, Accounts, Opportunities, Activities), custom entities from the managed solution schema, Customer Insights assets (Journeys, segments, email templates), and the total record count per entity.
What this step covers
We identify the export format available from the Dynamics environment (Dataverse bulk export, Configuration Migration Tool, or SQL .BAK) and determine the conversion path to CSV. We also audit the destination Zoho CRM edition (Standard, Professional, Enterprise, Ultimate) to confirm which modules and custom field capabilities are available.
Schema design and field mapping
We design the destination Zoho CRM schema based on the Dataverse schema export.
What this step covers
This includes mapping Dataverse entity names to Zoho modules (Account, Contact, Lead, Potential), Dataverse field types to Zoho field types (option set to picklist, two options to checkbox, decimal to currency or number), and creating any custom fields in Zoho CRM before data import begins. We create custom fields via the Zoho CRM API in a sandbox environment first. We also document the Lead-Contact split rule derived from Dynamics contact statecode for customer review.
Format conversion and sandbox import
We convert Dynamics 365 exported data (Dataverse bulk export or .BAK SQL export) into typed CSV files matching the Zoho CRM import format.
What this step covers
This includes type coercion for date fields (Dataverse uses UTC ISO 8601; Zoho uses locale-specific formats), picklist value normalization, and null field handling. We run a full sandbox import into a Zoho CRM sandbox org using production-like data volume. The customer's admin reviews record counts, spot-checks field mappings on 25-50 records per module, and signs off before production migration begins.
Owner and user provisioning
We extract all distinct Dynamics 365 owners referenced on Contacts, Accounts, Opportunities, and Activities and match them by email against the destination Zoho CRM User table.
What this step covers
The customer's admin provisions any missing Zoho Users and assigns them appropriate roles before migration. Owner lookups in Zoho CRM are required on standard records; migration cannot proceed with records referencing unprovisioned owners.
Production migration in dependency order
We run the production migration in record-dependency order: Accounts (base organization records first), Contacts and Leads (with the statecode split applied), Opportunities (with AccountId and OwnerId resolved), Products and Price Books, Activities (Tasks, Calls, Events, Emails in separate batches via Zoho CRM API with rate-limit handling), Attachments (after parent records confirmed), and Custom Entities (last, because they often have lookups to standard objects).
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins.
Marketing automation rebuild handoff and cutover
We deliver the written marketing automation rebuild guide covering email templates (with HTML content and subject lines documented), Customer Journey specifications (with entry triggers, segment criteria, step sequence, and wait-branch logic), and segment definitions (criteria-based and static).
What this step covers
We freeze writes in Dynamics 365 Marketing at cutover, run a final delta pass for any records modified during the migration window, then enable Zoho CRM as the system of record. We support a one-week hypercare window for data quality issues. We do not rebuild Customer Insights Journeys as Zoho Marketing Automation workflows inside the standard migration scope; that work is a separate engagement for the customer's marketing team or a Zoho Marketing Automation implementation partner.
Dynamics 365 Marketing - 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 field count, and whether marketing automation assets are scoped for documentation-only or active rebuild. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Dynamics 365 Marketing to Zoho CRM →Why teams move from Dynamics 365 Marketing to Zoho CRM
- Dynamics 365 Marketing carries a per-tenant price floor of $1,500/month before CRM user seats are counted, creating a significant cost barrier for small and mid-market teams. Zoho CRM Standard at $20/user/month offers the same CRM module coverage for a fraction of the cost, and even Zoho Marketing Automation at $50/month for the base plan is lower than the Microsoft stack floor. Teams with five to twenty users routinely see subscription cost reductions of 60-80 percent after switching.
- Organizations without a prior Microsoft 365 investment find managing separate admin portals for Dynamics CRM, Customer Insights - Journeys, and Dataverse capacity allocations operationally expensive. Gartner Peer Insights reviewers consistently rate Zoho CRM higher on ease of integration and deployment compared to Dynamics CRM (Legacy), citing the unified module structure and simpler navigation as factors that reduce admin burden for teams without dedicated IT resources.
- Dynamics 365 implementations commonly require six to twelve weeks for initial configuration, with dedicated admin resources needed to manage the Dataverse schema, Configuration Migration Tool, and Power Platform extensions. The implementation complexity and hidden training costs are cited in migration guides as a primary driver for moving to Zoho CRM, where module setup, field customization, and user onboarding are designed for smaller teams without dedicated IT staff.
- Zoho CRM supports custom fields and modules from its Professional and Enterprise tiers without requiring a managed solution export, and the built-in migration wizard provides a guided path for data import once CSV format is achieved. The Zoho ecosystem (Zoho Analytics, Zoho Desk, Zoho Campaigns) offers a unified vendor stack at lower per-product cost than equivalent Microsoft Attach licenses, which appeals to teams seeking a single-vendor CRM with integrated analytics and support.
- Organizations that rely on Dynamics 365 for transactional CRM data but do not actively use Customer Insights - Journeys are paying the full $1,500/month marketing tier for functionality they do not use. Migrating to Zoho CRM as the CRM of record and optionally adding Zoho Marketing Automation only if marketing automation is actively needed eliminates the marketing licensing overhead entirely for teams that have outgrown the per-tenant model.
Questions, answered
Dynamics 365 Marketing to Zoho CRM migration questions
How long does a Dynamics 365 Marketing to Zoho CRM migration take?
Most migrations land between four and six weeks for accounts with fewer than 10,000 Contacts, 3,000 Opportunities, and no custom Dataverse entities. Migrations with custom entities, large activity histories (over 200,000 records), or Zoho Marketing Automation integration planning move to ten to fourteen weeks because of the format conversion overhead, multi-pass scheduling for Dataverse exports, and the marketing automation documentation scope. The Dynamics 365 environment's export format (Dataverse bulk export or SQL .BAK) and the volume of Customer Insights assets are the primary timeline drivers.
What happens to my Customer Insights - Journeys and marketing email templates?
Customer Insights - Journeys and marketing email templates cannot be imported into Zoho Marketing Automation because the workflow engines use incompatible formats. We export the template content (HTML, subject, sender profile) and Journey configuration (trigger conditions, segment criteria, step sequence, wait branches) as written specification documents. The customer's marketing team uses these documents to rebuild the Journeys in Zoho Marketing Automation. If Zoho Marketing Automation is not yet licensed, the templates and Journey logic are preserved as documentation only and can be rebuilt when the marketing automation product is activated.
Do Dynamics 365 Workflows and Power Automate flows migrate to Zoho CRM?
No. Dynamics 365 Workflows, Power Automate flows, and Customer Insights Journey triggers are workflow definitions that do not have equivalents in Zoho CRM's automation engine. We do not migrate them as code. We deliver a written inventory of every active Dynamics 365 Workflow and Power Automate flow with its trigger, conditions, and actions documented, along with a recommended Zoho CRM workflow equivalent. The customer's admin rebuilds these in Zoho CRM's workflow builder post-migration. This work is outside the standard migration scope.
Can we migrate our Dynamics 365 marketing contacts without losing email subscription preferences?
Yes. Email opt-in and opt-out preferences stored on Dynamics 365 Marketing contacts migrate to Zoho CRM Lead or Contact fields. We preserve the original marketing contact classification in a custom field for audit. If the customer plans to use Zoho Marketing Automation or another email marketing tool post-migration, the opt-in status maps directly to the HasOptedOutOfEmail equivalent in the destination platform. We recommend reviewing the contact classification before migration to avoid unintended Dynamics 365 Marketing billing exposure on records that should be classified as non-marketing.
How do we handle the BAK file export from Dynamics 365?
Zoho CRM's built-in migration tool accepts only CSV files, not the SQL .BAK backup format that Dynamics 365 sometimes produces. We handle the format conversion as part of the migration process: we use Dataverse export utilities to extract the data into typed CSV files, normalize date formats to Zoho's locale-specific requirements, validate picklist values against the Zoho destination schema, and generate import-ready CSV files for each module. This conversion step adds one to two weeks to the timeline but ensures that no records are rejected by Zoho's import validator due to type mismatches.
Do we keep historical call, email, meeting, and task activity history?
Yes. We migrate the full activity history from Dynamics 365 ActivityPointer (calls, emails, meetings, tasks) into Zoho CRM's corresponding activity modules. Each activity type runs as a separate import batch via the Zoho CRM API with rate-limit handling. ActivityDate is preserved from the original Dynamics createdon timestamp. The parent record lookup (Contact, Account, Potential) resolves at migration time so that the Zoho activity timeline mirrors the Dynamics activity timeline for the migrated records.
Can FlitStack AI also migrate our Dynamics 365 data to Zoho Marketing Automation if we decide to license it?
Yes. Zoho Marketing Automation migration is a parallel scope to the CRM migration. We migrate marketing contact lists (static segments become Zoho Marketing Automation Lists), web form configurations (documented as rebuild specs for Zoho web forms), and email template content (HTML and subject exported as documentation). We do not migrate Customer Insights Journey definitions as functional workflows; those are documented for rebuild. Zoho Marketing Automation is a separate product from Zoho CRM with its own module structure, and the migration of marketing data follows the same format-conversion approach used for the CRM migration.
Related migrations
Zoho CRM implementation
Set up Zoho CRM and migrate into it as one engagement.
See the service → Customer.io to Zoho CRMMapping · history · rollbackSendCloud to Zoho CRMMapping · history · rollbackSalesforce to Zoho CRMMapping · history · rollbackDubsado to Zoho CRMMapping · history · rollbackClio to Zoho CRMMapping · history · rollbackAweber to Zoho CRMMapping · history · rollbackGet a quote
Moving from Dynamics 365 Marketing 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