The Data Migration wizard in Zoho CRM ensures that your data is migrated accurately and helps you reduce much of the manual work. It automatically maps import files to CRM modules and import file columns to Zoho CRM fields. In the case of modules that are not already available, Zoho CRM creates them and maps the relevant files to them. It gives you a clear indication of the number files that are mapped, unmapped and any that are not supported.
Migrating to Zoho CRM can be an easy experience but in case you are stuck in any of the steps, please feel free to contact us at migration@zohocrm.com.
Availability
Permission Required
Users with Data Migration permission in their profile can access this feature.
Migrate Options
There are a few options to migrate. Zoho CRM provides a custom-made setup to migrate from Salesforce, other Zoho CRM accounts, Pipedrive, Highrise, Insightly, MS Dynamics, Maximizer or any other vendors.
You can migrate from Pipedrive, Capsule, Hubspot, Insightly, Highrise, Bitrix, and Bigin using API transfer. All you need is to feed the API key and the migration will start without any manual intervention.
Before you migrate
We recommend that you go through the following guidelines for an overview of the migration process.
Migration checklist
- File format: The supported format is CSV.
Checkbox fields: The values for checkbox type fields in the import file should be either "True" or "False”. Imported data from checkbox fields is converted in Zoho CRM as follows:
- If checkbox is selected, True or 1
- If checkbox is not selected, False or 0
Characters not allowed: Data in the file to be imported should not contain the following characters:
- Double quotation marks ("): use only as a field delimiter
- Vertical bar (|)
- Angle brackets (<>)
- Multi-select pick list fields: The values should be separated by semi-colons in the import file.
Migrating Tags: Tags should be present in your file as comma separated values. If a record has more than 10 tags, only the first 10 tags will be migrated and each tag can have a maximum of 25 characters.
Migrating File Upload & Image Upload Fields : File Upload, Image Upload fields, picklist history, multi-select lookup, and subforms can be migrated to a specific module
.
Migrating Subforms: Subforms can be migrated along with the parent module. Let's say the Students module has two subforms: Educational Details and Achievements. So, during migration, you must map the file to the Students module and the appropriate subform. The module-file mapping will display the name of the subform along with the module name (Educational Details-Students). Before migrating you must ensure that the parent module and appropriate subform are already mapped.
- Update Mandatory Fields: You need to have data for all the default mandatory fields in Zoho CRM in your import file. For example, "Last Name" is a mandatory field in Zoho CRM. Make sure that the "Last Name" column in your Leads import file has values. For the records that do not have a last name, you need to specify the values as 'not provided' or 'none'. You can also assign default values. Any records that lack values for the dafault mandatory fields will be ignored during import. During migration you will get an option to fill the mandatory blank values.
Drop-down List: All data values displayed in the dropdown lists must exist in the corresponding Zoho CRM fields.
For example, if you plan to import account information that contains a value for the Industry Type drop-down list, before you import the account information, make sure all the industry values in the source file already appear in the dropdown list. If the values do not exist, you must either change the values in the source file to match the existing values in Zoho CRM, or have your administrator add the new values. It will be added even if the values are absent.
- Field names: Make sure the first row of data (records) in the source file contains the column headings or field names rather than the actual data values. These heading field name values help identify the data when you map the new data to the existing fields in Zoho CRM. Column names will be the field names.
- Blank rows in the import file: More than 10 blank rows in the file might indicate the end of the file. Data after the blank rows will be ignored during import. Make sure not to leave blank rows in between rows of data.
User data: Always migrate the user details into your Zoho CRM first. Then make sure the record's Owner ID field is mapped with the Record Owner ID in Zoho CRM. For example, when you migrate leads, map the Leads Owner ID field from the file with corresponding field in Zoho CRM.
Note
- In large migrations, attachments often constitute most of the data and might exceed upload limits. If that happens, you can add skipped attachments at the end and continue without starting a new migration. If you wish to complete the migration without adding the skipped attachments, simply click Go to Home Page.
The modules and their Zoho-defined mandatory fields are listed in the table below. Please make sure to map these fields when you import. There may be other mandatory fields in each module, but you can always customize and mark the fields as non mandatory, if required.
Module
| Mandatory Fields
| Module
| Mandatory Fields
| Module
| Mandatory Fields
|
Leads
| | Cases
| - Case Origin
- Subject
- Status
| Products
| |
Accounts
| | Solutions
| | Vendors
| |
Contacts
| | Sales Orders
| | Price Books
| |
Deals
| - Deal Name
- Stage
- Closing Date
| Quotes
| | Invoices
| |
Campaigns
| | Purchase Orders
| | Calls
| |
Tasks
| | Events
| |
|
|
Upsert your missed files back to the database using the Upsert Operation:
If you have missed to migrate a few data from the source file and realized it after completing the migration, you can use the Upsert operation to restore them to your migrated database in Zoho CRM.
Upserting preserves the timeline of the data as present in the source file. Unlike the data import available for each module, the data restored to the CRM will bear the same time as recorded in your former CRM.

From field values, to subforms—either missed to migrate or missed to map during migration, your goal with this upsert operation could be to
- Restore the missing data with its original timestamp.
- Revert to the legacy data that was altered in the new system.
Either case, you are required to declare the upsert resolution to prevent duplication and to ensure accuracy from Untouched records or All
Records.
Declaring the upsert resolution means providing confirmation for your actions. That is, at this juncture of upserting you would have two datasets at play:
- Data already migrated to Zoho CRM
- File with data to upsert
Based on your goals and preferences, you can select either of the following options:
- After migration is complete, if you have started using Zoho CRM and make changes to records, then those changes are the most recent and hence could be considered more accurate. If so, you can select 'untouched' during upsert which will only modify those records which have not been touched after migration.
- Selecting "All records" would mean that regardless of whether the records were modified or not, all records will be overwritten with the information from the file. Please make sure you double check before proceeding as this action cannot be undone.
If you have populated empty fields in Zoho CRM, that was empty in the file, during the upsert transfer not to replace with empty fields for existing data.
Modules unsupported for upsert:
The following data types are not supported for the Upsert operation in Zoho CRM:
- Users
- Profiles
- Roles
- Deal- Contact role
- Invitees
- Services
- Appointments
- Notes
- PicklistHistory modules
- Bundles and Relationships like like Account-Product, Contact-Product, Deal-Product, Lead-Product, Campaign-ContactMembers, Campaign-Lead Members are not supported.
To Upsert
- Go to Data Administration > Import.
- Select the vendor you have migrated from and upload your file for upsert.
- In the Upsert Operation page, select the upsert resolution.
- Check the Don't update empty values for existing data if you would like not to replace existing data populated after migration.
- Click Save.
Note:
You cannot rollback all of your upserted data. Only new data inserted as part of upserting can be rolledback while existing data overwritten using the upsert file cannot be undone.
Post-migration summary:
After completing this upserting operation successfully, you will see the status of migration that details on mapped versus unmapped files. You can review the migration and if you agree with this, you can start your migration.
Be it upsert migration or a complete migration, once the process is over, we recommend you to take a look at the summary before you get started. This step is vital for you to start your process to be assured about the data you are going to be working on.
The summary page shows module name, its status, number of files added, updated, skipped, and total migrated files for each module. These aren't mere numbers. Imagine you haven't mapped a field or there are a few data skipped by the system; you can click on the number corresponding to the module and the status to view the number of records in that status. With this, you can start using Zoho CRM, confidently.

In addition to this, the files added to the Zoho CRM database can be viewed in the
Import History page.
SEE ALSO
Migrating data from: