CRM migration readiness: what to fix before the import

Decide what the new CRM must preserve

Begin with the decisions people need to make after migration. A salesperson may need the last conversation, the current opportunity and the customer’s preferred contact. Operations may need the agreed scope and handover status. Finance may need a stable customer reference. These needs determine what must move and what can remain in a searchable archive.

Do not migrate every field simply because it exists. Separate operationally necessary information from obsolete experiments, duplicate fields and unclear labels. Ask who uses each field, what action it supports and which system should maintain it. Archive decisions should follow your organisation’s retention requirements rather than a general desire to make the new database smaller.

Treat identifiers and relationships as the foundation

A person, company and opportunity are different records, even when they share a name. Build a mapping that preserves their relationships. Keep the original system identifier in a dedicated reference field where appropriate so that migrated records can be traced and reconciled without relying only on a changing company name.

HubSpot’s import documentation explains that unique identifiers are used to update records, avoid duplicates and establish associations. Its deduplication guidance describes additional behaviour that varies by record type and creation method. Read the rules for your target system before assuming that an import will recognise every duplicate or retain every relationship automatically.

Test the difficult records early

A sample containing only complete, simple contacts gives false reassurance. Include a company with several contacts, a contact linked to several opportunities, an inactive owner, an international phone number, a missing email address and records with long notes. Test special characters and dates in the formats your team actually uses.

Check more than the final row count. Open representative records and confirm associations, ownership, activity chronology and searchable context. Reconcile totals by object and meaningful business category. A matching number of contacts does not prove that their companies or open opportunities are correct.

A practical migration rehearsal

Imagine a service business moving from spreadsheets and an older CRM. The same customer appears under a trading name in one file and a legal name in another. Instead of merging by name, the team creates a reviewed mapping of customer references, imports companies first and checks a small set of associated contacts and deals.

The rehearsal reveals that former employees own several open opportunities. Those records enter a reviewed reassignment list before the final move. The team also discovers that old notes contain delivery instructions still used by operations. It adds a visible handover summary instead of expecting staff to search years of unstructured history.

Build a cutover checklist

Agree when the old system stops accepting normal changes, how urgent updates are captured during the move and who can approve reopening the old process. A rollback plan must consider new activity created after launch; restoring an old export alone can lose that work.

• Approve field mappings, source identifiers and association rules.
• Keep an access-controlled backup and a documented archive location.
• Rehearse with complex records and reconcile counts plus relationships.
• Pause or isolate automations that could contact migrated records.
• Define the final update window and ownership of exceptions.
• Give users a short guide to the new record structure and daily tasks.

Judge readiness by the working day after launch

Give the reconciliation work its own owner and time allowance. The people who know whether an account relationship is correct are not always the people operating the import tool. Reserve their availability during the rehearsal and cutover, with an agreed route for decisions that cannot be resolved from the exported data alone.

Ask a salesperson to run a realistic follow-up task in the rehearsal environment. Ask a manager to review open opportunities and an operations colleague to locate a handover. These exercises expose missing context more effectively than a demonstration of the import screen.

A migration is ready when the team can continue its work, explain where the information came from and resolve discrepancies without guesswork. Software features matter, but a clear data model, a tested cutover and a named decision owner do more to protect continuity than importing everything at once.