How to Switch Dealer Management Systems

A practical sequence for changing the system your whole store runs on, written by people who have watched it go badly.

A dealer management system is the operational and financial core of the store. It holds the general ledger, accounts payable and receivable, payroll, deal posting, vehicle and floorplan accounting, parts inventory, repair orders, technician time, and in most cases title and registration work. Nearly every other vendor you use touches it.

That is what makes a DMS change different from any other software decision a dealership makes. Changing a CRM affects the sales floor. Changing a website affects marketing. Changing the DMS affects accounting, service, parts, F&I and sales simultaneously, and it does so on a deadline that does not move, because the month end close still has to happen.

To be clear about our own position before you read further: LeadLocate is not a dealer management system and we do not sell one. We make a lead generation platform with a CRM, which is one of the many systems that sits alongside a DMS. This guide exists because our customers go through DMS changes and ask us how to sequence them, and because the integration inventory step below is one most stores skip until it hurts.

The single most expensive mistake is discovering your data terms during your exit. Do this first, while you are still a happy customer and have leverage.

Read your current agreement and find out, in writing: what data you can export, in what format, at what cost, and on what timeline after termination. Whether third party integrators can access your data and what the vendor charges them, because that cost is usually passed to you. How long the vendor retains your data after you leave and how you get a final extract. Whether historical records, meaning closed deals, posted accounting and completed repair orders, come out in a usable form or only as reports.

Then ask the same questions of every vendor you are evaluating, and get the answers before you sign, not after. A vendor that is vague about how you leave is telling you something important about year three. Our data ownership guide covers the specific clauses to look for.

The pattern worth internalizing: negotiate your exit at the same time you negotiate your entry. Your leverage is never higher than the moment before you sign.

Every store underestimates how many systems touch the DMS. Before you shortlist vendors, write the list down. Walk each department and ask what they log into and what pulls data automatically.

You will typically find: the CRM, the website and inventory syndication, third party lead providers, the desking tool, F&I menu and lender submission, credit and compliance tools, service scheduling, digital vehicle inspection, parts catalogs and ordering, payroll and HR, accounting exports to a group office, the phone system, chat, reputation management, equity mining, and manufacturer reporting.

For each one, record three things: does it read from the DMS, write to it, or both; who owns the integration and what it costs; and what happens to it on the new system. Some will have certified integrations. Some will need to be rebuilt. Some will not be supported at all, and finding that out in month one is very different from finding out during cutover week.

This is also the moment to notice which integrations you are paying for and no longer use. Most stores find two or three. Our integration inventory template is a starting structure you can fill in.

Demos show the system working correctly with clean data and an experienced operator. Your store will run it on a busy Saturday with a new hire and a customer waiting. Evaluate accordingly.

Ask to see the ugly paths, not the happy ones. A deal unwind. A negative equity trade with a payoff correction. A repair order that splits across warranty, customer pay and internal. A month end close, ideally watched at a live reference store rather than in a sandbox. Multi store consolidated reporting if you are a group.

Insist on reference calls with stores that resemble yours in size, franchise mix and state, and specifically ask for a store that switched within the last eighteen months so the pain is still fresh. Ask those references one question above all others: what surprised you? The answer to that is worth more than the entire feature comparison.

Bring your controller into evaluation early and give their objections real weight. The controller lives in the DMS more than anyone and will be the one absorbing the pain of a bad choice. A system the sales floor likes and the controller hates is a system that will cost you a controller.

A typical franchise store should plan nine to eighteen months from decision to stable operation. Independents and smaller stores can move faster, but the sequence does not change.

1. Discovery and data audit. Integration inventory, data ownership terms, chart of accounts review, and a clear list of what you are bringing versus archiving.
2. Vendor selection and contract. Including exit terms, integration costs in writing, and named implementation staff.
3. Data cleanup in the old system. Do this before migration, never after. Migrating bad data just moves the mess and doubles the work.
4. Configuration and chart of accounts mapping. The single most detail sensitive step, and the one most often rushed.
5. Test migration and reconciliation. Move a full data set into a test environment and reconcile balances against the old system line by line.
6. Training by role. Not one general session. The parts counter, the service advisor, the F&I manager and the accounting office need different training entirely.
7. Parallel run. Through at least one full month end close.
8. Cutover and stabilization. Plan sixty to ninety days of elevated support after go live.

Never schedule a cutover for the end of a month, the end of a quarter, or the week before a manufacturer reporting deadline. Mid month is the least bad time.

Parallel running means operating both systems for a defined period so you can prove the new one produces the same numbers as the old one. It is expensive, it is unpopular with staff, and it is the step that separates smooth conversions from painful ones.

The non negotiable version is one complete month end close in both systems, reconciled. If the trial balance, the schedules and the inventory valuation match, you have real evidence. If they do not, you have found the problem while you still have a working fallback, which is the entire point.

Be honest with your team about the workload. Parallel running genuinely means doing some work twice, and pretending otherwise damages trust at exactly the moment you need people cooperating. Pay overtime, bring in temporary help for data entry, and say plainly that it is four to six weeks and then it is over.

Do not let a vendor talk you out of it to hit their implementation timeline. Their incentive is a fast close. Yours is a correct one.

The license fee is the number everyone compares. It is rarely the number that decides whether the project hurt.

Budget for: overlapping subscriptions during parallel running, typically one to three months of paying twice. Data migration and any extraction fee from the outgoing vendor. Integration rebuild costs for every third party on your inventory list. Overtime through the transition. Temporary staff for data cleanup. Lost productivity, which is real even though it never appears on an invoice, and typically runs four to eight weeks at reduced output. Hardware or network upgrades if the new system needs them. And ongoing per transaction or per integration fees, which vary enormously between vendors and are easy to miss in a headline price.

Model three years, not one. Introductory pricing and year one implementation credits distort the comparison badly. Our total cost of ownership guide lays out a structure for this, and the hidden costs page covers what surfaces late.

Here is the part stores routinely get wrong, and it is where we do have a stake. During a DMS conversion, management attention goes almost entirely to accounting, service and parts, because that is where the risk sits. Meanwhile the sales floor gets less oversight than usual for a period of months.

Lead response times slip. Follow up cadences get abandoned because managers are in conversion meetings. Salespeople default to their personal phones because the systems are in flux, and once that habit returns it is hard to break. Stores frequently come out of a successful DMS conversion having quietly lost a quarter of sales performance, and they attribute it to the disruption rather than to the specific thing that caused it.

The mitigation is straightforward. Keep the sales floor's tools stable while the back end changes. Do not change CRM and DMS in the same window, however tempting the bundle discount looks. Assign someone whose only job during conversion is watching lead response time and follow up depth, and give them authority to escalate. Keep reporting on those two metrics visible weekly.

Because our platform runs independently of your DMS and does not require an integration or an inventory feed to operate, it is one of the few systems that can stay completely stable while you change the core. That is genuinely useful during a conversion, and it is the honest extent of our role in one.

Bring these written down and ask for written answers.

What is the total three year cost including implementation, integration fees, and any per transaction charges? What exactly can we export if we leave, in what format, and what does it cost? Who are three reference stores like ours that switched in the last eighteen months? Which of our current integrations are certified, which need rebuilding, and which are unsupported? Who specifically will run our implementation and how many other conversions are they running at the same time? What does support look like during month end close? What is your recommended parallel run length, and will you support us through it?

The last question is a good filter. A vendor that encourages a proper parallel run is optimizing for your outcome. A vendor that discourages it is optimizing for their timeline.

If you are also reviewing the sales side of your stack, the CRM migration checklist covers that separately, and it is deliberately a different project with a different timeline.

How long does a DMS conversion take?

Plan nine to eighteen months for a franchise store from decision to stable operation. Independents can move faster. The sequence matters more than the calendar: data audit, selection, cleanup, configuration, test migration, role based training, parallel run, cutover.

Is LeadLocate a DMS?

No. We do not sell a dealer management system and have no accounting, parts or repair order functionality. We make a lead generation platform with a CRM, which runs alongside whatever DMS you use and does not require an integration with it.

Should we change our CRM at the same time as our DMS?

No. Changing both at once removes your stable ground. Keep the sales floor's tools steady while the operational core changes, then revisit the CRM once the DMS is stable, usually sixty to ninety days after cutover.

How long should we run both systems in parallel?

At minimum through one complete month end close, reconciled line by line. Do not let an implementation timeline talk you out of this step. It is where you find problems while you still have a fallback.

What is the most commonly missed cost?

Integration rebuilds. Stores count the license fee and the migration, then discover that six third party systems need repointing and several are billed separately. Build the integration inventory before you shortlist vendors.

When is the worst time to cut over?

Month end, quarter end, or immediately before a manufacturer reporting deadline. Mid month is the least disruptive window.

Our platform runs independently of your DMS, with no integration or inventory feed required, so lead flow and follow up stay stable through a conversion. Month to month, no long term contract.