NuVentrec

Guides / Moving conversations

Guide · Moving your data

How to move your CRM without losing a single conversation

Names and phone numbers are the easy part of a move. The texts, call logs, recordings, notes and photos are where history gets lost, usually without anyone noticing until a customer says "I already told you that". This guide is about moving the conversations themselves and proving that all of them arrived.

By the NuVentrec team · Published October 12, 2026 · Sources last checked October 12, 2026

The short answer

  • Count before you move. For each kind of record (texts, calls, recordings, notes, files) write down how many the old system holds. You cannot prove nothing was lost without a starting number.
  • Keep the old system's ID on every record. It lets you run the move twice without duplicates and trace any message back to where it came from.
  • Keep the original time, with its time zone. A conversation dated the day of the import is a conversation you can no longer follow.
  • Download files and recordings, do not just copy their links. Links into the old system stop working when the account closes.
  • Move the do-not-contact list first and make sure the move itself cannot send anything.
  • Finish with a gap report: old count, new count, and a named reason for every difference.

What a conversation is made of

When people say "our history", they mean several different kinds of record that most systems store and export separately:

  • Text messages, both directions, with the time, the two phone numbers and whether each one was delivered.
  • Calls: direction, start time, length, outcome (answered, missed, voicemail), and who on your team made or took it.
  • Recordings and voicemails, which are audio files stored apart from the call log.
  • Pictures and documents sent in either direction.
  • Notes typed by your team, with the author and date.
  • Emails, if the old system sent or logged them.
  • Events: stage changes, appointments, opt-out requests.

A contact export, the file most systems offer on a button, contains none of this. Ask the old provider how to get each item above, and expect a different answer for each. Our broader guide, how to switch CRMs without losing your history, covers contacts, deals and tasks. This one stays with the conversations.

Step 1: Count what you have

Before exporting anything, record the totals: messages, calls, recordings, notes and files, per account if you have more than one. Add the earliest and latest date of each. These numbers are the left-hand column of the gap report you will write at the end. If the old system cannot tell you its totals, count the rows in the export files as soon as you have them and treat that as the baseline.

Step 2: Export in a form that keeps every field

Conversation data is awkward for spreadsheets. A text message can contain commas, quotation marks and line breaks, and a spreadsheet file that handles those badly will split one message across several rows. The common standard for CSV files, RFC 4180, says that "fields containing line breaks (CRLF), double quotes, and commas should be enclosed in double-quotes" and that "each line should contain the same number of fields throughout the file." A quick check on any export is to confirm that every row has the same number of columns. If some do not, messages have been broken apart.

Where the provider offers it, a structured export (one record per line, with named fields) is safer than CSV for messages. Whatever the format, keep the untouched originals in a folder nobody edits, and work on copies.

Step 3: Keep the ID and the original time

Every message and call in the old system has an identifier. Store it on the matching record in the new system. This does three jobs. You can run the import a second time and it will skip what is already there. You can bring across late additions, the messages that arrived between the export and the switch, without creating duplicates. And when a number does not match at the end, you can list exactly which records are missing.

Time needs the same care. Exports sometimes give a local time with no zone, and the standard for internet timestamps, RFC 3339, is blunt about why that is a problem: an unqualified local time "will fail in approximately 23/24 of the globe". Find out which zone the export uses, convert once, and store the result with its offset. Then check a conversation you remember: the messages should appear in the order they happened, on the right day, at a believable hour.

Step 4: Match each conversation to the right person

  1. By the old system's contact ID first. Import people before messages, keeping their IDs, and attach each message through that ID.
  2. By phone number or email second, for records with no contact ID. Normalize numbers to one format before comparing.
  3. Leave the rest in a visible "unmatched" list. Do not attach a message to a guess, and do not drop it. A person can sort out a short list by hand.

Watch for people who exist twice. If two old records share a phone number, decide which one receives the history before you import, or you will split one conversation across two profiles.

Pictures, documents and call recordings are usually stored as web addresses that point back into the old provider's storage. Those addresses often need a login or expire, and they stop working altogether once the account is closed. Download every file while you still have access, store it where the new system can serve it, and tie it to its message or call by ID. Keep a list of any file that could not be fetched, with the reason. Check your storage space before you start: audio adds up quickly.

Some calls were never recorded. That is a fact to carry over as well. "No recording exists" is a different answer from "recording missing", and your gap report should tell them apart.

Step 6: Make sure the move cannot contact anyone

Two risks are specific to conversation data. The first is that importing a message triggers something: an automatic reply, a new-lead alert, a follow-up sequence. Imported history should be stored silently and marked as imported. The second is losing a stop request. Under 47 CFR 64.1200(d)(6) a do-not-call request to your business must be honored for five years, and a request is not cancelled because you changed software. Move the opt-out list first, and scan the imported texts for replies like "stop" that the old system may not have flagged. See how to keep one opt-out list.

Step 7: Rehearse, then prove it with a gap report

Run the whole import on a copy before you run it for real, and time it. Then run it for real and build a table like this for each kind of record:

  • how many the old system had;
  • how many are now in the new system, matched by ID;
  • how many are missing, each with a reason: no contact to attach to, an unsupported type, a file that could not be downloaded.

The goal is not a table of zeros at any price. It is a table where every number that is not zero has an explanation you have read and accepted. Keep the old account open, read-only, until that table is finished. Our move checker reads an export in your browser and shows what it contains before you commit to anything.

How this fits in NuVentrec today

NuVentrec's import keeps the outside ID on contacts, messages, calls, notes and tasks, so a second run adds nothing twice. It always starts with a dry run that shows counts and writes nothing, applies opt-outs before anything else, and cannot send a text or an email. Imported texts keep their original time and are tagged in the thread, pictures are shown from our own copy, and call recordings play from the call they belong to. The what's live page lists current features, and you can request access to try it on your own export.

Questions people ask

Do we need the old conversations at all?

For active leads, yes: the last thing they told you is what your next call depends on. For the rest, the opt-out and consent records are the part you must keep. Old chatter with closed leads can be archived as files if importing it is not worth the effort.

How long should the old system stay open?

Until the gap report is done and someone has spot-checked a handful of real conversations in the new system. Ending the subscription before that removes your only way to fetch something you missed.

What about messages that arrive during the move?

Keep exporting. Because every record carries its old ID, you can import a small "what changed since" file every few minutes until the day you switch, and nothing is duplicated.

Will imported texts look like we just sent them?

They should not. Each one should show its original time and direction, and it helps if imported messages are tagged so nobody mistakes a three-year-old text for a new one.

Sources

  1. Y. Shafranovich, RFC 4180, "Common Format and MIME Type for Comma-Separated Values (CSV) Files", October 2005, section 2
  2. G. Klyne and C. Newman, RFC 3339, "Date and Time on the Internet: Timestamps", July 2002, sections 4.4 and 5.6
  3. 47 CFR 64.1200, "Delivery restrictions", paragraph (d)(6) (do-not-call requests honored for 5 years), Legal Information Institute

Check your export in the browser first: see what it holds before you move anything.

Try the interactive demoBook a walkthrough
Call now