ZUUZStart free trial

← Back to blog

CRM Migration: Switch CRMs Without Losing Deal History

CRM migration for sales teams of 3 to 50: what to export, how to map fields and dedupe, a cutover week plan, and the deal history most switches lose.

CRM Integration

A CRM migration moves your records, activity history, emails, files and custom fields from one CRM to another. To keep deal history intact, export activities and attachments separately from records, store every old record ID, map stages and owners before importing, dedupe with a crosswalk, and keep the old CRM readable until five real deals check out.

TL;DR: Most CRM migrations lose the story behind each deal, not the deals. Record exports carry properties and associations; notes, emails and files usually need separate exports. Export by layer, keep legacy IDs, map before importing, dedupe with a crosswalk, and run the Deal History Test before switching off the old CRM. ZUUZ, the agentic AI CRM, has no CSV import today: its agents rebuild leads and deals from the last 90 days of conversations, or ZUUZ runs alongside the CRM you keep, so nothing migrates.

Key Takeaways
  • A CRM migration has seven data layers: records, associations, activities, emails, attachments, custom fields and history such as stage changes. Each one exports differently.
  • HubSpot's record export covers current property values and associations; for notes, calls and emails it points to individual record exports, activity reports or the engagements API, as of November 2026.
  • Original timestamps, owners on old activities, stage-change history and email threads are the items most often lost, because importers create new records rather than copy old ones.
  • The Deal History Test checks five real deals end to end before the old CRM goes read-only.
  • ZUUZ has no CSV import today. Teams either let ZUUZ agents rebuild records from the last 90 days of conversations, or keep their CRM and run ZUUZ alongside it.

Picture a twelve-seller team on the Monday after its CRM switch. The contacts are there. The open deals are there, with the right amounts. Then a rep opens her biggest renewal and finds a deal with no history: no notes from the pricing call, no email where the buyer asked for net-60 terms, no signed order form from last year. The record says what the deal is. It no longer says how it got there. This scene is an illustration, but it is the most common way a CRM migration fails for a small team.

This guide is for a team of 3 to 50 sellers where the owner or sales manager runs the switch, with one admin or none. It assumes the decision to move is made; if not, start with how to choose a CRM.

A tour of ZUUZ, the agentic AI CRM, and the deals a CRM misses when nobody logs the conversation

What a CRM Migration Actually Moves

A CRM is seven layers, and only the first two come out of a standard export cleanly. Build this inventory before anyone clicks Export.

Data layerExamplesComes out in a standard record export?What breaks if it is left behind
RecordsContacts, companies, deals, leadsYesThe pipeline itself
AssociationsDeal to contact, contact to companyUsually, as ID columnsDeals float free of the people buying
ActivitiesNotes, calls, meetings, tasksOften not; separate export or APIThe reasoning behind every stage
EmailsLogged threads, timestamps, participantsRarely in bulkWhat the buyer actually agreed to
AttachmentsQuotes, order forms, contractsRarely; separate file transferProof of price and terms
Custom fieldsRenewal date, lead source, contract termValues yes, definitions noReports and filters that depend on them
HistoryStage changes, owner changes, create datesMostly noCycle time and win-rate reporting

A team can live without most old marketing contacts. It cannot live without the email where a customer agreed to a price, or the order form that proves it. Rank the layers by what a rep needs in the next 90 days.

What to Export Before You Switch CRMs

Export in layers and keep the files: once the contract ends, they are the only copy you control.

Records and associations

Export every object you use: contacts, companies, deals, leads, products and any custom objects. Choose the option that includes all properties and associations, not just the columns in your current view. HubSpot's export records documentation describes three options (properties in the view, all properties, or all properties and associations), notes that download links expire after 30 days, and recommends CSV for wide exports because XLS stops at 256 columns, as of November 2026. Check your own CRM for the same traps before you start.

Activities and notes

This is where most migrations quietly lose history. HubSpot's same page says a standard record export does not carry activities such as calls and notes; it points instead to exporting an individual record's data, exporting certain activity reports, or using the engagements API, as of November 2026. Other CRMs differ in detail, but the pattern holds: activities live in their own tables and need their own export, with the parent record ID on every row.

Emails

Logged emails are activities in most CRMs, and full bodies often do not survive a bulk export. Decide early which matter: usually threads on open deals and on customers renewing in the next year. The rest can stay in an archive or the mailbox.

Attachments and files

Files are usually stored outside the record tables. Salesforce's Data Export Service has a separate option to include images, documents and attachments, and Trailhead notes that weekly exports are available in Enterprise, Performance and Unlimited editions, Professional Edition gets only a 29-day cadence, and the zip files are deleted 48 hours after the notification email (source: Salesforce Trailhead, Export Your Data, as of November 2026). Download them the day they arrive. HubSpot's own CRM migration process treats attachments as a one-time transfer outside its ongoing data sync, as of November 2026.

Custom fields and configuration

Export field definitions, not only values: type, picklist options, object, and the reports or automations that use each field. Write down pipelines and stages. All of it must exist in the new CRM before the first import.

Thinking of Switching? See What Your CRM Is Missing First.

ZUUZ connects to the sales inbox, calendar, meetings and calls, and shows the deals your current CRM never recorded, within 72 hours.

Map Fields, Stages and Owners Before Anything Imports

A mapping document is a spreadsheet with one row per source field and five columns: source field, target field, transformation, who signs it off, and how you will check it. It takes a day for a small team and saves a week of cleanup.

Source fieldTarget fieldTransformationHow to check it
Opportunity IDLegacy ID (new text field)Copy as text, never as a numberUnique on every imported deal
Opportunity ownerDeal ownerUser lookup by emailNo deal assigned to the importing admin
StagePipeline stageValue map, old to newOpen deal count per stage matches
Created dateOriginal created date (new field)Date format to target's standardSpot check ten old deals
Contract endRenewal dateCreate field first, then mapNo renewal in the next year is blank
AmountDeal valueCurrency code keptTotal open value matches

Three rules decide whether the history survives. First, add a Legacy ID field to every object and fill it on import. Every later step, from linking notes to merging duplicates, depends on it. Second, map users before records. If an owner's email does not exist in the new CRM, many importers assign the record to whoever ran the import, and a year of deals ends up under the admin. Pipedrive's migration help page makes the same point: start the migration before users and pipelines exist and the data belongs to the person who started it, as of November 2026. Third, store dates you cannot overwrite. Most importers set the create date to the import day, so keep the original in its own field.

Stage mapping deserves its own meeting: merging nine stages into six changes what last year's win rate means. If two-way sync between systems is part of the plan rather than a one-time move, field ownership and conflict rules matter more than this table, and how bidirectional CRM sync keeps records current covers that case.

Dedupe Without Breaking Deal History

Deduplicate before the import, in the export files, not after. Once duplicates are in the new CRM, merging them can orphan activities that were attached to the losing record.

  1. Match contacts on email address first, then on name plus company domain. Never on name alone.
  2. Match companies on domain. Treat subsidiaries and regional offices as separate unless the team sells to them as one account.
  3. Do not merge deals by name. Two deals called "Northgate Partners renewal" are often two years of the same contract, and both belong in the history.
  4. Pick a surviving record for each duplicate set, and write every losing Legacy ID into a crosswalk sheet: old ID, surviving ID.
  5. Use the crosswalk to repoint activities, emails and files to the surviving record before importing them.

The crosswalk is the step most guides skip. Ongoing cleanup after go-live is a separate job, covered in CRM hygiene for sales managers.

Plan the Cutover Week for a Small Sales Team

A team of 3 to 50 sellers does not need a three-month program. It needs one owner, a test import, a short freeze and a fallback. Here is a cutover week that fits a team with one admin or none.

  1. Monday: run a test import of 20 records across every object, including five deals with notes, emails and files. Check them by hand.
  2. Tuesday: fix the mapping. Rerun the test until all five deals look right.
  3. Wednesday afternoon: freeze the old CRM. Reps keep selling, but log new notes in a shared doc for two days.
  4. Wednesday evening: run the full export and import, in order: users, companies, contacts, deals, then activities, emails and files.
  5. Thursday: run the Deal History Test below. Load the delta, anything that changed after the export, from the shared doc.
  6. Friday: switch reps to the new CRM and set the old one to read-only. Keep it readable for at least one full sales cycle or until the contract ends.

Time the cutover against the old contract: a month of two CRMs is cheaper than a rushed migration. Switch off integrations that write to the old CRM during the freeze, or forms and email sync create records the export never sees. Once the switch is done, a week-by-week implementation plan covers rep onboarding and the first month.

What Usually Gets Lost in a CRM Migration

The losses follow a pattern. Each item below is lost for a structural reason, which means each one can be caught with a specific check.

Commonly lostWhy it disappearsHow to catch it before cutover
Email threads on dealsBodies not in the bulk exportOpen three deals and read the last email
Original create and close datesImporter stamps the import dateCompare ten old deals' dates side by side
Owner on old activitiesUser not mapped, falls to the adminFilter activities by owner after import
Stage-change historyAudit logs do not export as recordsExport a stage history report and archive it
Signed quotes and contractsFiles stored outside record tablesOpen the file on every renewal deal
Picklist valuesOption missing in target, value droppedCount blanks per mapped field
Open tasks and follow-upsTasks skipped or imported as doneCount open tasks per rep, before and after
Automations and reportsConfiguration never exportsRebuild the five reports managers use weekly

Two of these deserve a decision rather than a fix. Stage-change history rarely imports cleanly, so export a report and keep the file. Old email often does not need to move, because it still sits in reps' mailboxes. What matters is that new conversations reach the new CRM from day one; the CRM data quality guide explains why records decay after a fresh start.

The Deal History Test, With a Worked Example

Record counts tell you the import ran. They do not tell you the history survived. The Deal History Test checks what a rep would actually open on Monday morning.

The Deal History Test: did the deal history survive the CRM migration?

  1. Pick five deals: two open, one won, one lost and one renewal due in the next six months.
  2. Open each in the old and new CRM side by side.
  3. Check seven things on each: owner, stage, amount, original dates, the last three notes, the last email thread, and the latest signed file.
  4. Score one point per check that matches. Five deals give 35 points.
  5. Below 32 points, do not switch the old CRM to read-only. Find the layer that failed, fix the mapping, and reimport that layer.

Here is a worked example, labeled as an illustration. A twelve-seller team moves 4,800 contacts, 1,100 companies and 310 open deals. Record counts match on the first full import. The Deal History Test scores 24 of 35. Owners, stages and amounts pass on all five deals. Original dates fail on all five, because the importer stamped the import date. The last email thread is missing on three deals, and the signed file on two.

Three fixes follow: an "original created date" field, an email export for open deals only, and a file transfer keyed to the Legacy ID. The second run scores 33, and the team switches a week late with history it can trust. A week of delay is cheap. An empty renewal record in front of a customer is not.

Keep Your CRM. Stop the Typing Instead.

If the real problem is empty records, ZUUZ runs alongside Salesforce, HubSpot, Zoho, Attio, Pipedrive, Dynamics 365 or Less Annoying CRM, with two-way sync and nothing to migrate.

What Most CRM Migration Guides Get Wrong

The top results are mostly written by CRM vendors and are useful on process. They share four blind spots.

They treat migration as a data project only

Few ask why the team is leaving. If reps never updated the old CRM, the new one will be just as empty in six months. The migration fixes storage. It does not fix capture.

They count records instead of checking deals

Counts catch a failed import. They miss a deal whose emails stayed behind. A five-deal side-by-side check catches both.

They assume connecting an inbox restores history

Connecting email to the new CRM usually logs mail from that point on. Whether past mail comes across depends on the product and its settings, so test it with one mailbox before promising reps their history will appear. Ask the vendor how far back the first sync reaches.

They assume a migration is needed at all

The HubSpot alternatives guide has a Switch-or-Fix Test and the Salesforce alternatives guide a Leave, Layer or Stay Test for that choice. Run one before a week of exports.

CRM Migration and ZUUZ: Rebuild From Conversations or Move Nothing

ZUUZ, the agentic AI CRM, approaches CRM migration from the other end. It does not offer CSV import today, and it has no public API or Zapier connection. So it cannot take your old export files and load them. What it does instead depends on which of two doors a team walks through.

Door 1: ZUUZ as your new CRM, rebuilt from conversations

A team that wants ZUUZ as its CRM connects the sales inbox (Gmail or Outlook), the calendar, meetings on Teams, Meet or Zoom, and calls on JustCall, GoTo Connect, CallTrackingMetrics or CallTools. On first connection ZUUZ looks back over the last 90 days of those conversations, and its agents create the leads, deals, contacts and follow-ups they find, each value with its source attached. When ZUUZ is unsure whether a message is sales, it asks ("Maybe sales?") instead of filing it. A deal's value comes only from a quote, purchase order or contract, so a deal nobody priced stays empty rather than guessed.

The trade-off is plain. History from before that 90-day window does not come across, so keep the old exports as your archive. What comes across is the live pipeline, rebuilt from what buyers wrote and said, which is the part a migration usually breaks.

Door 2: keep your CRM, and nothing migrates

Many teams that start a migration project want the outcome, current records, more than a new system. For them ZUUZ runs alongside Salesforce, HubSpot, Zoho, Attio, Pipedrive, Dynamics 365 or Less Annoying CRM as a revenue intelligence layer, with two-way sync. An admin approves the first match-up between ZUUZ and the CRM once. After that, agents create and update leads, deals, follow-ups and renewals in the CRM you already have, and the rep's own edits win. Reports, automations and years of history stay where they are. The details are on keep your CRM and the full list of connectors on integrations.

$120K
Pipeline surfaced within 72 hours at RA Technologies, a US IT services company, on the HubSpot instance it had used for two years, with the same team. Source: RA Technologies case study.

RA Technologies did not migrate. It kept HubSpot, and the pipeline that had been sitting in the sales mailbox reached the CRM. One team's result is not a benchmark, but it shows what a team considering a switch should check first: whether the old CRM is the problem, or the empty records inside it.

From an operator's seat, the part teams do not budget for is the second empty CRM. In IT services and distribution sales, a switch gets approved, the import lands clean, and within two quarters the new records are as stale as the old ones, because the same busy people are still meant to type. Teams that fix capture first often find they no longer want to move.

Either way, every lead and deal the agents create has a one-click undo, and every value shows its source. For the wider choice, see AI CRM vs traditional CRM.

Run the Deal History Test on ZUUZ. Connect one rep's mailbox, calendar and call platform, with or without your current CRM. ZUUZ reads the previous 90 days and the first records appear within 72 hours. Compare five deals it built with the same five in your CRM before deciding whether to migrate. 14-day free trial, no credit card: https://zuuz.ai/trial

When ZUUZ Is Not the Right Choice

Being clear about limits saves everyone a wasted trial. ZUUZ is the wrong fit for a CRM migration when:

  • You need to load years of history from files. There is no CSV import, public API or Zapier connection today. A team whose priority is moving a full archive into a new system should use a CRM with a native importer or a migration service.
  • Deals move on LinkedIn, Slack or WhatsApp. ZUUZ does not capture those channels today, so records built from conversations would miss them.
  • You need a dialer or outbound sequences. ZUUZ does not dial or send sequences. Pair it with a dialer it reads from, or choose a CRM with both built in.
  • You need revenue projections or numeric scores. ZUUZ does not forecast and gives no lead or deal scores. It flags risk in plain words.
  • You need full reporting from day one. ZUUZ reports are partial, so teams with heavy reporting needs keep those in their main CRM.
  • Your buyer requires SOC 2 Type II today. ZUUZ has completed SOC 2 Type I, and Type II is in progress.

For moves between traditional CRMs, use the vendor importers; Pipedrive alternatives, the best CRM for sales teams of 3 to 50 and the switching hub compare options.

Rebuild the Live Pipeline From Conversations. First Records Within 72 Hours.

Connect one mailbox and see the leads and deals ZUUZ agents find in the last 90 days, each with its source attached.

Frequently Asked Questions

What is CRM migration?

CRM migration is moving your sales data and setup from one CRM to another. It covers records such as contacts, companies and deals, plus associations, activities, logged emails, attachments, custom fields and configuration like pipelines and reports. The hard part is rarely the records. It is keeping the history attached to each deal so reps can still see what was said and agreed.

How do I migrate CRM data without losing deal history?

Export each data layer separately, including activities, emails and files, and keep the old record ID on every row. Map users, stages and fields before importing, dedupe in the files with a crosswalk, and import in order: users, companies, contacts, deals, then activities. Check five real deals side by side before switching the old CRM to read-only.

How long does a CRM migration take for a small team?

For a team of 3 to 50 sellers with standard objects, plan about two to four weeks: one to two weeks for the audit, exports and mapping, a week of test imports, and a cutover week with a short freeze. Heavy custom objects, many integrations or messy data stretch that. Time the switch to the old contract's end date so you are not rushing.

What data usually gets lost when switching CRMs?

The most common losses are email threads on deals, original create and close dates, the owner on old activities, stage-change history, attached quotes and contracts, picklist values with no match in the new CRM, and open tasks. Each disappears for a structural reason, such as files living outside record tables, so each can be caught with a specific check before cutover.

Should I migrate all historical data or only recent records?

Migrate what a rep needs in the next year: open deals, customers with upcoming renewals, and their recent activity, emails and files. Older closed deals and inactive contacts can stay in an archived export or a read-only copy of the old CRM. Moving everything adds cleanup work and clutter, while deleting records you are legally required to keep creates a different problem.

Can ZUUZ import data from my old CRM?

Not from files. ZUUZ has no CSV import, public API or Zapier connection today. As your new CRM, its agents rebuild leads and deals from the last 90 days of email, calendar, meetings and calls, each value with its source. If you keep your current CRM instead, ZUUZ syncs two-way with Salesforce, HubSpot, Zoho, Attio, Pipedrive, Dynamics 365 and Less Annoying CRM, so nothing migrates.

How do I avoid duplicates when migrating a CRM?

Deduplicate in the export files before importing, not in the new CRM afterward. Match contacts on email address, companies on domain, and never merge deals on name alone. Record each losing record's old ID against the surviving one in a crosswalk sheet, then use it to repoint activities, emails and files so no history is orphaned when duplicates are removed.

Do I need to switch CRMs, or can I fix the one I have?

Switch when the CRM itself is the problem: cost, missing capabilities or a structure your team has outgrown. If the real issue is that records are empty because reps do not log calls and emails, a new CRM inherits the same gap. In that case, keeping the current CRM and automating capture alongside it is usually faster and avoids the migration entirely.

Explore on ZUUZ

Stop losing deals to your inbox.Start winning with ZUUZ.