Switching From Dealertrack DMS: A Migration Guide

The sequence, the timing and the questions that decide whether a conversion goes quietly or costs you a quarter of gross.

Almost every conversion that goes badly went badly at this step, months before anyone touched software. Pull the agreement out and find four things.

The term and the auto renewal date. The notice window, which is frequently ninety days and occasionally longer, and the exact form notice has to take. Whether notice must be delivered by a named officer or by certified mail rather than by an email to your rep. What you still owe on exit, including any hardware, any bundled service, and anything that was discounted on the condition that you stayed a specified length of time.

Then work backwards from your intended go live date and mark the notice deadline on a calendar that somebody other than you can see. Stores miss this constantly, discover they have auto renewed for another year, and end up paying two vendors for months. If your notice window has already closed for this cycle, that is not a disaster, it just means you have twelve months to run a careful evaluation instead of a rushed one. Our contract termination and exit plan covers the paperwork order.

Ask this before you sign anything with the next vendor, and ask it of your current one while your leverage is still intact. The question is not whether you own your data. Everybody says yes to that. The question is what you can actually get out, in what format, at what cost, and how quickly.

Be specific. Accounting detail and how many years of it. Customer and vehicle records. Deal files. Full service history including labor operations and parts detail, not just a summary. Open items on the day of cutover. Ask whether extracts arrive as usable structured files or as printed reports, whether there is a fee per extract, and how long the vendor will keep your data accessible after termination.

Write down what you will genuinely need on day one, what you need for the tax and audit trail, and what can live in a read only archive nobody logs into. Trying to move everything is how conversions slip. The data ownership guide lays out the questions in the order that gets straight answers.

The order matters more than the calendar. This is the sequence that tends to survive contact with a real store.

1. Contract and notice. Deadlines identified, notice drafted, exit costs quantified. Nothing else starts until this is settled.
2. Scope and inventory of integrations. Every system that posts into or pulls from the core, written down. Website, lead providers, chat, phone, payroll, inventory, service scheduling, payment processing, OEM feeds. There will be more than you think.
3. Data extraction test. Pull a real extract early, not at the end. Open it. Confirm it contains what the vendor said it contains.
4. Chart of accounts mapping. Controller led, and the single most time consuming item on the list.
5. Configuration and department setup. Parts, service, accounting and the business office each configured by the people who will live in them.
6. Training. Before cutover, not during. Covered further down.
7. Parallel run. Both systems live for a defined period.
8. Cutover and stabilization. Then a written punch list with owners and dates.

Compress any of the first four and you will pay for it in the last two.

Pick the date for accounting reasons, not for convenience. The strong preference is the first business day of a month, immediately after a clean close, because a conversion that straddles a close means reconciling two systems for a period neither one owns completely.

Avoid year end entirely. Avoid the weeks around your fiscal close, physical inventory, and any manufacturer reporting deadline that carries money with it. Avoid your two busiest selling weeks of the year, whenever those fall in your market. If your store does heavy tax season business, do not convert in February.

Give the parallel run a real definition rather than a vague intention. Which transactions are entered in both systems, by whom, for how long, and what the reconciliation check is at the end of each day. A parallel run without a daily reconciliation is just double data entry with no payoff. Our page on running a parallel conversion covers what to double enter and what to leave alone, because doing all of it is not realistic in a working store.

Each department has a different exposure, and the traps are predictable.

Assign a named owner per row before you begin. A department without an owner discovers its own gaps three days after cutover, which is the most expensive time to discover anything.

Here is the argument we actually care about, and it is the reason this guide exists on our site.

During a core conversion, the store still has to answer the phone, work leads, set appointments and desk deals. Every hour a manager spends on chart of accounts mapping is an hour not spent on the floor. If your CRM and your lead flow are wired directly into the system being replaced, they wobble at exactly the moment you cannot afford it.

LeadLocate is deliberately independent. It does not require a DMS integration or an inventory feed to operate, so your lead delivery, follow up cadences, texting, calling and desking keep running whatever is happening in the back office. Leads land in a territory you define around your store, exclusively. The desking engine covers loan and lease with a fifty state tax matrix, semimonthly frequency and trade credit caps, so a manager can still pencil a deal on the day of cutover without waiting for anybody. If you also happen to be replacing your CRM, our CRM migration checklist is a separate and much smaller project than this one, and should never be run in the same month.

Vendors quote training in hours, which encourages stores to buy the smallest number that looks defensible. That is a false economy for a simple reason: everyone in the building relearns their daily work in the same week, and the cost of the resulting slowdown dwarfs whatever you saved on the quote.

Train by role rather than by department, and train on your data rather than on a demo dataset. A parts counter person needs a different session than a parts manager. Identify two or three people per department who learn fast and train them deeper, because they will answer ninety percent of the questions in week one and they will be more available than the vendor.

Expect a productivity dip of two to four weeks. Plan around it instead of pretending it will not happen: schedule light, staff up rather than down for the first fortnight, and tell your management team that the numbers for that month will be ugly and that is not a performance problem. A conversion where nobody warned the department heads produces a lot of avoidable conflict.

Add these to whatever number you are comparing, because the subscription difference is usually the smallest figure in the whole exercise.

Overlap, where you pay both vendors during the parallel run. Data extraction fees, which some agreements price per pull. Integration rework for every third party that posts into the core, each of which may have its own connection fee. Custom reports rebuilt from scratch, since your existing ones do not travel. Forms and printer setup, including alignment on preprinted stock. Hardware, if the new system has different requirements. Overtime through the cutover weeks. And the productivity dip, which is real money even though nobody invoices you for it.

Then the item stores forget entirely: historical reporting continuity. Your comparison numbers for next year live in the old system. Pull the reports you will want to compare against while you still have access, and store them somewhere outside both vendors. The hidden costs page works through the full list, and the total cost of ownership guide puts them in a format you can take to an owner.

If you are early in this, the following month of work will save you a quarter later.

Find your notice deadline and put it on a shared calendar. Request a full data extract now, while you are still a customer in good standing, and actually open the files. Build the integration inventory. Ask your controller how long a chart of accounts mapping realistically takes given everything else on their plate, and believe the answer. Sit two demos, not eight, and take the vendor questions from our DMS demo question list into both. Ask each vendor for three reference stores of your size and franchise mix, and call them without the vendor on the line.

And separate the decisions. The core system, the CRM and your lead sources are three different purchases on three different timelines, and stores that bundle them into one project usually finish none of them well. If your sales side needs help this quarter, that can be handled independently and reversed just as easily. Contact us at 844-376-2274 if it would help to talk it through.

How long does a DMS conversion take?

Plan on months rather than weeks once contract notice, data extraction, chart of accounts mapping, configuration, training and a parallel run are all counted. The software install is never the long pole. Your controller availability usually is.

When is the worst time to cut over?

Year end, the weeks around your fiscal close or physical inventory, any manufacturer reporting deadline that carries money, and your two busiest selling weeks. The first business day of a month, right after a clean close, is the usual target.

What data should we insist on extracting?

Accounting detail, customer and vehicle records, deal files, full service history with labor operations and parts detail rather than a summary, and open items as of cutover. Confirm the format is structured files you can actually load, not printed reports.

Should we change our CRM at the same time?

No. Run them as separate projects in separate months. A core conversion already consumes your management attention, and stacking a CRM change on top is how stores end up doing both badly.

Does LeadLocate depend on our DMS?

No. The platform runs independently and requires no DMS integration or inventory feed, so lead delivery, texting, calling, follow up and desking keep working while the back office is mid conversion.

Can you help with the conversion itself?

Not directly, because we do not sell a dealer management system and would be no use to your controller. What we can do is keep the sales and communication layer stable and independent so the front of the store keeps producing during the change.

Your lead flow, follow up and desking should not wobble because accounting is mid migration. Ours run independently of any core system. Month to month, no long term contract.