CRM Data Export Checklist for Dealerships

Everything you should be able to get out of your CRM, in the order you should ask for it, and how to check that what arrived is actually complete.

The single most expensive mistake in a CRM change is discovering what you cannot export after you have already given notice. Your leverage with a vendor is at its absolute peak in the weeks before you sign a renewal and drops to nothing the moment you tell them you are leaving. So the export test belongs at the start of your evaluation, not at the end.

Do this while you are a happy paying customer: open a support ticket asking for a full export of your account data in a documented format, with a list of exactly what is and is not included. Not a sample. Not a summary of the export tool. The real file, or a real subset of it, plus the documentation.

What you learn from that one ticket is worth more than any demo. You will find out how fast they respond, whether communication history is included or excluded, whether attachments come as files or as broken links, whether there is a fee, and whether the answer changes when it becomes a retention conversation. Every one of those facts is a negotiating position later.

If a vendor will not or cannot produce an export for a customer in good standing, treat that as the answer to a different question, which is whether you want to be with them in three years. This applies to us as well. Ask us the same thing and hold us to the same standard.

Work down this list. The items at the top are the ones you cannot rebuild if they are missing.

1. Customer and contact records. Names, phone numbers, emails, addresses, and every custom field your store added over the years. Custom fields are frequently dropped from standard exports.
2. Opt out and consent status. Who has unsubscribed from email, who has asked you to stop texting, and when. This is a legal record, not a preference, and losing it exposes you.
3. Notes and activity history. The record of what your people actually said and did. This is what makes a customer record worth having rather than a phone list.
4. Communication history. Text threads, email threads, call logs, recordings and any transcripts. This is the item vendors most often exclude or charge for.
5. Appointments and tasks. Past and future. Future appointments especially, because losing those is immediate and visible.
6. Deal and desking records. Structures, numbers, trade information, and the documents attached to them.
7. Attachments and documents. Driver licenses, insurance cards, signed forms, trade photos.
8. Lead source and campaign data. Where every lead came from. Without it, your historical cost per sale is unreconstructable.
9. Users, roles and assignment history. Who owned which record and when, including people who no longer work there.
10. Reports you will want to compare against. Pull the actual reports as files, not just the raw data, because reconstructing a vendor's report logic later is a project nobody has time for.

Almost every CRM will hand you a contact list. Far fewer will hand you the conversations attached to those contacts, and the difference matters more than dealers expect until they live through it.

Consider what a salesperson does when a lead from eight months ago calls back. If the record shows a name and a phone number, they are starting over. If it shows the six texts, two calls and the note about the customer waiting on a bonus in March, they are picking up a relationship. That is a measurable difference in close rate, and it disappears the day you migrate a contact list without its history.

Ask three specific questions. Does the export include the body of text messages and emails, or only a count of them? Are call recordings included as audio files, or only as log entries pointing at storage you lose access to? Are transcripts included, and in what format?

Then ask the receiving vendor the mirror question: can they actually import all of that, or will history land as one giant note field per customer? Both halves have to work. An export you cannot import is a backup, not a migration. Our CRM migration checklist covers the sequencing on the receiving side.

Get the format in writing before the file arrives. CSV is the common denominator and is usually fine for flat data. Anything with nested structure, meaning a customer with many messages, does better as JSON or as a set of related tables with keys you can join on.

Then the practical traps. Phone numbers exported without formatting will arrive as numbers with leading zeros stripped, and dates will arrive in whichever format the vendor's database happened to use. Encoding matters more than it should: an export that is not UTF-8 will turn every apostrophe and accented name into noise, and you will not notice until a customer named O'Brien is in your system as O?Brien.

Ask for a data dictionary alongside the file. A column called status_2 with values 1 through 7 is worthless without the key. Get that key while someone at the old vendor still answers your email.

Finally, check file size and row counts against what the system reports in its own interface. If your CRM says you have 41,000 contacts and the export has 38,200 rows, something was filtered. Find out what before you go further, because the missing 2,800 are rarely random.

An export you have not checked is a rumor. Verification takes an afternoon and it is the highest value afternoon in the whole project.

Start with counts. Contacts, notes, messages, appointments, deals. Compare each against the number the live system displays. Then spot check by hand: pick twenty customers you know well, including your oldest record, your most active record, one with a lot of attachments and one with a long text thread, and confirm each one arrived complete.

Check the edges. The oldest record in the file tells you whether history was truncated at some date. The newest tells you how current the snapshot is. Sort by field length to find records that were cut off mid sentence, which happens when a note field is longer than the export column allows.

Look for duplicates and for records that lost their owner. Both are common, and both are far easier to fix in a file than after they are loaded into a live system where your team is already working. Cleaning at this stage is the right time; see automotive CRM data cleanup for what is worth fixing and what is not.

Store the verified export somewhere safe and keep it. Even after a successful migration, that file is your only copy of anything the new system could not accept.

Dealers assume their customer data is theirs. Usually it is, but the contract is what decides, and most people signed it years ago without reading the section that matters.

Find your agreement and look for four things. First, an explicit statement that customer data belongs to the dealership. Second, the export or data return obligation on termination, including format and timeline. Third, the retention period, meaning how long they keep your data after you leave and whether you can require deletion. Fourth, fees, because some agreements permit a charge for extraction that nobody mentions until you ask to leave.

Then check the notice period. Thirty, sixty and ninety day notice windows are all common, and the window usually starts when written notice is received, not when you told your rep on a phone call. Put notice in writing and keep proof.

If you are negotiating a new agreement right now, this is the cheapest moment to fix all of it. Ask for the data return language before you sign. A vendor confident in their product rarely objects. There is more on this in dealership data ownership, which covers the same questions on the system side.

Some of what lives in your CRM is not just useful, it is subject to retention rules, and changing vendors does not pause them.

Consent and opt out records need to survive the move intact, with dates. If a customer revoked consent to be texted in 2023 and that record is lost in migration, your new system will happily text them, and the fact that the data was lost in a vendor change is not a defense anyone will accept.

Anything touching credit applications, identity verification or adverse action carries its own retention expectations, and those records may live partly in your CRM and partly in a separate application system. Map where each piece lives before you move any of it. Our Safeguards Rule page covers the security side of holding that information, and it applies to an export file sitting on somebody's laptop just as much as to a live system.

Which raises the practical point people forget. The export itself is a large file of customer personal information. Encrypt it, keep it off personal devices and consumer file sharing accounts, limit who has a copy, and delete the working copies when the project is done. A migration is one of the few moments when your entire customer database exists as a single downloadable file, and that is exactly the moment to be careful with it.

On our side, the import path is contact import for customer records, and the customer profile is where records live once they are in, with personally identifiable information stored encrypted and access controlled per user rather than open to everyone with a login. Blacklist import exists specifically so your do not contact list arrives before your first campaign goes out rather than after.

Two hygiene tools are worth running on any imported list before you send anything. The phone validator checks numbers, and the email validator checks addresses. Imported dealership databases are usually several years of accumulated typos and disconnections, and finding that out through a validator is much cheaper than finding it out through a bulk send that damages your sending reputation.

Be realistic about what any CRM can accept. Structured data such as contacts, vehicles, sources and appointments maps cleanly. Free form history from another vendor's schema rarely maps field for field into anything, and the honest answer from any vendor is that some of it lands as attached history rather than as native threaded conversations. Ask us to show you a sample load with your actual file before you commit to anything.

Because the platform is month to month with no long term contract, there is no scenario where you have to migrate everything to find out whether the workflow suits your store. Load a slice, run a team on it, then decide.

Stores that do this well spread it over about six weeks and treat the export as its own phase rather than as a task inside cutover week.

Weeks one and two are discovery: request the test export, read the contract, list every third party currently posting into your CRM, and confirm what the new vendor can accept. Weeks three and four are the real export, verification and cleanup, done on a copy, with nothing yet loaded into production. Week five is a trial load of a subset into the new system, worked by two or three people who will tell you honestly what is missing. Week six is the full load, with both systems running in parallel.

Do not cut the parallel period to save a month of subscription cost. Running two systems briefly is the cheapest insurance in the project, and running two CRMs during migration explains how to do it without confusing your team about where to work a lead.

The one thing that genuinely cannot be rushed is adoption. Expect a productivity dip of two to four weeks after cutover regardless of how clean the data is, and plan management attention accordingly. We cannot guarantee a specific outcome from any migration, but the stores that come through it well are almost always the ones that did the export test first.

When should I request a test export?

At the start of your evaluation, while you are still a customer in good standing. Your leverage disappears the moment you give notice, and what you learn from that one support ticket shapes the entire project.

What do CRM vendors most often leave out of an export?

Communication history. Contact lists are almost always available, but text and email bodies, call recordings and transcripts are frequently excluded, charged for, or delivered as links to storage you lose access to. Ask about each specifically.

Do I need to export opt out records separately?

Check, because they are often stored apart from the contact record. Opt out and consent status with dates is a legal record. Losing it in a migration means your new system will contact people who revoked consent, and the migration is not a defense.

How do I verify an export is complete?

Compare row counts against what the live system reports, spot check twenty records you know well including your oldest and most active, check the earliest and latest dates for truncation, and look for records cut off mid sentence or missing an owner.

Can LeadLocate import history from another CRM?

Contacts, vehicles, sources and appointments map cleanly through contact import, and blacklist import brings your do not contact list across first. Free form history from another vendor's schema rarely maps field for field, so ask us to run a sample load with your real file.

Is the export file itself a security concern?

Yes. It is your entire customer database as one downloadable file. Encrypt it, keep it off personal devices and consumer file sharing accounts, limit who holds a copy, and delete working copies when the project closes.

We will run a sample load with your actual data, show you exactly what maps and what does not, and give you a straight answer before you give anyone notice. Month to month, no long term contract.