NuVentrec

Guides / Switching CRMs

Guide · Moving your data

How to switch CRMs without losing your history

Names and phone numbers move easily. What gets lost in a move is everything around them: who said stop, when you last spoke, which notes belong to which deal. Here is a plain order of work for a small team, and the checks that tell you nothing went missing.

By the NuVentrec team · Published October 12, 2026 · Sources last checked October 12, 2026 · General information, not legal advice

The short answer

  • List what you have before you export anything: contacts, deals, tasks, notes, calls, texts, files, and your do-not-contact list.
  • Move the do-not-contact list first. A person who opted out in the old system must be opted out in the new one before anyone can reach them from it.
  • Export to plain files and keep the originals untouched. Work on copies.
  • Do a trial import of a small piece, check it by eye, then import the rest and compare counts.
  • Keep the old system readable for a while, then dispose of the leftover copies on purpose.

Step 1: Take stock

The Federal Trade Commission's guide to protecting personal information starts with the same advice we would give for a move: "Know what personal information you have in your files and on your computers." It adds that "no inventory is complete until you check everywhere sensitive data might be stored."

For a CRM move, write one line for each kind of record and where it lives today:

  • People: contacts and leads, with their phone, email, mailing address and tags.
  • Work in progress: deals or opportunities and the stage each one is in, open tasks, appointments.
  • History: notes, logged calls, texts, emails, call recordings.
  • Files: contracts, photos, anything attached to a record.
  • Permissions and refusals: who agreed to texts and when, and who told you to stop.
  • Copies outside the CRM: spreadsheets, a phone's address book, a dialer, an email tool.

Then decide what should not come along. The FTC's second principle is to "keep only what you need for your business." A move is the cheapest moment you will ever have to leave behind ten-year-old leads with no phone number.

Step 2: Move the do-not-contact list first

If someone asked you to stop calling or texting, that request does not expire because you changed software. Bring the list of opted-out numbers and emails into the new system before any contact is imported, so the first import already knows whom not to reach. Our guide on keeping an opt-out list explains what the list has to hold, and which records to keep and for how long covers the consent side.

Check one thing by hand: pick five people you know opted out, find them in the new system, and confirm it refuses to text or call them.

Step 3: Export to plain files, and protect the originals

Almost every CRM can export a CSV file: one row per record, one column per field, values separated by commas. The format is simple, but it has rules that matter the moment a note contains a comma or a line break. The common description of the format, RFC 4180, says each line "should contain the same number of fields throughout the file", and that fields containing line breaks, double quotes or commas "should be enclosed in double-quotes". A file that breaks those rules will slide columns sideways: a note ends up in the phone column and the import looks fine until you read it.

Three habits prevent most damage:

  1. Save the export and never edit that file. Make a copy to work on. If something goes wrong you can start again from the original.
  2. Be careful opening it in a spreadsheet. Microsoft's own help page says that when Excel opens a CSV "it uses the current default data format settings to interpret how to import each column of data", which can change dates. The same page describes importing the column as text to preserve leading zeros, which matters for ZIP codes and parcel numbers.
  3. Export each kind of record separately and keep the old system's ID in a column. The ID is what lets you tie a note or a deal back to the right person later.

Step 4: Map the fields on paper before you import

Write two columns: the field in the old system and the field it becomes in the new one. Most trouble hides in four places:

  • Names. One "Full name" field on one side, "First" and "Last" on the other.
  • Phones. Several numbers in one cell, or numbers with extensions. Decide which is the mobile.
  • Stages. Your old stages rarely match the new ones one for one. Decide where each old stage lands; our guide to pipeline stages may help you simplify.
  • Dates. A call logged in March should still say March after the move, not the day of the import. Ask how the new system treats the original date of a note or call.

Anything with no home in the new system should go into a notes field or a custom field rather than be dropped.

Step 5: Trial import, then the real one

  1. Import 50 to 100 records you know well. Open ten of them and read every field against the old system.
  2. Import the same file a second time. A good import recognizes the records and adds nothing. If you get doubles, fix that before going further.
  3. Import everything, in this order: do-not-contact list, people, deals, then history and files.
  4. Compare counts: people out versus people in, deals per stage, open tasks, opted-out numbers. Write the numbers down.

The numbers will rarely match exactly, because duplicates get merged and junk rows get refused. What matters is that you can explain every difference.

Step 6: Run both for a short time, then close the old one properly

Keep read-only access to the old system for a few weeks. People will remember a note or a file that did not come over. When you are sure, deal with what is left behind. The FTC's fourth principle is to "properly dispose of what you no longer need": that includes the export files on your laptop, the copy in your downloads folder and the spreadsheet someone emailed. If a contractor helped with the move, the same guide says to "put your security expectations in writing in contracts with service providers".

What usually goes missing

  • Opt-outs stored as a tag or a note instead of on a list.
  • The date and wording of consent to text.
  • Call recordings and photos, which are files, not rows.
  • Notes written on a deal rather than on the person.
  • Who each lead belongs to on the team.
  • Tasks that were due after the move date.

Texts, calls and recordings need the most care; moving your CRM without losing a single conversation covers counts, original times and files step by step.

How this fits in NuVentrec today

NuVentrec's move checker and import checker read an export in your browser and show what would come across and what needs fixing, without uploading the file. Inside the CRM, a lead upload is checked first, imported in pieces that can each be undone, and an import run twice adds nothing the second time. In a done-for-you migration, opt-outs are brought in before people. That migration is a paid service; prices are on the pricing page.

Questions people ask

How long should a move take for a small team?

The import itself is quick. The time goes into the inventory, the field map and reading the trial import. Give those the most attention; a rushed map is what creates weeks of clean-up afterwards.

Should I clean my data before or after the move?

Remove what you clearly do not need before, because every row you leave behind is a row you do not have to check. Merge duplicates after the trial import, when you can see how the new system matches people.

Can I just copy and paste from a spreadsheet?

For a few dozen contacts, yes. Beyond that, export and import files: you keep an untouched original, you can repeat the import, and you can count what went in.

What if my old system will not export notes or call history?

Ask its support for a full data export in writing; many can produce one on request even when the screen has no button for it. If they cannot, decide which records matter most and copy those notes by hand before your access ends.

Do I have to keep the old exports?

Keep one protected copy for as long as your record-keeping rules ask, and delete the working copies. An export is a full list of people's contact details sitting in a file.

Sources

  1. Federal Trade Commission, "Protecting Personal Information: A Guide for Business" (take stock, scale down, lock it, pitch it, plan ahead)
  2. RFC 4180, "Common Format and MIME Type for Comma-Separated Values (CSV) Files" (October 2005), section 2
  3. Microsoft Support, "Import or export text (.txt or .csv) files" (how Excel interprets columns when it opens a CSV)

See what your own export would look like before you decide.

Check my exportBook a walkthrough
Call now