Migrate from Dynamics 365 Field Service to Zoho CRM

Dynamics Account maps 1:1 to Zoho Accounts. Industry, number of employees, annual revenue, and website URL carry over as standard fields. Any Dynamics custom fields on Account must be manually recreated in Zoho's field editor before migration — we deliver a custom field creation checklist as part of the pre-migration schema plan.

Dynamics Contact maps directly to Zoho Contacts. Full name, email, phone, mobile phone, job title, and full address fields (street, city, state, postal code, country) transfer as standard fields. Dynamics allows N:N contact-to-account relationships; Zoho uses a single primary Account lookup — we resolve one primary AccountId per contact and surface remaining associations via the Account-Contact Relationship module.

Dynamics Lead maps to Zoho Leads with status, lead source, rating, and description fields preserved. Lead score (if populated via a Dynamics plug-in) migrates as a custom numeric field Lead_Score__c. Dynamics does not have a dedicated Lead object in the same sense as Zoho — some teams use Contact directly — so we inspect the source schema first to determine whether leads and contacts share the same table or are separate.

Dynamics Opportunity maps to Zoho Deals. Deal name, amount, close date, and probability transfer directly. Pipeline stages in Dynamics map to Zoho Deal stages via value-by-value mapping — stage names are rarely identical, so we produce a stage-mapping table during discovery. If Dynamics uses multiple pipelines, we configure multiple Zoho Deal pipelines with stage sets per pipeline.

Dynamics Task activities (Type = 'Task') migrate to Zoho Tasks with subject, description, status, and due date preserved. Task status values differ between systems — we produce a Task status mapping table during discovery so that 'Open' in Dynamics maps to 'Not Started' in Zoho, for example. Original timestamps and owner assignments carry over via custom datetime fields.

Dynamics Phone Call activities migrate to Zoho Calls with subject, call type (inbound/outbound), start time, and duration preserved. Dynamics call recordings do not store inside the CRM entity by default — we flag them for separate file export and re-upload to Zoho Files linked to the Call record.

Dynamics Appointment activities map to Zoho Events with subject, start time, end time, all-day flag, and location preserved. The Dynamics Organizer field maps to a custom Owner_Name__c text field since Zoho Events do not have a native Organizer lookup — attendees map via the Event Attendees related list if your Zoho plan supports it.

Dynamics annotations (notetext, subject, objectid) map to Zoho Notes with subject as the Note title and notetext as the body content. Dynamics supports rich-text annotations; we preserve HTML content as-is so it renders in Zoho Notes. Note attachments (filebody) migrate as separate Zoho attachments linked to the Note record.

Dynamics Incident (Case) maps directly to Zoho Cases with case number, title, status, priority, description, and case origin fields preserved. Dynamics case status values (Active, Resolved, Cancelled) map to Zoho Case status values via a value-mapping table. If your Dynamics case origin field uses custom values, we create matching pick-list values in Zoho Cases before migration.

Dynamics Product maps to Zoho Products with product name, SKU, unit price, product category, and active/inactive status preserved. If your Dynamics instance uses Product Relationships (up-sell, cross-sell), we map those to Zoho's Related Products related list. Bundle products in Dynamics require manual decomposition in the migration plan.

Dynamics Quote maps to Zoho Quotes with quote number, name, account link, contact link, and quote line items preserved. Quote status values (Draft, Active, Revised, Closed Won, Closed Lost) map to Zoho Quote stage values. Quote-level discounts and tax fields transfer as-is; line-item-level discounts map to Zoho Line Tax records.

Dynamics Sales Order maps to Zoho Sales Orders with order number, account, contact, product lines, quantity, and pricing preserved. Order status values (Active, Fulfilled, Invoiced, Cancelled) map to Zoho Sales Order status values. Partially fulfilled orders retain fulfillment state in a custom field since Zoho Sales Orders track fulfillment as a single status.

Dynamics Invoice maps to Zoho Invoices with invoice number, billing account, line items, tax, and total amount preserved. Invoice status (Paid, Unpaid, Overdue, Cancelled) maps to Zoho Invoice status via value mapping. Dynamics invoice attachments (invoicedoc) migrate as Zoho File attachments linked to the Invoice record.

Dynamics Price List maps to Zoho Price Books with price book name and status (Active/Inactive) preserved. Individual product pricing from Price List Items maps to Zoho Product Pricing records within the Price Book. Multiple price lists in Dynamics map to multiple Zoho Price Books with the same name.

Dynamics BookableResourceBooking stores technician/resource assignments for field service jobs. This entity has no native Zoho equivalent. We create a custom Work Orders module in Zoho and map Booking ID, Resource Name, Booking Status, and from/to times as custom fields. The booking status (Pending, Committed, Cancelled) is stored as a custom pick-list field (Booking_Status__c).

Dynamics work order service tasks define sub-tasks within a work order (e.g., 'inspect HVAC unit', 'replace filter'). We store these as line items within the custom Work Orders module or as related Tasks linked to the work order parent, depending on whether your Zoho instance has the subform feature in the custom module.

Dynamics Competitor entity stores competitive intelligence per opportunity. Zoho CRM has no native Competitor module — competitor names are stored as a multi-select pick-list or text field on the Deal record. We migrate the competitor data as a custom multi-select field (Competitors__c) on the Zoho Deal so sales reps retain win/loss competitive context.