Migrate from Dynamics 365 Marketing to Zoho CRM

Dynamics 365 CRM contacts map to Zoho CRM Lead or Contact depending on the lifecycle state. 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.

Dynamics 365 Accounts map directly to Zoho CRM Accounts. 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.

Dynamics 365 Opportunities map to Zoho CRM Potential. 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.

Dynamics 365 Leads (separate from Contacts, representing pre-qualification records) map directly to Zoho CRM Lead. 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.

Dynamics 365 Products map to Zoho CRM Products with Standard Price Book entries created during import. 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 fields on any Dynamics 365 entity must be defined in the destination Zoho CRM schema before data values can be imported. 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.

Activities stored in the Dynamics 365 ActivityPointer entity (Email, Task, PhoneCall, Appointment) migrate to Zoho CRM's corresponding activity modules. We extract from the type-specific child tables and set ActivityDate from the original createdon timestamp. The Regarding (objectid) lookup preserves the relationship to Contact, Account, or Potential. Owner assignment migrates via email-to-User matching. Each activity type runs as a separate import batch.

Dynamics 365 attachments stored as Annotation records are exported individually with file content and metadata (objectid, objecttypecode). We download file blobs, generate a Zoho CRM attachment manifest, and reattach to parent records using the Zoho CRM Attachments API after the parent record (Contact, Account, Potential) is confirmed in the destination. The objecttypecode from Dataverse maps to the Zoho module name, and the objectid maps to the Zoho record ID.

Dynamics 365 Users referenced as record owners are matched to Zoho CRM Users by email address. The customer's admin provisions Zoho User accounts before migration. Owners without a matching Zoho User are held in a reconciliation queue; inactive Dynamics users are mapped to inactive Zoho Users if historical assignment must be preserved. We do not migrate security roles or Dataverse team memberships as they have no direct Zoho equivalent.

Marketing email templates stored in the msdynmkt_email table are marketing-journey assets, not transactional CRM records. We export the template content (subject, HTML body, sender profile) as a structured document and deliver it as a rebuild guide for Zoho Marketing Automation. Zoho Marketing Automation is a separate product from Zoho CRM; the templates are documented as configuration, not migrated as data. If the customer does not license Zoho Marketing Automation, email templates are scoped out of the migration entirely.

Customer Journey definitions from Dynamics 365 Customer Insights - Journeys (msdynmkt_journey) store trigger conditions, segment membership criteria, email sequence order, and wait-branch logic in a format not compatible with Zoho Marketing Automation workflows. We export Journey configuration as a written specification document covering entry trigger, segment criteria, email steps, delays, and exit conditions. The customer's marketing team rebuilds each Journey in Zoho Marketing Automation using the documented sequence as the reference. This is a documentation-only deliverable, not a data migration.

Segment definitions from Customer Insights - Data live in a separate service from the core CRM Dataverse and require a separate export pass. Static segments with a fixed member list can be exported as a contact list and imported as a Zoho Marketing Automation List. Criteria-based (dynamic) segments cannot be exported in equivalent form because the segment evaluation logic differs between Customer Insights and Zoho Marketing Automation. We export the segment criteria as a written specification document for the customer's marketing team to reproduce as Zoho dynamic list rules.