Skip to content
Get a quote

Zoho CRM to Salesforce migration

We migrate Leads, Contacts, Accounts, Deals, and Activity history from Zoho CRM into Salesforce Sales Cloud with subform line items reconstructed as child records, picklist values normalized across both platforms, and every Blueprint inventoried for your admin to rebuild in Salesforce Flow.

Short answer

FlitStack AI migrates leads, accounts, contacts, opportunities and record type + sales process from Zoho CRM to Salesforce, 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: 3-6 weeks.

By

Source Zoho CRM
DestinationSalesforce
LeadAccountContactOpportunityRecord Type + Sales Process
Mapped field by field · sample run · one-click rollback

What moves from Zoho CRM to Salesforce?

Moving from Zoho CRM to Salesforce Sales Cloud is a structural schema migration.

Read the full summary

Zoho stores Accounts and Contacts in one unified Companies module with phone, website, and address fields duplicated across both entity types, while Salesforce splits these into separate Account and Contact objects with a lookup relationship that must be satisfied at import time. Zoho's subform data model (line items inside Quotes, Sales Orders, and Purchase Orders) requires separate API fetches to reconstruct as Salesforce child records. Zoho Blueprints are workflow configurations that cannot export as data; we document each one so your admin rebuilds equivalents in Salesforce Flow post-migration. We sequence the migration in dependency order (Users, Accounts, Contacts, Products, Deals/Opportunities, Activities) and resolve Owner IDs by matching Zoho user emails to Salesforce User records before record import begins. Workflows, Blueprints, and Zoho-specific automations do not migrate as code.

1:1

Lead → Lead

Zoho Lead records map directly to Salesforce Lead.

How it maps

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.

1:1

Accounts (Companies) → Account

Zoho Accounts (internally labeled 'Companies') map to Salesforce Account.

How it maps

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.

1:1

Contacts → Contact

Zoho Contacts map to Salesforce Contact with a required lookup to the Account resolved via AccountId.

How it maps

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.

1:1

Deals → Opportunity

Zoho Deals map to Salesforce Opportunity.

How it maps

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.

configuration

Pipeline → Record Type + Sales Process

Each Zoho pipeline becomes a Salesforce Record Type with a corresponding Sales Process that whitelists the relevant stage values.

How it maps

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.

1:1

Products → Product2

Zoho Products map to Salesforce Product2 records.

How it maps

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.

What moves17 objects
Zoho CRMSalesforce
  • LeadLead1:1
  • AccountsAccount1:1
  • ContactsContact1:1
  • DealsOpportunity1:1
  • PipelineRecord Typetransformed
  • ProductsProduct21:1

+ 11 more in the mapping below

How Zoho CRM and Salesforce 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.

DimensionZoho CRMSalesforce
Account and Contact modelUnified Accounts/Companies module with embedded contact fieldsSeparate Account and Contact objects with a lookup relationship
Pipeline unitDeals module with multi-pipeline support gated at EnterpriseOpportunity object with Record Types and Sales Processes from Professional
Custom objectsAvailable from Enterprise ($40+/user)Available from Professional tier ($80/user) without additional setup fees
Pricing modelPer-seat, $14-$52/user/month; API access from $23+Per-user, $25-$500/user/month; Starter at $25 includes full CRM API access
Workflow automationBlueprint visual workflow builder (Professional+)Salesforce Flow with record-triggered, scheduled, and screen variants from Professional
Line item storageSubform child records fetched separately via APIOpportunityLineItem object linked to Opportunity
App ecosystem45+ native Zoho apps; 2,500+ third-party integrationsAppExchange with over 9,000 listings including native CPQ and ERP depth

What to watch for in a Zoho CRM to Salesforce migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Subform data does not export via CSV

Zoho stores line items inside Quotes, Sales Orders, and Purchase Orders as subform child records rather than inline fields.

How we handle it

Standard CSV exports from Zoho's Data Administration > Export tool flatten the parent record but drop all subform rows entirely. We handle this by issuing separate API calls for each subform relationship (Quote_Subform, SalesOrder_Subform, PurchaseOrder_Subform) using Zoho's COQL query endpoints, reconstructing the parent-child hierarchy, and inserting both layers into Salesforce with the child records linked to the parent Opportunity or Order. If the source Zoho plan lacks API access, we alert the customer that subform data will require manual re-entry or a Zoho partner-assisted export.

high

API access requires Professional tier or above

The Zoho CRM REST API is not accessible on the Free or Standard plan.

How we handle it

If you are migrating from a Zoho Free or Standard org, you cannot use API-based bulk extraction and must rely on manual CSV exports, which do not include attachments, subforms, or related records. We confirm the source Zoho plan's API entitlement during the scoping call and budget extra time for CSV-based extraction when API is unavailable, as it is significantly slower for datasets over 5,000 records and requires manual data split across multiple CSV files.

medium

Zoho picklist values do not always map directly to Salesforce

Zoho and Salesforce maintain independent picklist value sets for equivalent fields (Lead_Status, Industry, Stage, Salutation).

How we handle it

A Zoho picklist value that does not exist in Salesforce's target org causes an import rejection unless the Salesforce admin pre-creates it. We run a picklist gap analysis during scoping, collect the full Zoho picklist export, compare it against the Salesforce destination org's active values, and document any additions required before migration. We also flag picklist values that are Zoho-specific and cannot map cleanly (e.g., Zoho-only industry classifications) for the customer's admin to either create as custom Salesforce values or consolidate.

medium

Zoho API credit consumption is non-linear

Zoho's API credit system charges 1 credit per COQL query with LIMIT 1-200, 2 credits for LIMIT 201-1000, and 3 credits for LIMIT 1001-2000.

How we handle it

A migration fetching 50,000 records in 200-record pages consumes 250 API calls x 1 credit = 250 credits. Enterprise plans offer 100,000 credits per 24-hour rolling window, but multi-module migrations with subform fetches can approach limits. We implement page-level backoff, spread large fetches across multiple API windows, and monitor credit consumption during extraction to avoid 429 errors that would stall the migration.

medium

Owner IDs are not transferable across Zoho orgs

When migrating records to Salesforce, Zoho's Owner field references internal User IDs that do not exist in the destination org.

How we handle it

We extract the Users module during discovery, build an email-to-User-ID mapping table, and write Salesforce User IDs at import time. If the source Zoho org has inactive or departed users assigned as record owners, we flag those records and reassign to an active admin user to avoid orphaning. Any Owner assignment that cannot be resolved goes to a reconciliation queue.

How the migration runs

  1. Discovery and scoping

    We audit the source Zoho CRM org across plan tier, active modules, custom fields, subform usage (Quotes, Sales Orders, Purchase Orders), Blueprints, and Owner assignments.

    What this step covers

    We inventory every active Blueprint and document its trigger and actions for the rebuild handoff. We run a picklist gap analysis comparing Zoho field values against the target Salesforce org's active picklists and document any additions required. The discovery output is a written migration scope document, a field-level mapping table, and a Salesforce edition recommendation based on the customer's user count and required features.

  2. Schema design and sandbox provisioning

    We design the destination schema in a Salesforce Sandbox (Full Copy or Developer Pro).

    What this step covers

    This includes provisioning custom objects and fields (with __c API names), Record Types (one per Zoho pipeline), Sales Processes (stage whitelist per Record Type), Page Layouts, and the Salesforce Lead Status and Industry picklist values required to accept the migrating data. Any missing picklist values are added by the customer's Salesforce admin before the Sandbox migration begins. Schema is validated via Salesforce metadata API or change set before any data moves.

  3. User and Owner reconciliation

    We extract every distinct Zoho user referenced as an Owner on any record and match by email against the Salesforce destination org's User table.

    What this step covers

    Inactive Zoho users are held in a reconciliation queue. The customer's Salesforce admin provisions any missing Salesforce Users and confirms whether departed Zoho users should be created as inactive Salesforce Users or reassigned to an active owner. Migration cannot proceed past this step because OwnerId references are required on most standard Salesforce objects.

  4. Sandbox migration and reconciliation

    We run a full migration into the Salesforce Sandbox using production-like data volume.

    What this step covers

    The customer's RevOps lead reconciles record counts (Accounts in, Contacts in, Leads in, Opportunities in, Activity records in), spot-checks 25-50 random records against the Zoho source for field-level accuracy, and validates that picklist values imported correctly. Any mapping corrections, missing picklist values, or schema adjustments happen here before the production migration begins.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Accounts (from Zoho Companies), Contacts (with AccountId resolved), Leads, Products and Pricebook entries (required for Quote and Sales Order line items), Opportunities (with AccountId, OwnerId, and RecordTypeId resolved), Quotes and their subform line items (fetched separately via Zoho API and inserted as OpportunityLineItem records), Sales Orders and their line items, Activity history (Tasks, Events, Calls, Notes via Bulk API 2.0), Attachments (via Zoho Attachments API uploaded to Salesforce ContentVersion), Custom Modules (last, after standard object lookups are satisfied).

    What this step covers

    Each phase emits a row-count reconciliation report before the next phase begins.

  6. Cutover, validation, and Blueprint rebuild handoff

    We freeze Zoho writes during cutover, run a final delta migration of any records modified during the migration window, then enable Salesforce as the system of record.

    What this step covers

    We deliver the Blueprint inventory document to the customer's admin team, mapping each Zoho Blueprint to recommended Salesforce Flow equivalents. We support a one-week hypercare window where we resolve any reconciliation issues raised by the customer's sales team. We do not rebuild Zoho Blueprints as Salesforce Flow inside the migration scope; that is a separate engagement.

Zoho CRM Salesforce
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · SalesforceRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

3-6 weeksTypical, smaller accounts
8-14 weeksLarge or heavily customised accounts

A quote scales with record volume, custom object complexity, and subform reconstruction scope. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Zoho CRM to Salesforce →

Why teams move from Zoho CRM to Salesforce

  • Zoho's multi-level account hierarchy limitations push growing mid-market companies to Salesforce. While Zoho CRM handles single-level organizational structures adequately, Salesforce supports multi-level account hierarchies with parent-account-to-child-account relationships that reflect complex enterprise buying structures. Comparison reviews and Reddit discussions on r/Zoho confirm that teams managing aerospace, defense, and enterprise manufacturing customers consistently cite this as a scaling constraint.
  • Zoho's implementation consultant ecosystem is less mature than Salesforce's certified partner network. Industry reviews cite that equivalent Zoho implementations run $5,000-$15,000 while Salesforce implementations start at $25,000; however, mid-market companies upgrading from Zoho cite the need for deeper customization capabilities that require certified Salesforce developer resources, suggesting the implementation cost differential reflects genuine capability depth rather than simple pricing.
  • Salesforce's advanced analytics and Einstein AI provide pipeline intelligence that Zoho gates behind Enterprise ($40+/user) or Ultimate ($52+/user) tiers. Revenue operations teams managing complex multi-territory forecasts cite Salesforce's reporting engine as more flexible for multi-dimensional pipeline analysis across product lines, custom fiscal periods, and non-standard attribution models. Zoho's analytics suit inbound-centric reporting but constrain complex slicing for teams with mature forecast processes.
  • Support quality inconsistency drives churn. Zoho's quality of support scores 7.6/10 against industry average according to G2 reviewer data, with Enterprise tier requiring 50+ user minimum for Priority Phone support. Salesforce's tiered support model (Standard, Premier, and Platinum+) offers clearer escalation paths for technical teams that rely on SLA-backed response times during critical migration and ongoing operations.
  • Companies requiring native ERP, CPQ, and revenue intelligence integrations move to Salesforce because AppExchange has over 9,000 listings versus Zoho's roughly 2,500 integrations. Native connectors for NetSuite, SAP, Conga, Apttus, and DocuSign CLM are AppExchange-certified rather than third-party routed, reducing integration maintenance overhead for companies with complex quote-to-cash and contract lifecycle management workflows.

Questions, answered

Zoho CRM to Salesforce migration questions

How long does a Zoho CRM to Salesforce migration take?

Most migrations land between three and six weeks for accounts under 10,000 records across Accounts, Contacts, Leads, and Deals with no subform-heavy Quote histories. Migrations with subform line items inside Quotes and Sales Orders, multi-module Zoho configurations, large activity timelines, or Enterprise-tier Zoho custom modules move to eight to fourteen weeks because of multi-layer API fetching, Salesforce Bulk API chunking, picklist normalization, and the sandbox-to-production validation cycle.

Do Zoho Blueprints and Workflows migrate to Salesforce Flow?

No. Zoho Blueprints are workflow automation configurations stored as process rules, not as data records, and cannot be exported via Zoho CRM API or CSV. We do not migrate them as code. We deliver a written Blueprint inventory during scoping that documents each Blueprint's trigger, stage progression conditions, and automated actions with a recommended Salesforce Flow equivalent. Your Salesforce admin or a certified Salesforce partner rebuilds them post-migration. Zoho workflow rules (not Blueprints) similarly do not migrate; we document them in the same handoff and recommend Flow or Process Builder equivalents.

Can Zoho subform data (line items) be migrated to Salesforce?

Yes, but not via CSV. Zoho stores line items inside Quotes, Sales Orders, and Purchase Orders as subform child records that do not appear in standard CSV exports. We issue separate API calls to Zoho for each subform relationship, fetch all child rows, reconstruct the parent-child hierarchy, and insert both layers into Salesforce. If your source Zoho plan lacks API access (Free or Standard tier), subform data requires manual re-entry or a Zoho partner-assisted export. We flag this constraint during scoping if it applies to your migration.

Do we lose historical activity data (calls, emails, meetings, tasks) during migration?

No. We migrate the full activity history through the Salesforce Bulk API 2.0 with parent-record resolution. Tasks land as Salesforce Task records; calls land as Task with TaskSubtype=Call and duration preserved; meetings land as Event records with attendee links via EventRelation; notes land as Salesforce Note records linked via ContentDocumentLink to the parent record. Activity timeline ordering is preserved by setting ActivityDate to the original Zoho timestamp. Attachments are fetched via the Zoho Attachments API and uploaded to Salesforce as ContentVersion records.

What happens to Zoho user assignments during migration?

Zoho Owner IDs are internal identifiers that do not exist in Salesforce. We build an email-to-User-ID mapping table by matching Zoho user emails against the Salesforce destination org's User table during scoping. At migration time, we write the Salesforce User ID rather than the Zoho ID for every Owner field. If a Zoho user has no matching Salesforce User, the record is held in a reconciliation queue and the customer's Salesforce admin provisions the missing User before migration resumes. Inactive Zoho users are flagged separately; the customer's admin decides whether to create them as inactive Salesforce Users or reassign their records.

How do we handle picklist value mismatches between Zoho and Salesforce?

Zoho and Salesforce maintain independent picklist value sets for equivalent fields. A Zoho picklist value that does not exist in Salesforce's target org causes an import rejection. We run a picklist gap analysis during scoping, export the full set of active picklist values from the Zoho source org, compare them against the Salesforce destination org's active values, and document any additions required. The customer's Salesforce admin adds the missing values to the Salesforce picklist before migration begins. For Zoho-specific picklist values that have no Salesforce equivalent, we recommend either adding them as custom values or consolidating to the nearest standard value during scoping.

Can FlitStack AI migrate from a Zoho Free or Standard plan?

Yes, but the method changes. Zoho Free and Standard plans do not include full API access, limiting us to CSV-based extraction. CSV exports do not include attachments, subform data, or related records (e.g., subform line items inside Quotes and Sales Orders). If your Zoho plan lacks API access, we alert you during scoping that subform data will require manual re-entry or a Zoho partner-assisted export. We plan additional time for CSV-based extraction since it is significantly slower for datasets over 5,000 records and requires manual data segmentation across multiple CSV files. Upgrading to Zoho Professional ($23/user/month) before migration unlocks API access and enables the full-fidelity migration path.

Get a quote

Moving from Zoho CRM to Salesforce?

Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.

Get a quote