Migrate from Zoho CRM to Salesforce Sales Cloud

Zoho Lead records map directly to Salesforce Lead. Standard fields (First_Name, Last_Name, Email, Phone, Company, Lead_Status, Lead_Source) map to Salesforce equivalents with identical names. Custom fields carry over with __c suffix appended. Lead_Status picklist values from Zoho are normalized to the Salesforce Lead Status picklist; any Zoho-specific statuses are mapped to the nearest Salesforce equivalent or flagged for the customer's admin to add as a custom value before migration.

Zoho Accounts (internally labeled 'Companies') map to Salesforce Account. The Account_Name, Website, Industry, Annual_Revenue, and Number_of_Employees fields map directly. Zoho stores phone and address on the Account record directly; these map to Account.Phone and BillingAddress fields in Salesforce. Account is created before any Contact import so that the AccountId lookup is satisfied at Contact insert time.

Zoho Contacts map to Salesforce Contact with a required lookup to the Account resolved via AccountId. Zoho stores phone and mailing address on the Contact record; these map to Contact.Phone and MailingAddress in Salesforce. We resolve the Contact-to-Account relationship by matching Zoho Contact.Account_Name to the Account.Name already imported, falling back to domain-based matching if exact name match fails.

Zoho Deals map to Salesforce Opportunity. The Deal_Name field maps to Opportunity.Name; Amount, Closing_Date, and Probability transfer directly. Zoho's pipeline and stage assignments map to Salesforce Opportunity.StageName, which we configure as part of the target schema design. Owner assignments are resolved via the email-based User mapping. Multi-pipeline Zoho configurations become Salesforce Record Types on Opportunity.

Each Zoho pipeline becomes a Salesforce Record Type with a corresponding Sales Process that whitelists the relevant stage values. Stage probability percentages migrate from Zoho to Salesforce StageProbability. If Zoho has custom stage names (e.g., 'Proposal Sent', 'Negotiation'), we create equivalent Stage values in the Salesforce Sales Process and document any non-standard stage additions.

Zoho Products map to Salesforce Product2 records. Product_Code maps from Zoho Product_Code to Product2.ProductCode. Standard Price Book entries are created during import with UnitPrice mapped from Zoho's Unit_Price field. Product2 is imported before any Quote or Sales Order migration to satisfy the Pricebook2 reference.

Zoho Quotes map to Salesforce Quote, which is available from the Professional tier Salesforce edition. Quote headers (Account, Contact, Valid_Date, Description) map directly. Zoho line items inside Quotes are stored as subform child records; we issue separate API calls to Zoho to fetch all Quote_Subform rows, then insert them as Salesforce OpportunityLineItem records linked to the Opportunity derived from the Zoho Quote's related Deal.

Zoho Sales Orders map to Salesforce Order. Zoho's subform line items (Product, Quantity, Unit_Price, Discount) are fetched separately via the Zoho subform API endpoint and reconstructed as Salesforce OrderItems. The Account lookup is resolved via the Account mapping. Order.Status is set to Draft pending activation after all line items are committed.

Zoho Tasks map to Salesforce Task. Subject, Status, Priority, Activity_Date, and Description transfer directly. The linked-to record (WhatId) is resolved by matching the Zoho parent record type and ID to the equivalent Salesforce record. Owner assignments use the email-to-User mapping to resolve Salesforce OwnerId.

Zoho Events map to Salesforce Event with Start_DateTime, End_DateTime, and Location preserved. Zoho stores attendee information as related Contact records; these map to EventRelation records in Salesforce linked to the corresponding Contact. The linked-to record (WhatId) is resolved via parent record type matching against the imported Accounts, Contacts, or Deals.

Zoho Call records map to Salesforce Task with TaskSubtype = Call. Call duration, disposition, and any caller notes transfer to custom Task fields. The WhoId on the Task points to the linked Contact or Lead; ActivityDate is set from the Zoho Call timestamp to preserve timeline ordering.

Zoho Notes map to Salesforce Note records linked via ContentDocumentLink to the parent record (Lead, Contact, Account, or Opportunity). Note body migrates as rich text. We preserve the Note created-by and created-date metadata from Zoho. If the Note contains attachments, these are handled via the Zoho Attachments API and uploaded as ContentDocument records.

Attachments in Zoho are stored as separate file records linked to parent modules via lookup IDs. They do not appear in standard CSV exports and must be fetched via the Zoho Attachments API endpoint (GET /Attachments). We download each file, then upload to Salesforce as ContentVersion linked to the parent record via ContentDocumentLink. This requires the migration user to have Content workspace permissions in the Salesforce destination org.

Zoho custom modules are discovered via GET /settings/fields and mapped to Salesforce custom objects with a __c API name suffix. We introspect the custom module's field metadata (field type, required, picklist values) before mapping. The destination Salesforce schema (custom object, custom fields, field types, validation rules) is deployed via metadata API or change set before any data import begins. Lookup relationships to standard objects (Accounts, Contacts) are resolved via the pre-imported parent record mapping.

Zoho Tags are cross-module label objects that export with the parent record in CSV. We parse tag arrays from Zoho's API response and reconstruct them in the destination using either a Salesforce multi-select picklist field (preferred if tag count is under 200) or Salesforce Topics with TopicAssignment records. The customer chooses the strategy during scoping.

Zoho User records (full name, email, role, profile, active status) are extracted during discovery. We build an email-to-User-ID mapping table against the Salesforce destination org's User table. Any Zoho Owner ID referenced on a record is translated to the matching Salesforce User ID at import time. Inactive Zoho users are imported as inactive Salesforce Users or flagged in a reconciliation queue for the customer's admin to provision before record import begins.

Zoho Blueprints are workflow automation configurations stored as process rules, not as data records. They cannot be exported from Zoho CRM via API or CSV. We run a Blueprint discovery scan during the scoping phase, document every Blueprint's trigger, stage progression conditions, and automated actions in a written handoff document, and recommend equivalent Salesforce Flow constructs for each. The customer's admin or a Salesforce partner rebuilds these post-migration; they are not part of the data migration scope.