Migrate in stages: map every field from the old system to the new one, decide which history you really need, move a sample and have the people who use it check records they know, then run a final top-up migration at cutover. History gets lost when fields are dropped silently, when IDs are renumbered, or when dates and ownership are overwritten by the import itself.
Map the fields before anything moves
Start with a spreadsheet. Down the left, list every field in the old system for each record type: customer, vehicle, deal, lead, service visit, note. Beside each, write where it will live in the new system. Three kinds of row need a decision: fields with no home in the new system, coded values such as lead status where the two lists of codes do not match, and free-text fields where staff have been storing something structured, like a second phone number in the notes box.
Every row gets one of three answers: moves as it is, moves after conversion, or is left behind on purpose. Nothing should disappear because nobody looked.
Decide which history matters
Not everything is worth carrying. For a dealership, the history that earns its place is what someone looks up while a customer is standing there.
- Service history by vehicle, tied to the VIN and not just the owner's name.
- Past deals: what was bought, when, by whom, and who sold it.
- Lead source and the record of calls, emails and texts with each customer.
- Contact preferences, including anyone who has asked not to be contacted.
- Open work: live leads, deals in progress, unfinished repair orders, vehicles on order.
- Which salesperson or advisor each customer belongs to.
How long records must be kept is a question for your accountant or lawyer, not for the software. Anything you have to retain but do not need day to day can stay in the archive instead of being migrated.
Migrate a sample and let staff check records they know
Move a slice of real data into a test copy of the new system and hand it to the people who use it. A service advisor pulls up a long-standing customer and checks that every visit is there in the right order. A salesperson opens their own pipeline and confirms that each lead shows the right stage and the last conversation. They will spot in minutes what a row count never shows, such as a note attached to the wrong vehicle. Fix the mapping, run the sample again, and repeat until the checks come back clean.
Keep IDs, dates and ownership intact
Store each record's old ID in a reference field in the new system, so that anything can be traced back to its source. Carry the original created and modified dates across as data. If the new system stamps every record with the day of the import, every customer looks brand new, and any follow-up rule based on age will fire at once. For the same reason, switch off automatic emails and texts while the import runs. Keep the assigned salesperson on every customer and lead, or Monday morning begins with an argument about whose they are.
The delta at cutover, and the archive
The showroom keeps trading while the main migration runs. At cutover, run a delta: a second pass that brings across only what was added or changed since the main one. Pick a quiet moment, stop entry into the old system, run the delta, then reconcile counts and spot-check the newest records.
Finally, keep the full export from the old system, labelled with its date, stored read-only in two places.
If a replacement is still only an idea, our free software bill calculator shows what the current system costs over three years, and our guide to owning your software explains why running two systems side by side lowers the risk. When we rebuild software for a dealership we move the data across ourselves, and systems your manufacturer requires stay in place. Our page for car dealerships has the detail.