DMS Switching Checklist for Service Departments

The shop is the department with the most moving parts and the least tolerance for downtime. Cars are on lifts whether the software is ready or not.

Accounting can close a period and take a breath. The sales floor can write a deal on paper for a weekend. The shop cannot pause. Cars are on lifts, customers are waiting in the lounge, technicians are being paid by the hour, and parts are on order from three suppliers.

That is why fixed ops carries the most operational risk in a system change even though the office carries the most financial risk. A repair order that will not print, a labor operation that is not configured, a warranty submission that gets rejected, or a parts catalog that did not load are all immediate, visible failures in front of customers.

It is also the department with the most external connections. Manufacturer warranty systems, parts catalogs and ordering, tire and service contract administrators, scheduling tools, inspection tools, payment devices, and whatever your BDC uses to text customers. Every one of those has to be inventoried, repointed and tested, and most of them were configured once years ago by somebody who has left.

Stated plainly at the outset: LeadLocate does not sell shop management software or a dealer management system. There is no repair order management, no technician time clock or dispatch, no shop loading, no parts inventory, no warranty claim handling, no digital vehicle inspection and no capacity based scheduling. This page is buyer education. What we do sell is the customer communication and follow up layer that sits alongside your shop system, and that part is covered at the end rather than dressed up as the whole page.

Your leverage is highest before signature. Get the shop's requirements into the evaluation rather than into the complaint list afterward.

In the demo, refuse the clean repair order. Ask to see an ugly one: a job that splits across warranty, customer pay and internal, with a parts backorder partway through, a technician reassignment, and a second concern added after the customer approved the first estimate. That single scenario tells you more about a system than an hour of feature slides.

Ask how labor time is captured and whether technicians in real stores actually use it, because a time clock that gets bypassed produces worse data than no time clock at all. Ask how shop loading behaves when three advisors book against the same capacity at the same time. Ask what happens to a repair order when a customer declines work, because that record is a follow up list and it should not be a dead end.

Then the vendor questions. What does each integration cost, who maintains it, and what happens to your history if you leave. Ask that last one before you sign, because your leverage never returns. Questions to ask during a DMS demo covers the wider set, and data ownership covers the contract language.

Most of the shop's go live pain traces back to configuration that was not finished, and most of that configuration is unglamorous data entry that somebody has to own weeks in advance.

The list is long and each item is a real failure if missed. Labor operation codes and descriptions. Labor rates by type, including warranty, customer pay, internal and any fleet or account specific rates. Menu and package pricing. Shop supplies and environmental fee calculation. Sublet handling. Tax treatment on parts and labor for your state, which differs more than people expect. Discount and coupon structures. Advisor and technician records with the right skill and pay setup.

Print is its own project. Every document the shop hands a customer or hangs on a car has to be mapped and tested on the actual printers: the repair order, the estimate, the multi point inspection sheet, the invoice, the warranty copy and the technician hard copy if you use one. Print a full set for a real split job on real paper before the weekend, not after.

Test the pricing with known jobs. Take ten repair orders you closed last month, rebuild them in the new system, and compare the totals line by line. Differences are configuration errors you can still fix cheaply. Finding them through a customer complaint costs far more than the afternoon this takes.

Parts and warranty are where conversions produce delayed, expensive surprises rather than immediate visible ones.

On parts, confirm how the catalog and price file load and how often they update afterward. Verify on hand quantities against a physical count for a sample rather than trusting the load report, because a load can succeed and still be wrong. Check that special order and backorder status carried across with the customer and the repair order still attached, since an orphaned special order is a customer who calls in three weeks and nobody can find their part. Confirm supplier ordering connections, returns and core tracking, and obsolescence reporting.

On warranty, this is the money at risk. Confirm claim submission works to your manufacturer's current requirements before go live, and submit a small test batch early rather than converting and hoping. Check that open and pending claims carried across with their status, and know exactly where partially submitted claims sit on cutover weekend. Confirm service contract and extended warranty administrator connections separately, because those are usually different vendors with different formats.

Then build the full list of every third party that touches the shop and record the format, the owner, the lead time to change it and who tests it. The parts department checklist goes deeper on the parts side, and hidden costs of switching covers the integration fees that surprise stores.

This is the item most likely to be discovered late, because scheduling often lives partly outside the shop system and nobody owns the whole picture.

Find out early whether existing appointments convert, and if they do not, decide how they get rebuilt. A store that loses three weeks of booked appointments over a weekend has a very bad Monday, and rebuilding them by hand takes longer than anyone estimates.

Confirm how capacity, technician availability and skill matching are configured, and whether your online scheduling tool writes into the new system or the old one. Check the reminder mechanism specifically, because appointment reminders often run from a separate tool pointed at a database that is about to change.

A practical safeguard: export your booked appointments to a spreadsheet before the weekend regardless of what the vendor says about conversion. It costs an hour and it is the difference between a manual rebuild and a guess.

Worth knowing that customer communication does not have to depend on the conversion. Appointments, reminders and a calendar with settings live in the CRM layer, and messaging keeps running independently of the shop system, which means you can still confirm and remind customers while scheduling is being rebuilt.

Service history is what makes an advisor credible, and losing it changes the conversation at the desk in a way customers notice.

List what the department actually needs: customer records with correct contact detail, vehicle records with correct VIN and mileage, service history with what was done and when, declined recommendations, open recommendations, warranty history, service contract coverage, and any notes about a customer that a new advisor would need in order not to make a mistake.

Then get specific about what will not convert. Advisor notes, photos attached to inspections and communication history are the usual casualties. If those matter to you, export them while you still have access rather than discovering the gap in week three.

Declined work deserves separate attention because it is the department's cheapest revenue source and it is routinely lost in conversions. Every declined recommendation is a follow up opportunity, most declines are timing rather than refusal, and if that data does not carry across then a year of opportunity disappears silently. Pull it to a file before the move even if the vendor says it converts.

Test the load yourself with records you chose: a customer with a long history, a vehicle with warranty work, and a repair order with declined lines. Migrating historical records and cleaning data before migration cover the sequencing.

The shop needs its own written plan for the weekend, separate from the office plan, because the work in progress does not stop for a conversion.

Decide what happens to open repair orders crossing the boundary and communicate the rule before the weekend rather than during. Whether you close everything you can on Friday, how a job that is half complete is handled, where parts already issued sit, and how a customer waiting on a backordered part is tracked across the change.

Write the manual process down. What an advisor does if the system is unavailable, where the paper goes, who rekeys it and when, and who is authorized to give a customer a price. Assign the rekeying to a named person with time set aside, because otherwise it happens badly at the end of a long day.

Consider scheduling lightly for the first two or three days. Stores that book a full shop on go live Monday almost always regret it. Deliberately under booking for seventy two hours costs you less than the chaos does.

Then the first thirty days. Expect the productivity dip, two to four weeks is normal. Run a five minute daily meeting with one question: what could you not do today. Keep a visible issue list with owners. Watch effective labor rate and hours per repair order closely, because configuration errors show up there before anyone reports them as a problem. The cutover checklist and the training plan cover the cross department sequencing.

Here is the part where we have something to offer, stated with the limits attached.

During a conversion the shop's communication with customers is usually the first thing to degrade. Advisors are learning a system, the phones are busier than normal because customers are calling about jobs, and status updates stop going out. Customers do not know a conversion is happening, so what they experience is a dealership that stopped answering.

The communication layer does not have to live inside the system being replaced. SMS and MMS with real threading, so a photo of a worn part sits in the same conversation as the estimate. RCS with automatic SMS fallback for branded messages on supported handsets. A shared inbox rather than personal phones. Click to call with a VoIP softphone, voicemail drop, and call recording with transcription so a manager can read a difficult call in half a minute. AutoMail adds IVR, call routing and forwarding, which matters when the morning rush gets worse than usual. Appointments and reminders, automations and follow up processes for declined work and retention, plus an email validator and a phone validator for the old contact data every service database carries.

None of that requires DMS access or an inventory feed, which is the point during a conversion. What it is not is a shop system, and we will not pretend otherwise. See automotive service CRM for where the line sits, and service texting software for the messaging side on its own.

If the shop only gets a few items on the agenda, make them these.

Someone from fixed ops sits in the evaluation and builds one ugly split repair order in the demo. Labor codes, rates, menus, fees, tax treatment and every print template are configured and printed on real paper before go live, and ten known repair orders are rebuilt and compared line by line. Parts catalog, on hand counts, special orders and supplier connections are verified against a physical sample rather than a load report. Warranty submission is tested with a small live batch early, and the status of open claims on cutover weekend is known. Booked appointments are exported to a spreadsheet regardless of what the vendor says. Declined work is exported before access ends. The weekend has a written manual process, a rule for open repair orders, and a named rekeying owner. The first three days are deliberately under booked.

And keep customer communication on ground that is not moving, so the department that talks to customers every day can keep doing it.

Our side is month to month with no long term contract, US only, from $199 on CRM Only. Detail on the pricing page. If you want the communication layer steady before your conversion date, contact us or call 844-376-2274 and we will tell you plainly what we do and do not cover.

Does LeadLocate replace a shop management system?

No. There is no repair order management, technician time clock or dispatch, shop loading, parts inventory, warranty claim handling, digital vehicle inspection or capacity based scheduling, and we do not sell a dealer management system. We provide the customer communication and follow up layer alongside it.

What should fixed ops insist on seeing in a vendor demo?

One ugly repair order built end to end: a job splitting across warranty, customer pay and internal, with a parts backorder, a technician reassignment and a concern added after approval. That scenario reveals more than an hour of feature slides.

What service data most often fails to convert?

Advisor notes, inspection photos and communication history are the usual casualties, and declined recommendations are the most valuable thing lost. Export declined work and any history you rely on before your access to the old system ends.

What happens to appointments already on the books?

Find out early whether they convert, and export them to a spreadsheet regardless. Rebuilding three weeks of appointments by hand takes far longer than anyone estimates, and online scheduling tools often write into a database that is about to change.

How should we handle open repair orders on cutover weekend?

Decide the rule and communicate it before the weekend. Close what you can on Friday, define how a half complete job is handled, know where issued parts sit, and track anyone waiting on a backordered part manually across the boundary.

Can we keep texting service customers during the change?

Yes. The messaging layer runs independently of the shop system and needs no DMS access or inventory feed, so status updates, appointment reminders and follow up on declined work keep going while the shop system is being converted.

See texting, calling, reminders and follow up running independently of the shop system, with no DMS access or inventory feed required. Month to month.