CRM migration checklist for a small business

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:

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.

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.

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.