Migrating to a new CRM without losing history

Inventory the records and history you need

List contacts, companies, opportunities, activities, notes, attachments and custom records before exporting. Identify the relationships that make this information understandable. A contact file alone does not preserve which person participated in which commercial discussion.

Separate required history from obsolete or unnecessary data using approved retention rules. Check what the destination can import natively and what may need another method or controlled archive. Do not assume that exporting a CSV preserves emails, attachments or stage history.

Build a field and identifier mapping

Create a mapping sheet with source field, destination field, data type, transformation and validation rule. Preserve legacy record identifiers so migrated records remain traceable. Decide how owners, currencies, dates and inactive users will be represented.

Review matching and update behavior before importing. HubSpot documents record identifiers and other matching approaches, but destination rules and integration paths can differ. Test how blank values, duplicates and existing destination records are handled.

• Map fields and data types.
• Preserve legacy identifiers.
• Map owners and inactive users.
• Define date and currency handling.
• Test duplicate and overwrite behavior.

Run a representative rehearsal

Use a test migration containing simple and difficult cases, including multiple contacts, old notes, closed deals and suppressed records. Reconcile counts by record type and inspect relationships in the destination. Matching totals do not prove that history is attached correctly.

Ask sales users to retrieve an old conversation and continue an active opportunity from the migrated record. Test permissions, reports and connected tools without triggering unintended messages. Document unsupported history and agree how users will access it.

Control cutover and post-migration validation

Set a cutover window and define when the old system stops accepting updates. Capture changes made after the initial export through a tested final-transfer process. Pause relevant integrations and automation until destination records and exclusions have been validated.

Keep a secured source export and a documented rollback plan subject to access and retention requirements. Name the person who approves the migration and the team handling discrepancies. Retire the old system only after users can access the necessary history and agreed acceptance checks pass.

• Freeze or control source updates.
• Transfer final changes.
• Reconcile records and relationships.
• Verify suppression and permissions.
• Approve automation restart.
• Document acceptance and rollback decisions.