Skip to content
Techila Global Services
Techila/Migration/Zoho CRM to Salesforce migration

Zoho CRM to Salesforce migration:
process and checklist

Last reviewed:

A Zoho CRM to Salesforce migration maps Zoho modules to Salesforce objects, exports the data within Zoho's export limits, and rebuilds workflows and custom functions. Attachments need the full backup, not module exports. Volumes, custom modules and connected apps decide the plan, so it starts with an audit.

When does moving make sense?

These are the situations in which a move usually pays off:

  • Processes now need deeper customization, approvals or a larger partner ecosystem.
  • The business is consolidating onto Salesforce after an acquisition.
  • Reporting, governance or integration needs have outgrown the current edition.
  • The team plans to use Agentforce on CRM data.

What Zoho CRM lets you export

The Zoho CRM documentation sets limits that shape the plan. The points below come from the vendor's own help pages:

  • Zoho module exports are CSV or XLSX in a ZIP: XLSX up to 50,000 records per export and CSV up to 200,000 records from one module; larger sets need several exports filtered by Created Time or a full backup. Source: Zoho Help
  • Notes export as their own module. Attachments are not part of module exports. Source: Zoho Help
  • Daily export counts depend on the edition: 10 (Free), 100 (Standard), 250 (Professional), 500 (Enterprise), 1,000 (Ultimate). Users need the Export (Module) permission. Source: Zoho Help
  • An administrator can request a data backup: CSV module data plus a separate ZIP of all attachments. It excludes email content and attachments, Documents and data obtained through integrations. Download links last up to 7 days. Source: Zoho Help

How the data maps to Salesforce

Where Zoho CRM data normally lands in Salesforce. The final mapping is agreed field by field in the design phase and signed off before any data moves.

How the data maps to Salesforce
In Zoho CRMIn SalesforceNote
LeadsLeadKeep the Zoho record ID in an external ID field; map lead status and source picklists.
ContactsContactLoad after accounts; map the account lookup.
AccountsAccountDeduplicate by name and website before loading.
DealsOpportunityMap Zoho pipelines and stages to a sales process and stages.
CasesCaseMap status and priority picklists.
Products, price books, quotes, sales ordersProduct, price book, Quote, OrderCreate products and price books before loading quotes and orders.
Tasks, events, callsTask and EventMap related-to and who fields.
NotesContent Note or NoteExported as their own module; relink to the parent record.
AttachmentsFiles (Content Version)Taken from the full backup, not from module exports.
CampaignsCampaign and campaign membersMap member status values.
Custom modules and fieldsCustom objects and fieldsReview multi-select, subform and lookup fields; subforms usually become related child objects.

What does not move automatically

Some things cannot be copied across and are rebuilt, replaced or retired. These are agreed during the audit so that nothing surprises the business on go-live day:

  • Workflow rules, blueprints and custom functions (rebuilt as Flow or Apex)
  • Zoho web forms and portals (replaced)
  • Email content and attachments held in Zoho (not in the backup)
  • Reports and dashboards (rebuilt)
  • Data from third-party integrations (re-collected from the source apps)

Zoho CRM to Salesforce migration steps

A migration runs in seven phases. Each phase ends with a deliverable that is reviewed before the next one starts.

  1. Discover and audit

    Deliverable: Scope document and data inventory

    What happens in this phase
    • List the Zoho CRM objects, custom fields, automations, integrations and reports in use
    • Count records per object and flag duplicates and stale data
    • Agree what is migrated, archived or left behind
    • Request a full backup early so attachments are available
  2. Design the Salesforce model and the mapping

    Deliverable: Target data model and signed mapping sheet

    What happens in this phase
    • Choose standard and custom objects, record types and the sales or service process
    • Write the field-by-field mapping with transformation rules
    • Design security: profiles, permission sets, sharing
    • Define record ownership and user mapping
  3. Prepare Salesforce

    Deliverable: Configured sandbox

    What happens in this phase
    • Configure objects, fields, page layouts, validation and automation in a sandbox
    • Set up integrations that must exist on day one
    • Create users and permissions
  4. Clean and transform the data

    Deliverable: Load-ready files and transformation scripts

    What happens in this phase
    • Deduplicate and standardize values
    • Resolve relationships between records before loading
    • Prepare load files in dependency order and convert subform rows into child records
    • The Data Import Wizard imports up to 50,000 records at a time; Data Loader complements the web-based import wizards for larger loads.
  5. Trial loads and reconciliation

    Deliverable: Reconciliation report and test sign-off

    What happens in this phase
    • Load into the sandbox, compare record counts and sample values with the source
    • Fix mapping errors and repeat until counts reconcile
    • User acceptance testing with real scenarios
  6. Cutover

    Deliverable: Production go-live and rollback plan on record

    What happens in this phase
    • Freeze changes in the source system for the agreed window
    • Run the final load into production and reconcile again
    • Switch web forms, email and integrations to Salesforce
  7. Hypercare and retire the old system

    Deliverable: Closure report and decommission checklist

    What happens in this phase
    • Support users and fix defects after go-live
    • Keep the source data read-only for an agreed period
    • Cancel or downgrade the old subscription only after sign-off

The audit in phase 1 produces the plan with dates, effort and owners for the specific case. Techila does not quote a duration before the audit, because record volumes, automation and integrations differ for every business.

Risks and how they are handled

Every migration has the same handful of risks. This is how each one is controlled:

Risks and mitigations
RiskHow it is handled
Attachments missedTake the full backup, which holds attachments in a separate ZIP, and plan the file load separately.
Export limits stall the workSplit large modules by Created Time and watch the daily export count for the edition.
Subform data flattened or lostDecide a child-object design in the mapping phase and test with real records.
Email history not availableConfirm what email data matters; the backup excludes email content, so capture it from the mail system.
Custom functions and blueprints not reproducedInventory each one in the audit and decide whether to rebuild, replace or drop.
Duplicates carried acrossDeduplicate before load and define matching rules in Salesforce.

FAQ

Frequently asked questions

Can Zoho data be exported in one file?

Module exports have record limits, so large modules need several exports or the full backup.

Are attachments migrated?

Yes, from the full backup. Module exports do not include them.

Can Zoho and Salesforce run together during the move?

Yes. A phased move with a short freeze window at cutover is common. See the Zoho integration page.

How long does a migration take?

It depends on volumes, custom modules, automation and integrations. The audit produces a plan with dates for the specific case.

Plan your migration with a Salesforce architect

Tell us what you need. We reply within 1 business day.

All fields are required unless marked optional.

We save these details on this device to fill them in next time.

Add project details (optional: clouds, users, start date, role)
Salesforce clouds (optional, choose any)Which Salesforce clouds are involved?
Salesforce users (optional)How many Salesforce users?
Start date (optional)When do you want to start?
Your role (optional)What is your role?

We reply within 1 business day.

By sending this form, you agree that Techila Global Services may contact you by email or phone about your request. We do not sell your personal information. See our Privacy Policy.

Next step

Let's plan your next Salesforce program.

Techila starts with an audit of your Zoho CRM setup and a mapping to Salesforce. Share the objects in use, record counts and integrations, and we reply within 1 business day.

Related

Related

Evidence

Sources

  1. Zoho: export CRM data
  2. Zoho: data backup
  3. Salesforce: how many records can be imported with the Data Import Wizard
  4. Salesforce Data Loader guide (Winter '27)

Product names are trademarks of their owners. Zoho is a trademark of Zoho Corporation. Techila is not affiliated with Zoho. Information on this page was checked on 26 October 2026; vendor limits and prices change, so confirm on the vendor pages linked in the sources.