Inventory and clean a copy of your data, map fields and record relationships, test a small sample, and keep the original export unchanged until the new CRM has been checked.
Use the resources in this guide
This article uses public documentation and cited sources. Product claims have not been independently tested by Operleaf. How we research
A CRM move is a data and process change, not just a file upload. Before you transfer anything, decide which records are still useful, what the new fields mean, who should access them, and how you will confirm the move worked.
This checklist is a general operating template. Import options, field behavior, and export permissions differ by product and plan. HubSpot’s import-tool documentation and Zoho’s module import guide describe their own systems; check the current guides for the CRM you select. For a product shortlist, see HubSpot vs. Zoho CRM.
1. Name the reason for moving
Write down what the current system cannot do or what is changing. Examples might include assigning follow-up clearly, separating customer and prospect records, improving access control, or consolidating duplicate tools. Define two or three observable conditions that will show the new CRM is ready for everyday use.
If there is no clear problem, pause before migrating. A new system can reproduce old confusion and add another subscription without improving the work.
2. Choose a migration owner and a review window
Name one person accountable for the file, field map, import, validation, and sign-off. Identify who can approve changes and who will test common tasks. Pick a low-activity window if practical, and tell the team when to stop making edits in the old system or how new changes will be captured during the move.
Decide in advance how you can return to the prior workflow if the new system is not ready. Keep access to the old account until the owner has verified the records and essential work in the new CRM.
3. Inventory records and decide what should move
List each data type separately: contacts, companies, leads, deals, notes, activities, attachments, consent or communication preferences, and custom fields. The exact object names vary by product. For each group, mark it as move, archive, or exclude, and record why.
Remove obvious test records and identify likely duplicates in a working copy. Do not silently delete ambiguous records. Ask the responsible person to decide whether they should be merged, retained, or excluded. Preserve an untouched export in a restricted location and document who can access it.
4. Map fields and relationships before uploading
Create a mapping worksheet before opening the import screen:
| Source field | New field | Data type or allowed values | Required? | Transformation or cleanup | Validation sample |
|---|---|---|---|---|---|
| First name | First name | Text | If required by destination | Trim extra spaces | A real sample row, reviewed without exposing unnecessary personal data |
| Company | Company / account | Related record or text | Depends on destination | Normalize spelling before matching | Check a record with a company relationship |
| Status | Lifecycle stage / status | Controlled list | No | Map each old value to an agreed new value | Review one record for every source status |
| Next follow-up | Task due date | Date/time | If the process needs it | Confirm timezone and date format | Compare the imported date with the original |
Use each CRM’s sample file and import instructions to confirm column format and required fields. HubSpot describes mapping columns to CRM properties and defining record relationships. Zoho’s import guide describes downloading a sample file, selecting how records should be added or updated, and mapping import columns. Do not assume two products interpret a similarly named field the same way.
5. Decide duplicate and matching rules
Choose the identifier used to match an incoming row to an existing record, such as a provider record ID or another stable unique field supported by the destination. Email addresses can be useful for contacts but may be absent, shared, or changed; they should not automatically be treated as a universal key for every object.
Document what the import should do with a match: update, skip, or send for manual review. Be especially careful with updates. Zoho’s current import documentation notes that records can be added, updated, or both depending on the selected option, and that updates to existing records cannot be undone through the same add-record undo path. Confirm the current behavior in your target system and keep a recovery copy.
6. Run a small pilot
Prepare a sample that covers ordinary records and edge cases: a missing optional field, an international phone number, a company relationship, a duplicate candidate, a closed deal, and a value that needs mapping. Use only the minimum personal data needed for the test, and follow your internal privacy controls.
Import the sample into a test area if the provider offers one, or a clearly marked limited set. Check counts, field values, relationships, dates, ownership, permissions, and duplicate handling in the CRM itself. Ask a second person to repeat one or two everyday tasks using the migrated records.
7. Import in controlled groups
After the pilot passes, divide the remaining data into understandable batches, such as one record type at a time. Record the source file name, batch, date, operator, row count, result, and any skipped or rejected rows. Avoid making simultaneous edits in both systems unless you have a written reconciliation rule.
After every batch, compare source and destination counts and inspect a sample from each important record type. Keep failed rows separate, diagnose the cause, and correct the mapping before retrying. Do not rerun a whole batch blindly if it might create duplicates.
Reconcile keys before approving the move
Two exports with three rows can contain different records. Preserve a stable source identifier in a destination column; if the new CRM replaces it, export the old key too. Do not treat unrelated system IDs as equivalent.
Paste CSV with headers and a comma, semicolon or tab delimiter; both inputs must use the same delimiter. Key columns can have different names. Quoted fields and embedded newlines are supported. Blank lines are ignored; leading and trailing key spaces are trimmed and case matters. This tool accepts 20,000 data rows and two million characters per input; these are not provider limits.
Check migration keys and a field
Compare two CSVs using a stable identifier. You can also check the text of a required field preserved in both files. Use fictional data or IDs without confidential information.
Optional: select a UTF-8 CSV up to 2 MB (2,000,000 bytes). It is read in this tab and replaces the text on that side; it is not sent to the site. You can also paste its content below.
Ready to compare
This does not validate relationships, attachments, permissions or the meaning of a value. Text is processed only in this tab. The downloaded CSV contains IDs and, when you select a field, its values. Store it securely.
Download the CRM field map as CSV to record objects, fields, formats, transformations, relationships and ownership. Its four rows are proposals with fictional IDs; fill in your CRM’s destination fields and record the observation before changing “Not checked.” It is not an import-ready file. Do not store passwords, credentials or personal case files in the map.
Repeat the check with downloadable files
Download the fictional source, the destination with issues and the destination with matching keys. These comma-delimited CSVs have an id header and three data rows, with no personal information. Select them using “Open source CSV” and “Open destination CSV”, or paste their contents. Use UTF-8 text CSVs up to 2 MB each; the file picker does not send files to Operleaf. Choose the delimiter and columns before comparing.
The first destination should be missing C02 and C03, contain unexpected C04 and repeat C01. The other should match three unique keys despite a different row order. To check manually without JavaScript, look for each source ID at the destination, repeat in reverse and count each key’s occurrences. Three matching keys do not prove that fields or relationships match; those still need review.
Equal counts can hide two missing records
The fictional example contains C01, C02 and C03 at the source, and C01, C01 and C04 at the destination. Both have three rows. The checker calculates two missing keys, one unexpected key and one repeated destination key. These are algorithm fixtures, not a migration performed in a provider’s system.
If differences appear, review filters, omitted batches, transformations and duplicate rules before repeating an import. Even when keys match, check critical fields, relationships, attachments and permissions. HubSpot distinguishes properties and associations; Zoho distinguishes module exports and full backups. A contacts CSV does not establish that attachments arrived.
Matching keys can hide changed fields
Repeat the check with the three-record source and the destination with changed fields. C01, C02 and C03 all match. Enable “Also compare a required field” and select status at the source and stage at the destination: C02 changes from open to closed, while C03 loses closed. Expect two different values and one empty destination field, despite no missing IDs.
This is an executed check of our comparator using fictional files, not an import performed in a CRM. Comparison is literal: spaces, case and different date formats count as differences. It does not normalize meaning. Repeated IDs remain ambiguous and their fields are not compared. Download the report to review all issues; the screen shows up to 30 per block. Relationships, attachments, permissions and unselected fields still require review.
8. Validate real work and access
Before switching the team, verify the tasks the CRM is meant to support:
- Find a contact and see the correct related company or deal.
- Assign an owner and record a next action.
- Find notes and activities needed for an active customer request.
- Confirm the right people can view and edit the right records.
- Export a small sample and check that the resulting file is readable.
- Review how opt-outs or other communication preferences are represented.
Do not assume that the import succeeded just because the tool displayed a success message. Review rejected rows and inspect the records in context.
9. Switch over, then keep the old source available temporarily
Tell the team what system is now authoritative, where to record new inquiries, and whom to contact internally when a record looks wrong. Keep the old system available in read-only mode if the service and your account terms permit it. Define a specific review date for deciding when to close it, rather than keeping parallel records indefinitely.
If validation reveals a material problem, pause the switch, record the affected data, and follow the recovery plan. Do not erase the source export or cancel the old account until the owner has confirmed that the new system supports the required work and that retained records are handled appropriately.
Worked example: ten contacts before moving the customer base
Illustrative scenario: a maintenance company wants to move its records to another CRM. Start with ten test contacts, two companies, and three related opportunities; retain source identifiers.
The pilot includes “Northside LLC” and “Northside, LLC,” a phone number beginning +1, and a task due October 3. Agree normalization before importing. Do not merge contacts merely because they share a surname.
After import, check all ten contacts, company relationships, three opportunities, phone number, and date. If contacts arrive but opportunities lose their company links, the pilot fails despite a correct contact count.
Proceed only when another person can find a test customer, understand the history, and record the next follow-up. Until then, correct the mapping and keep the previous system available.
Copy-and-use sign-off
- Purpose and success checks agreed
- Migration owner and review window assigned
- Record types classified as move, archive, or exclude
- Untouched export stored with restricted access
- Field map, controlled values, and relationship rules reviewed
- Duplicate and update behavior confirmed in current documentation
- Pilot imported and validated by a second person
- Batches logged and rejected rows resolved
- Permissions, follow-up tasks, related records, and sample export checked
- Team told which system is authoritative and how to report internal issues
- Old system closure date set after successful review
Keep the sign-off with the field map and import log. For a CRM selection decision, use the software evaluation scorecard; after the move, establish an owner and next action for each new inquiry with the lead follow-up workflow.
References & research notes
- Understand the HubSpot import toolOfficial source · Checked September 28, 2026
- Import data into a CRM moduleOfficial source · Checked September 28, 2026
- Zoho CRM export dataOfficial source · Checked September 28, 2026