Many teams that move from Salesforce to Zoho CRM do it for the same reasons: licence costs that keep rising, an org that has grown complicated over the years, and a wish to run sales, finance and support on one connected suite. The move itself is usually not the hard part. The hard part is deciding what to bring across, what to rebuild and what to leave behind, and then moving the data in an order that keeps every note, activity and owner attached to the right record.
This guide explains how Zoho's Salesforce migration tool works, what it moves and what it does not, and how to plan the switch so your team starts work in Zoho CRM with clean, trusted data.
Quick answer: Zoho CRM has a built-in Salesforce migration wizard. You export your data from Salesforce as CSV files (in a ZIP, with attachments if you want them), upload them to Zoho CRM, and the wizard maps files to modules and columns to fields before it imports. It moves records, owners, notes, activities and attachments, but not your automation: workflows, Flows, Apex, validation rules, reports and dashboards have to be rebuilt in Zoho CRM.
How Zoho's migration tool works was checked on Zoho CRM's help pages in November 2026. Salesforce export rules were checked on published Salesforce admin guides in November 2026. Both products change often, so confirm the current behaviour in your own accounts before you start.
How does Zoho's Salesforce migration tool work?
The Salesforce route in Zoho CRM is file-based. Unlike some other CRMs, which Zoho can pull from directly with an API key, Salesforce data reaches Zoho CRM as exported CSV files. The steps on Zoho's help pages are:
- Sign in to Zoho CRM as an administrator (or a user whose profile has the Data Migration permission).
- Go to Setup > Data Administration > Import, open Data Migration and choose Salesforce.
- Upload your files, either one CSV per object or a single ZIP holding all of them plus an Attachments folder.
- Check the module-file mapping. Zoho reads each file and matches it to a module. You see which files are mapped, unmapped or unsupported, and you can map an unmapped file to an existing module or create a new one. A file ending in "_c" (for example a custom object's CSV) is treated as a custom module.
- Check the field mapping for each module. Zoho auto-maps columns to fields and suggests new custom fields for columns it cannot place. You can create fields here, map several source columns to one field, set default values and fill empty mandatory fields.
- Review and start. A review page shows the mapping status and pre-migration checks for each module before you start.
- Check the results. A summary shows records added, updated and skipped per module. If something went wrong, you can undo the migration from Import History and run it again.
Zoho also offers its own migration help, and a Zoho partner can run the whole process for you. The tool does the heavy lifting; the quality of the result depends on the preparation you do before you upload.
What data does the migration move, and what does it leave behind?
Zoho's migration tool supports the standard Salesforce objects most companies use, plus custom objects. It moves data, not logic.
| Moves with the migration tool | Has to be rebuilt in Zoho CRM |
| Users (needed first, so record owners can be assigned) | Workflow rules, Process Builder and Flows |
| Leads, Accounts, Contacts and Opportunities (Deals) | Apex code, triggers and Lightning components |
| Campaigns, Cases, Solutions and Products | Validation rules and approval processes |
| Notes and activities (tasks, events and calls) | Reports and dashboards |
| Attachments and files (included in the export ZIP) | Email templates and assignment rules |
| Quotes, Sales Orders, Invoices, Purchase Orders, Vendors and Price Books | Sharing rules, roles and profiles (recreated, not imported) |
| Custom objects (as custom modules) and custom field values | Integrations with other systems |
Two points cause most confusion:
- Custom fields are created, not copied. The wizard suggests new fields for columns it does not recognise, and you can create simple fields during mapping. Formula fields, multi-select lookups, sections and subforms cannot be created in the mapping step, so build those in Zoho's module builder first.
- Salesforce's export contains data only. The Data Export Service produces CSV files of your records. It does not include metadata such as validation rules, automation or page layouts, so there is nothing for Zoho to import on that side even if it wanted to.
This is not a weakness of either product. It is a good moment to rebuild your sales process deliberately rather than carrying across years of rules nobody remembers creating. Our guide to Zoho CRM customization covers modules, fields, layouts and scripts in more detail.
How do you export your data from Salesforce?
Most companies use Salesforce's Data Export Service (Setup > Data Export). Things to know before you rely on it:
- How often you can export depends on your Salesforce edition. Enterprise, Performance and Unlimited editions can export every 7 days; Professional and lower editions every 29 days. Plan your final export around that limit, because you cannot simply run another one the next morning.
- Tick the options for attachments and files if you want them. The export lets you include images, documents, attachments, Salesforce Files and Salesforce CRM Content. Leave them out and you will get the record data only.
- Large exports are split into several ZIP files of up to 512 MB each.
- Download links do not last. Download the files within 48 hours of the notification email or they expire.
- Downloads may be slow for large orgs. Backup vendors report that since the Winter '26 release Salesforce allows only one export file to be downloaded at a time, with a short wait between files. For a large org with many ZIP parts, allow time for this.
Salesforce's Data Loader is the alternative when you want object-by-object control or need to filter what you export (for example, only accounts touched in the last five years). Whichever method you use, keep an untouched copy of the full export somewhere safe. It is your archive if a question about old data comes up later.
What should you decide before you migrate?
The decisions that matter are made before you upload a single file:
- What to bring across. Old, unqualified leads, duplicate accounts and contacts with no email or phone add noise and storage cost. Agree a rule, such as "open records plus anything with activity in the last three years", and archive the rest.
- How Salesforce objects map to Zoho modules. Most map one to one (Opportunities become Deals), but custom objects need a decision: a custom module, a subform or a set of fields.
- What the sales process should look like. Rebuild stages, required fields and hand-offs as a Blueprint rather than copying old validation rules one by one.
- Which Zoho CRM edition you need. Custom modules, Blueprint, sandbox and some automation limits depend on the edition. Check this before you design, not after. Our Zoho CRM pricing guide explains the editions.
- Who owns the data. Users must be migrated first so records keep their owners, and inactive Salesforce users need a decision: create them as inactive users or reassign their records.
- What happens to integrations. List every system that reads from or writes to Salesforce today (website forms, telephony, email marketing, accounting, ERP) and decide how each one will connect to Zoho.
How do you keep relationships, owners and history intact?
A migration fails quietly when records arrive but lose their links: a contact without its account, a note without its deal, a deal owned by the admin who ran the import. To avoid that:
- Migrate users first. Zoho's help pages say record owners can only be associated once the users file has been migrated. Each user needs a first name, last name, email and Salesforce user ID.
- Keep the Salesforce IDs. Zoho links records using the migration IDs from your export, and those IDs must be unique across all modules. Do not strip or rename ID columns when cleaning the files.
- Check the parent before the child. Errors such as "parent record not found" or "child record not found" usually mean an account was excluded but its contacts were not. Fix the scope, not the error.
- Clean picklists and tags. Multi-select picklist values must be separated by semicolons, checkboxes must be True/False or 1/0, and tags have limits on number and length. Characters such as the vertical bar and angle brackets cause problems.
- Watch file sizes. Attachments are usually most of the data volume. Zoho's pages give per-file and total upload limits (the figures differ slightly between pages, so check the current ones), and skipped attachments can be added later without starting again.
For a broader view of migration method, including how to test with a sample before the full load, see our guide to Zoho data migration.
How should you plan the switch-over?
A safe Salesforce-to-Zoho switch-over usually follows these stages:
- Design. Map objects to modules, fields to fields and old automation to new Blueprints, workflows and functions. Write it down in one mapping document.
- Build. Set up modules, fields, layouts, roles and profiles in Zoho CRM before any data arrives.
- Trial migration. Run a full migration into a sandbox or a test account using a recent export, then check record counts, owners, links and a sample of records against Salesforce.
- Rebuild automation and integrations. Workflow rules, assignment rules, email templates, web forms and connections to other systems. Our list of Zoho CRM workflow rules is a useful starting point.
- Freeze and final export. Agree a cut-off, stop changes in Salesforce, take the final export (remembering the export frequency limit) and run the live migration.
- Verify and go live. Reconcile counts by module, spot-check key accounts with the sales team, then switch everyone to Zoho CRM.
- Train and support. People adopt a new CRM when it makes their day easier. See our guide on Zoho user adoption.
Keep Salesforce available read-only for a short period after go-live if your contract allows it, so the team can check anything that looks wrong. Do not let anyone keep working in both systems.
What should businesses in India, the UAE and East Africa watch for?
- India: many Salesforce orgs in India are connected to Tally or another accounting system through custom integrations. If you are moving to Zoho, it is often worth moving quotes and invoices to Zoho Books at the same time so sales and accounts work from the same records. Design consent and retention rules for customer data with the Digital Personal Data Protection Act in mind.
- UAE and GCC: check whether you need Arabic names or bilingual fields on accounts and contacts, and whether your Salesforce org holds data for several legal entities. Plan how entities, currencies and territories map in Zoho CRM before migration.
- Uganda and East Africa: teams often rely on WhatsApp and phone more than email. Decide early how calls and chats will be logged in Zoho CRM, so the activity history you migrate is continued rather than replaced by messages outside the system.
What are the common mistakes?
- Migrating everything. Ten years of dead leads make search slower, reports noisier and storage more expensive.
- Copying Salesforce instead of redesigning. Rebuilding every old rule one for one recreates the complexity you were trying to leave.
- Importing records before users. Every record ends up owned by the person who ran the migration.
- Skipping the trial run. The first full migration always shows mapping issues. Find them in a test, not on go-live day.
- Forgetting the export limits. Teams plan a final export for the cut-off weekend and then find they used their weekly export a few days earlier.
- Leaving integrations to the end. If the website form still posts to Salesforce after go-live, leads go missing.
Planning this for your business?
A Zoho-certified consultant can review your setup on a free call and tell you where to start.
Frequently asked questions
Can Zoho CRM connect directly to Salesforce to migrate data?
Zoho's help pages describe a file-based route for Salesforce: you export your data from Salesforce as CSV files or a ZIP, then upload them to Zoho CRM's migration wizard. Zoho offers direct API-based migration for some other CRMs, but not for Salesforce in the pages we checked in November 2026.
Will my Salesforce workflows, Flows and Apex code move to Zoho CRM?
No. Salesforce's data export contains records, not metadata, and Zoho's migration tool imports data. Workflows, Flows, Apex, validation rules, approval processes, reports and dashboards need to be rebuilt using Zoho CRM's Blueprint, workflow rules, Deluge functions and analytics. Treat this as a chance to simplify your process.
Are notes, activities and attachments migrated?
Yes. Zoho's Salesforce migration supports notes, tasks, events, calls and attachments, as long as they are in your export. Tick the option to include attachments and files when you schedule the Salesforce export, and keep the attachments folder in the ZIP. Very large attachment sets can be added after the main migration.
Can I undo a migration if the mapping was wrong?
Yes. Zoho CRM lets you undo a migration from Import History, after which you can fix the mapping and run it again. This is why a trial migration in a test account or sandbox is so useful: you can repeat it until the counts and links are right.
Should we migrate all our historical data?
Usually not. Bring across open records, active customers and the history your team actually uses, and keep the full Salesforce export as an archive. Agree the rule with sales, support and finance before you start, so no one is surprised by what is missing.
Planning a move from Salesforce?
OHO Solutions is a Zoho Premium Partner, founded in 2019, with 25 Zoho-certified consultants in Kochi and Dubai. We help businesses in India, the UAE and GCC, Uganda and East Africa, and global markets plan Salesforce-to-Zoho CRM migrations: data mapping, clean-up, trial runs, rebuilding automation in Blueprint and workflows, and reconnecting integrations. Engagements can be fixed-price, time-and-material or project-based. Book a consultation to review your Salesforce org and what a move would involve.



