How do you move to a new CRM without losing your history?
By Matthew Eagle
Founder, Eagle AI Agency. Eight years as a staffing account executive.
Published . Updated .
We moved a small firm's years of CRM history into a new system and checked every record. The next day they told us the notes had not come over. They had.
You move to a new CRM without losing history by copying everything in, deleting nothing, and checking every record against the original field by field instead of trusting a count. Then you check that the old history actually shows up where your team reads it, because history that moved but cannot be seen feels exactly like history that was lost. We learned the second half the day after a move we had already verified.
What happened the day after the move?
The team told us their old notes had not come over, and every one of them had.
We had just moved a small firm off the CRM it had used for years and into a new one we built for them. The owner's rule was simple: keep everything the way it was, and only delete if two records are being merged. Companies, contacts and years of activity went across, and every field was checked against the original export before we called it done.
Then a member of their team opened a task and could not find the old notes. From where they sat, years of history were gone.
Why did complete data look missing?
The data was complete, but the screen they used never showed the field it landed in.
The old notes were stored on each task, just not in the notes log the team actually reads. And where the old history did show, it was one long run-on block. The old system exported years of updates as a single paragraph with no line breaks, so even someone who found it could not read it.
A count would have said the move was perfect. It was perfect, and it still failed the person using it.
What can look fine on a count and still be wrong?
Most migration problems pass the obvious check. Here is what we hit on this one, in the order we found it.
What a count would not catch in a CRM move
| What we checked | Why a count would not catch it | What we did |
|---|---|---|
| Every field matches the original | A record can exist with the wrong value in it | Compared every field to a fingerprint of the original, and caught one name that picked up a typo on the way in |
| Old tasks do not fire reminders | Years of old due dates look like overdue work to a new system | Marked imported history as already reminded before go-live |
| Old dates land on the right day | The old history carried local times with no time zone | Converted each one, so no note shifted by hours |
| History shows where the team works | The data can be there while the screen ignores it | Split the old history into separate dated entries in the notes log |
| Contact details are in real fields | The old system kept addresses and phone numbers in one free-text box | Pulled them into proper fields and kept the full original stored behind the scenes |
How did we fix the history so the team could use it?
We split the old history into separate, dated entries, each with its author, and put them in the log the team already reads.
The old system wrote a small header every time someone updated a task, naming who updated it and when. We used those headers as the break points. Each one became its own entry with the right author and the right time. Then we compared the new entries, joined back together, against the original text to prove not a word was lost.
The original block stayed where it was. Nothing was overwritten.
What happens when records disappear after the move?
You ask before you restore anything, because the owner may have removed them on purpose.
A few days after go-live, a batch of companies was gone from the new system. We never delete, so someone on their side had. The easy move was to put them all back from the export.
We asked first. The owner had removed them on purpose, because they should never have come over in the first place. Restoring them would have undone a cleanup the owner had just finished.
Keeping the raw export is what makes asking safe. Anything can still be brought back, so there is no rush to guess.
How do you plan your own CRM move?
Plan it as a copy with checks, not a transfer you hope worked.
How to plan a CRM move
- 1Decide what comes over with the owner, in writing. People who have left, old history, inactive records. Make it their call, not the tool's default.
- 2Export everything first and keep the raw file. It is your undo button for months.
- 3Copy in, never overwrite or delete. Fill blanks on existing records, leave anything that is already there.
- 4Check every field against the original, not just the totals.
- 5Switch off anything that reacts to old data: reminders, automations, emails to customers.
- 6Open the new system as the person who will use it and look for the old history on the screens they work in.
- 7When something looks missing, check the data before you reload it. It is usually there and just not on screen.
We set up and run CRMs for small teams as part of our sales work. The wider lesson, that a check which passes is not the same as a job that works, is the same one behind what breaks when you automate a process nobody is watching.
Questions people ask
Should I bring over all my old CRM history or start fresh?
Bring it over unless you are sure nobody needs it. Old notes are often the only record of why a client is set up the way they are, and the person who wrote them may have left.
How do I know nothing was lost in the move?
Compare every field of every record against the original export, not just the number of records. A count tells you the records exist. It does not tell you they are right.
Why does my old history look like one long paragraph in the new system?
Many systems export years of updates as a single block of text. It can be split back into separate dated entries using the headers the old system wrote each time someone updated a record.
What if my team says data is missing after the move?
Check the data before you reload anything. In our case every note was there and the screen simply was not showing it.
If you are switching CRMs and want every record to come across intact and usable, book a call.
More notes
- What stops AI outreach from sending the wrong message?This week a prospect received our AI's private note about them as the opening message of a sequence. Here is how it got through, how we made sure it was the only one, and what checks the words now.
- Why do verified emails still bounce?This week a list that passed two separate email checks still bounced hard enough to stop its own campaign. Here is what the checks missed, and what we now run before every send.
- Why did the link in your email open a warning page?We approved an email with a clean payment link. Our customer clicked it and landed on a warning page instead.
- Can you use AI on work that is under an NDA?A confidentiality agreement that never says the word AI can still rule out the tools you were about to use.
- Is your outreach broken, or is the benchmark wrong?The fastest way to wreck a campaign that is working is to measure it against a number that came from somewhere else.
- Do more pages actually help your website rank?The advice to publish more assumes pages are the unit of measurement. They are not, and a site full of near identical pages can be worth less than a site with a handful of good ones.
- How do you check if your cold email is going to spam?We spent days proving our email was landing in spam. Every test was pointed at a kind of mailbox almost nobody on the list used.
- Should a staffing firm hire a recruiter or rent a desk?Most small staffing firms are not short of a recruiter. They are short of a recruiter they can afford to carry while one ramps.
- Why does AI make things up, and how do you stop it?A model handed something unusable does not stop. It produces something plausible, and it will produce a different plausible thing the next time you ask.
- What breaks when you automate a process nobody is watching?Automation rarely fails loudly. It fails quietly, and keeps reporting that it is fine.
- Why did your cold outreach run out of leads?Usually it is not the message. You have simply run out of people to send it to.
- Do you need to hire a salesperson, or a system?The honest answer depends on one thing, and it is not budget.
- What do you do about sales when you are already at full capacity?The trap is not that you are too busy. It is that being busy feels like being safe.
Want the version of this for your business?
Twenty minutes, your actual situation, a straight answer about what we would do first.
20 minutes. You leave with a straight answer.