Migrate from Zoho CRM to Microsoft Dynamics 365 Sales

Zoho Accounts map directly to Dynamics 365 Account. We use Account_Name as the match key during upsert. Multi-address records in Zoho (stored as related address records per Account) are split by address type (billing, shipping, other) and written to the Dynamics 365 composite address fields (postaladdress, ship_to_address, other_address) on the Account entity. If no address role is designated in Zoho, the primary address maps to postaladdress and subsequent addresses are appended to a custom notes field or a related-address custom entity we provision during migration.

Zoho Contacts map to Dynamics 365 Contact. We enforce the Account-Contact hierarchy by importing Accounts first, then resolving AccountId on every Contact during the Contact upsert phase. Contacts without a matching Account in Zoho are flagged in the reconciliation report; customers choose whether to create placeholder Accounts or attach orphaned Contacts to a default Account. Email address is the dedupe key.

Zoho's Lead module (distinct from Contacts with Lead_Status set to New or Open) maps to Dynamics 365 Lead. The Zoho Lead_Status picklist translates to Dynamics 365 Lead Status option set. Any Zoho Contact records where the customer wants to preserve pre-conversion prospect history migrate as Leads rather than Contacts, and the customer's admin converts them post-migration. We flag records with mixed history (both Lead and Contact activity) during discovery.

Zoho Deals map to Dynamics 365 Opportunity. The Deal's Pipeline assignment determines the Microsoft Dynamics 365 Sales Process and Record Type. Stage names translate via a picklist translation table built during discovery. Closing_Date, Amount, and Probability migrate directly. OwnerId resolves via the User mapping table. If the Zoho org uses multi-pipeline (Enterprise tier), we provision one Record Type per Zoho pipeline and configure corresponding Sales Processes in Dynamics 365 before importing Opportunities.

Zoho Products map to Dynamics 365 Product2. Product_Code maps to ProductNumber, Product_Name maps to Name, and Unit_Price becomes the StandardPrice on the DefaultPriceLevel. We import Products before any Quote or Sales Order migration to satisfy the product reference constraint.

Zoho Quotes, Sales Orders, and Invoices (subform-heavy modules) map to Dynamics 365 Quote, SalesOrder, and Invoice respectively. Line items migrate as OpportunityProduct (for Quotes) or SalesOrderDetail (for Sales Orders) child records. We issue separate API fetches for each subform relationship in Zoho, reconstruct the parent-child hierarchy, and upsert both layers into Dynamics 365. Parent Opportunity lookup resolves at migration time via the deal-ID-to-opportunity-ID mapping built during the Deals phase.

Zoho Tasks map to Dynamics 365 Task with Priority and Status preserved. Zoho Events map to Dynamics 365 Event with StartDateTime, EndDateTime, and Location. Zoho Calls map to Task with TaskSubtype=Call and CallDurationInSeconds in a custom field. ActivityParty records link meeting attendees and call participants to the parent Contact or Lead. ActivityDate controls the timeline ordering in Dynamics 365.

Zoho custom modules migrate to Dataverse custom entities. We introspect the Zoho module schema via GET /settings/fields during discovery, pre-create the equivalent Dataverse table (including column definitions, data types, and lookup relationships) in the destination Dynamics 365 environment, then migrate records via the Dataverse Web API. Custom module-to-standard-object lookups resolve via the ID mapping tables built during earlier phases.

Zoho attachments are stored as separate file records linked to parent modules. We fetch them via the Attachments API endpoint and migrate them as Dynamics 365 Annotation (Note) records with documentbody for small files or as SharePoint file references if the Dynamics 365 environment has SharePoint integration enabled. File size limits on the Dynamics 365 API require chunking for attachments over 4 MB.

Zoho Users map to Dynamics 365 User records by email match. We extract the full Users module during discovery, build an email-to-user-ID mapping table, and write the Dynamics 365 User ID as the OwnerId on all migrating records. Inactive Zoho users who own records require the customer's admin to either activate corresponding User accounts in Dynamics 365 or reassign ownership to an active admin before migration resumes.