The safest way to move CRMs is to treat it as a small project with a rehearsal: list every source of customer data, decide what’s worth bringing, map and clean it, run a test import, check it, then switch over on a set date with a way back if it goes wrong.
Most of the effort goes into the data, not the new software. And because a migration means handling every customer record you hold, it’s also the best chance you’ll get to bring your data protection house in order.
- Inventory every source first, including spreadsheets and inboxes, then decide what to migrate, archive or delete.
- Map fields, deduplicate and clean before you import, and always do a test import of a sample.
- Under UK GDPR, don’t carry over data you no longer need, and keep marketing consent records attached to each contact.
- Plan cut-over, a rollback route and training as carefully as the import itself.
Step 1 of 6
Inventory
List every place customer data lives, who owns it and how current it is.
Step 2 of 6
Triage
Decide what to bring, what to archive and what to delete.
Step 3 of 6
Map and clean
Match old fields to new ones, merge duplicates and fix formats.
Step 4 of 6
Test import
Load a few hundred records and check them by hand.
Step 5 of 6
Cut over
Freeze the old system, run a final import and switch forms and integrations.
Step 6 of 6
Close out
Train staff, delete stray exports and record what moved and when.
The ten steps below fill in the detail behind each stage.
The CRM migration checklist
1. Inventory every data source
List everywhere customer information currently lives: the old CRM, spreadsheets, the accounting package, email marketing tool, shared inboxes, booking system and any paper files. For each, note who owns it, roughly how many records it holds and how up to date it is. If you’re moving off spreadsheets for the first time, our piece on signs you need a CRM covers the usual suspects.
2. Decide what to bring, archive or delete
This is the step people skip. Not everything deserves a place in the new system. Typical rules are: bring active customers, open deals and recent enquiries; archive closed history you need for legal or accounting reasons; delete what you no longer have a reason to keep. The UK GDPR section below explains why the last category matters.
3. Map the fields
Build a simple table: old field name, new field name, data type, and any transformation (splitting “Name” into first and last name, converting “Y/N” into a tick box, translating old pipeline stages into new ones). Agree which fields are mandatory and which old ones you’re retiring. Pay special attention to relationships, such as which contacts belong to which company and which deals belong to which contact.
4. Deduplicate
Choose a unique identifier for each record type and stick to it. HubSpot, for example, uses email address as the unique identifier for contacts and company domain name for companies, and a Record ID overrides both if you include it. Salesforce’s Data Import Wizard can prevent duplicates by matching on account name and site, contact email address or lead email address. Merge duplicates in the source data before import rather than hoping the new system catches them.
5. Clean the data
Standardise phone numbers and postcodes, fix obvious typos in email addresses, make country and county values consistent, and remove test records. Flag records with missing essentials rather than importing them silently.
If the old data has been living in spreadsheets, expect this stage to take longest. Our guide on when to replace a spreadsheet with a custom app covers why those files drift out of shape.
6. Run a test import
Import a sample of a few hundred records into a test environment or a fresh account, then check them by hand. Are associations intact? Did dates come through in the right format? Do notes and activity history appear against the right person?
Source: HubSpot Knowledge Base, Set up your import file, checked 22 November 2026
Know your tool’s limits before you plan the full run. HubSpot accepts .csv, .xlsx and .xls files with one sheet each and fewer than 1,000 columns. On paid plans it allows files up to 512 MB, up to 1,048,576 rows per file and 500 imports in a rolling 24 hours; on free tools the limits are 20 MB per file and 50 imports. Salesforce recommends its Data Import Wizard when you’re loading fewer than 50,000 records into a supported object with fewer than 50 fields, and its Data Loader for bigger or more complex loads, scheduled imports and objects the wizard doesn’t support. Data Loader handles CSV files of up to 150 million records and is available on Enterprise, Performance, Unlimited and Developer editions.
7. Run both systems in parallel
For a short, defined period (often a week or two), keep the old system read-only or running alongside the new one. Spot-check that new enquiries, tasks and reports behave as expected. Don’t let parallel running drift on for months, or you’ll end up with two sources of truth again.
8. Cut over on a set date
Pick a quiet day, freeze changes in the old system, run a final delta import of anything added since the test, then switch website forms, email integrations and phone systems to point at the new CRM. Tell customers nothing has changed, because from their side nothing should.
9. Have a rollback plan
Before cut-over, take a full export of the old system and keep it somewhere secure. Decide in advance what would make you roll back (missing records, broken integrations) and who makes that call. Keep the old subscription active until you’re confident, even if it costs an extra month.
10. Train people and close the loop
Short, role-specific training beats one long demo. Afterwards, close down old copies: delete stray spreadsheets and exports, revoke access to the retired system, and record what you migrated and when.
UK GDPR and PECR points to get right
A migration is processing personal data, so the usual rules apply. This is general information, not legal advice.
Bring only what you need
Data minimisation (Article 5(1)(c)) requires personal data to be “adequate, relevant and limited to what is necessary”. The ICO says you should periodically review what you hold to check it’s still relevant, and that you “must not collect personal data on the off-chance that it might be useful in the future”. A migration is the natural time for that review.
Storage limitation (Article 5(1)(e)) says data should be kept “for no longer than is necessary”. The ICO expects you to set retention periods, review data regularly, and erase or anonymise it once you no longer need it. Note that the ICO treats pseudonymised data as still personal data, so stripping names alone doesn’t count as anonymising. Some records, such as those needed for tax, may have to be kept for set periods under other laws, and keeping them for that reason is fine.
Carry the lawful basis across
The ICO says you must determine and document your lawful basis before you start using personal information, and that you “should not swap to a different lawful basis at a later date without good reason”. Moving systems doesn’t change why you hold the data, so bring across whatever field or note records the basis for each group of contacts.
Consent records must move with contacts
If you send marketing emails or texts on the basis of consent, PECR and UK GDPR mean you need proof. The ICO’s consent guidance says your records should show who consented, when, how, what they were told, and whether and when they withdrew. It specifically gives a spreadsheet with “consent provided” written next to a name as an example of poor practice, and says to keep the evidence for as long as you’re relying on that consent.
In practice, map consent status, date, source and the wording version as proper fields, and import opt-outs and unsubscribes too. If an unsubscribe doesn’t survive the move, you risk emailing someone who asked you to stop. Our guide to email and SMS marketing rules in the UK explains the consent and soft opt-in rules, and B2B cold email law covers business contacts.
Keep an audit trail
Write down what you migrated, what you archived, what you deleted and why, with dates. It helps you answer any later question from a customer or the ICO, and it’s useful for your own team when someone asks where an old record went.
Keep the data secure in transit
Export files are full copies of your customer list. Store them in a restricted location, share them only with the people doing the work, and delete them when the project closes. If an agency or contractor handles the migration, they’re processing data on your behalf, and the ICO’s security guidance expects anyone processing for you to meet the same security standards, so put that and the deletion of copies in writing.
Common questions
How long does a CRM migration take?
It depends far more on the state of your data than on the number of records. A tidy single source can move in days. Several messy spreadsheets plus an old CRM with custom fields can take weeks of cleaning before the import itself.
Should we migrate old emails and activity history?
Bring recent history that staff genuinely use. Older activity can often sit in an archive export instead, which keeps the new system cleaner and fits the storage limitation principle better.
Planning a move
If you’re moving to a system built around your own process, or weighing that against HubSpot, Salesforce and Pipedrive, our custom CRM team can help plan the migration as part of the build.
Sources
- ICO: Principle (c): Data minimisation (accessed November 2026)
- ICO: Principle (e): Storage limitation (accessed November 2026)
- ICO: A guide to data security (2023, under review)
- ICO: A guide to lawful basis (accessed November 2026)
- ICO: How should we obtain, record and manage consent? (accessed November 2026)
- ICO: Guide to PECR, electronic and telephone marketing (updated 20 August 2025)
- HubSpot Knowledge Base: Set up your import file (accessed November 2026)
- HubSpot Knowledge Base: Import records and activities (accessed November 2026)
- Salesforce Developers: When to use Data Loader (accessed November 2026)
- Salesforce Developers: Data Loader (accessed November 2026)