Migrating Historical Records to a New DMS

Not everything should come across. Deciding what moves, what gets archived and what you must keep is the real work in a conversion.

The mistake that makes conversions painful is treating this as a single question: are we bringing the history or not. There are three answers, and every category of data belongs to exactly one of them.

Live migration. Records that go into the new system as working data your team searches, edits and reports on. This should be the smallest set you can live with, because everything here has to be mapped, cleaned and validated, and every extra table adds cost and risk.

Archive. Records extracted into files you keep but do not load. Searchable if you build an index for them, retrievable if somebody asks, and out of the way the rest of the time. This is where most of your history belongs.

Legacy access. The old system kept alive in read only mode for a defined period, usually paid for month by month. Expensive, but the only way to answer questions that need the original system's own logic and formatting.

Assign every data category to one of the three before you write a single mapping rule. Doing this on a whiteboard with your controller, your fixed ops manager and your sales manager in the room takes two hours and saves weeks. It is also the conversation where you discover that two of them have completely different assumptions about what is coming across.

Reasonable defaults, which your store may adjust for good reasons.

Active customer records. Names, contact information, addresses, household links. Anyone who has transacted or been in contact within your chosen window, commonly seven to ten years.

Consent and opt out records. All of them, regardless of age, with their original dates. There is no window on this one. A stop request from 2018 is still a stop request.

Vehicles owned. What each customer bought or brought in, with VIN, so a service visit and a possible trade are the same conversation rather than two disconnected ones.

Recent deal summaries. Enough to answer what somebody bought, when, at what number, and who sold it. Full deal detail with every line item is usually archive material rather than live data.

Open items. Anything unfinished on cutover day. Open deals, scheduled appointments, active repair orders, units in stock, outstanding we owes. These are non negotiable and they are the source of most cutover pain, which is why the timing of the conversion matters so much.

Recent service history where your fixed ops team will actually reference it, usually two to three years, longer if your customers keep vehicles a long time.

Archive is not a euphemism for deleted. It is an extract you keep, stored properly, that nobody has to search through daily.

Old deal detail beyond your live window. Full service history beyond what fixed ops references. Superseded customer records that were merged during cleanup. Old marketing campaign detail. Every record belonging to a customer who last transacted before your cutoff and shows no sign of life since.

Extract archives in an open format that will still open in ten years. CSV and PDF outlast any vendor's proprietary export. A file you can only read with software you no longer license is not an archive, it is a hostage.

Then index it. An archive nobody can search is functionally the same as an archive that does not exist. At minimum, keep a spreadsheet listing what each file contains, the date range it covers and where it came from. Store it somewhere with access control and backups, not on a former IT person's external drive, and encrypt it, because these files contain the personal information of everyone who has ever done business with your store.

Decide the retention period for the archive itself and write it down. Keeping everything forever with no policy is its own liability, and the security side of holding it is covered on our Safeguards Rule page.

This surprises dealers every time, and the accountants in the room are usually already nodding.

Reconciled financial history generally does not migrate into a new general ledger. You do not want prior period entries landing in a fresh set of books, your CPA does not want it, and reconciling a migrated ledger against statements you already closed is a project with no upside. The standard approach is to close the old system's books, start the new system with opening balances as of a clean date, and keep the old system or its extracts available for anything historical.

Which means the calendar drives the conversion. Month end is the minimum, and many stores go live at the start of a fiscal year or a quarter precisely so the cut is clean. Converting on the 14th of a month is how a controller ends up rebuilding a month by hand.

Talk to your CPA before you set the date, not after the vendor has scheduled it. And get the statements, trial balances and reconciliations you will need for your next audit or review exported and stored before anyone touches the old system, because the moment you stop paying for it your access assumptions may change.

To be direct about our own position: LeadLocate is not a dealer management system. There is no general ledger, accounts payable or receivable, payroll, bank reconciliation or deal posting to accounting. This section is here because the question comes up constantly during conversions, not because we sell the answer.

Legacy access is the line item nobody budgets for and everybody ends up paying.

The common range is three to twelve months of read only access after cutover. What drives the length is your reporting cycle. You need the old system available through at least one full annual close, one tax filing season, and whatever manufacturer or lender reporting runs on an annual rhythm. Cut it off in month two to save money and you will find out in month five what you needed.

Negotiate this before you give notice, when your leverage is highest. Get the read only rate in writing, get the notice period for ending it, and get confirmation of what happens to your data when access stops, including whether they delete it and whether you can require them to.

Then set a reminder for sixty days before legacy access ends and do a deliberate sweep. Pull anything you have needed even once during the period, plus the reports you have not needed yet but will at year end. That sweep is your last chance and it is worth a full day of somebody's time.

The related questions about who owns what are on dealership data ownership, and it is worth reading before you sign anything with the incoming vendor too.

Retention obligations do not pause for a system change, and a conversion is exactly when records go missing.

Deal jackets and the documents inside them carry retention requirements that vary by state and by document type, and several federal rules add their own. Credit application records, adverse action notices, identity verification records under the Red Flags Rule, OFAC screening records and cash reporting documentation all have expected retention periods. Your compliance counsel should give you the specific list for your state and your franchise agreements.

The practical instruction is simple. Before anything moves, map where each of those record types currently lives, because in most stores they are scattered across the main system, a document imaging tool, a separate application platform and a filing cabinet. Then confirm which of those four you are actually changing, because a conversion often touches only one and stores panic about all of them.

Consent and messaging records deserve one more mention because they are the ones most often lost. Load your suppression and opt out list into the new system first, before any customer records, so there is never a window where contactable records exist with no suppression applied. All it takes is one campaign going out during that window. TCPA compliance for dealership texting covers what those records need to show.

A migration report that says success is a claim, not evidence. Verify it yourself.

Start with counts. Customers, vehicles, open deals, appointments, units in stock. Compare each against what the old system reported on the same date. Investigate every discrepancy rather than accepting a close approximation, because the missing rows are rarely random and you will want to know the reason before you go live rather than in March.

Then spot check by hand. Pick twenty five records you know well: your oldest customer, your most active, a household with several vehicles, a deal with a lot of attachments, a customer with a long text history and one with an opt out on file. Walk each one end to end in the new system and confirm nothing was dropped or truncated.

Check the boundaries. The earliest record in the new system tells you whether history was cut off where you intended. Look for date fields that landed as 1900 or 1970, which almost always means the field was empty and got a default. Look for text cut off mid sentence, which means a field was longer than the destination allowed. Cleanup done before the load prevents most of this, and data cleanup before migration covers that stage in order.

Finally, have three people who use the system daily go find records they remember. They will catch things a reconciliation script never will.

The part of a conversion that costs the most money is rarely the data. It is the four to six weeks when your team is distracted, unsure where to look, and slower on every lead.

This is where a decoupled sales and communication layer earns its keep. LeadLocate runs independently of whichever system your store operates on. No DMS integration and no inventory feed is required, so your lead flow, your text threads, your follow up cadences and your desking do not go dark while the back end is being replaced. Salespeople keep working in the same place they worked last week, which means the conversion does not become a reason for follow up to collapse.

Concretely, that means the lead inbox and distribution rules keep routing, SMS and MMS threads stay intact with RCS and SMS fallback still working, the dialer with call recording and transcription keeps running, follow up processes and drips keep firing, and the desking engine with its fifty state tax matrix keeps producing numbers your desk can stand behind. The customer profile holds contact and vehicle history with personally identifiable information stored encrypted, so a shopper who calls during conversion week does not get treated like a stranger.

CRM Only is $199 a month, month to month with no long term contract, and lead programs start at $799. We cannot guarantee a smooth conversion, because that depends on your data and your vendors. What we can do is make sure the sales side is not one of the moving parts. Current figures are on the pricing page, or contact us and tell us what you are converting from.

How far back should we migrate customer records?

Seven to ten years of active customer records is a common live window, with anything older extracted to an archive. Consent and opt out records are the exception and should all come across with their original dates regardless of age.

Does accounting history move to the new system?

Usually not. Reconciled financial history stays in the old system or an archive, and the new system starts with opening balances as of a clean date. Talk to your CPA before setting the conversion date, because month end or fiscal year end makes the cut far cleaner.

How long should we keep the old system available?

Three to twelve months of read only access is common, driven by your reporting cycle. You want it through at least one annual close, one tax season and any annual manufacturer or lender reporting. Negotiate the read only rate before you give notice.

What is the difference between archiving and migrating?

Migrated data goes into the new system as live working records your team searches and edits. Archived data is extracted into open format files you keep and index but do not load. Most history belongs in the archive, which keeps the live system fast and the project small.

How do we verify the migration actually worked?

Compare record counts against the old system on the same date and investigate every discrepancy. Then hand check twenty five records you know well, including your oldest, your most active, one with many attachments and one with an opt out on file.

Does LeadLocate replace a dealer management system?

No. There is no general ledger, accounts payable or receivable, payroll, deal posting, parts, repair orders or title work. The platform provides the lead, communication, follow up and desking layer, and it runs independently so your sales side stays up during a conversion.

The leads, the messaging and the desking run independently of your back end system. See it working before your cutover date. Month to month, no long term contract.