Switching From Wayne Reaves: Migration Guide

The parts that go wrong are never the parts vendors talk about. Here is the order to do this in.

Stores describe this project as switching systems, singular, and that framing is where the trouble starts. Most independent dealerships are actually running three distinct things, and each moves on its own timeline with its own risks.

The operational and accounting system. Inventory records and cost, deal posting, the general ledger, accounts payable and receivable, buy here pay here note servicing and collections, title and registration work, state forms and reporting. Moving this is the hard part, and the part that can genuinely hurt the store.

The customer layer. Leads, communication history, follow up, appointments, desking worksheets, the record of what was said to whom.

The web presence. Your website, your inventory display, your forms and where they post.

The value of pulling them apart is that you can move them separately. A store that changes all three in the same week has multiplied its risk for no reason, and it has done so during the period when its people are least able to absorb a mistake. Decide which one is actually causing your pain, move that first, and leave the others alone until the dust settles.

To be explicit about where we sit: we do not sell dealer management software. LeadLocate has no general ledger, no accounts payable or receivable, no deal posting to accounting, no title or registration processing, no note servicing, no parts and no repair orders. This guide is written to help you run the project well, and we are only involved in the second category.

Your leverage is at its maximum before you announce anything and drops to near zero the moment you do. Spend it on data.

Ask your current vendor, in writing, exactly what you can export and in what format. Not whether you can export, which always gets a yes, but what fields, what file types, and whether it includes history rather than only current records. Ask what it costs, whether there is a lead time, and how long they retain your data after termination.

Then test it. Request a sample export now, while you are still a customer in good standing, and open it. A file you have never opened is not a backup, it is a promise. Stores discover the gaps at the worst possible time: notes that came out as one unreadable column, payment history that stopped at a date, attachments that were never included.

Read your agreement for the termination clause, the notice period and any auto renewal. Missing a thirty day window on an annual renewal is a common and expensive mistake, and it turns a planned March migration into a rushed one next January.

Do all of this before the first demo with a replacement vendor. It sometimes changes which vendor you pick.

Work down this list and store everything in one organized place with dates in the filenames.

1. Customer and contact records. Names, addresses, phones, emails, and any consent or opt out flags. Opt out status is the one people forget, and losing it is a compliance problem rather than an inconvenience.
2. Deal history. Sold units with dates, vehicles, gross where you keep it, salesperson, and finance detail. You will want this for year over year comparison and you will not get it later.
3. Inventory. Current stock with cost, dates in stock, reconditioning and floor plan detail.
4. Note and payment records if you run buy here pay here. This is the highest risk data in the building. Verify it twice, reconcile totals against your accounting, and do not move it on a Friday.
5. Accounting history. Trial balance, general ledger detail, payables and receivables aging. Talk to your accountant about how far back to carry and what stays as a read only archive.
6. Documents. Scanned deal jackets, titles, contracts, signed forms. These are often stored differently from the database and are the most commonly missed item in a migration.
7. Reports you use. Run and save the reports you rely on monthly, for the last two or three years. Report formats never survive a migration intact.

Keep a read only copy of the old system for as long as your vendor allows and your record retention policy requires. Ask your counsel about retention periods for your state rather than guessing.

The calendar decides how bad this is. Choose it deliberately.

Move at the quietest point in your year, never during tax refund season, never at month end and never at year end close. Cut the accounting side at a clean period boundary so your close does not straddle two systems, and talk to your accountant about it before you pick a date rather than after.

Sequence in this order for most independent stores. First, get the customer and communication layer stable and independent, which is the part that protects revenue. Second, move the operational system at the period boundary with a parallel period. Third, deal with the website, which can wait and which is easiest to fix if it goes wrong.

Plan a genuine parallel period rather than a same day switch. Two to four weeks of running both, with new activity entered in the new system and the old one kept readable, catches the discrepancies while somebody can still fix them. Reconcile at least once during that period: inventory count, receivables total, and a sample of customer records checked field by field.

And name an owner. Not a committee, one person with authority and time, with a written checklist and a daily standup during cutover week. Migrations that fail almost always fail because everyone assumed someone else was watching a particular piece.

Here is the pattern we see most often, and it is worth planning around because it costs real deals.

The store's attention goes entirely to accounting and inventory, which is understandable, since those have deadlines and auditors. Meanwhile leads keep arriving. For three or four weeks, response times slide, follow up stops, and nobody notices because everyone is looking at the trial balance. The store loses a month of sales momentum and blames the new system for a slow quarter.

The insulation is structural: keep your leads, communication and follow up in a system that is not part of the migration. If texting, calling, email, appointments and follow up processes live somewhere independent, a back office change cannot touch them. Salespeople work the same way on Monday as they did on Friday.

That is what our platform does here, and the reason it works is that no DMS integration and no inventory feed is required to operate. There is no data mapping project and no waiting for two vendors to schedule each other. You can stand it up before the migration starts, which also gives you a clean baseline: response time, touch counts and appointments measured before the disruption, so you can tell afterward what the migration actually cost you.

Get the customer records in early, then run the phone validator and email validator across the imported list so your first campaign after the move is not sent into a wall of dead addresses.

These items are individually small and collectively the reason cutover week goes badly.

Phone numbers. Find out who owns every number your store advertises, including tracking numbers on your website and in print. If a vendor owns them, start the porting conversation early; porting takes longer than anyone expects and cannot be rushed at the end.

Website forms. Every contact form, credit application and trade in tool posts somewhere. List them, then repoint them, then submit a test through each one and confirm it arrives.

Lead providers. Every third party sending you leads has a destination on file. Give them the new one in advance and confirm receipt with a test, because a provider still posting to a dead endpoint loses leads silently.

Inventory syndication. Whatever feeds your listings has to keep running. Verify vehicles are still appearing on every site you advertise on, the day after cutover and again a week later.

Payment processing and lender connections. Confirm before, not during.

User accounts and permissions. Build them before cutover day, not on it. Nothing wastes a morning faster than fourteen people who cannot log in.

Printers and forms. Deal jackets, buyers guides, state forms. Print one of each and check alignment before you need one for a customer.

Expect a dip. Two to four weeks of slower work while people relearn tasks they used to do without thinking. Pretending otherwise is how a store sets itself up to panic in week two.

Train by role rather than by module. Your office manager, your desk manager and your salespeople need three different sessions, and a generic overview serves none of them. Train close to go live, because anything taught six weeks early is gone. Then run a second short session two weeks after cutover, once people have real questions rather than theoretical ones, which is when training actually sticks.

Identify one person per department who learns it properly and becomes the internal answer. That reduces vendor support load dramatically and gets people unstuck in minutes instead of days.

Write down your own process, not just the vendor's. How does your store enter a deal, what gets checked, who approves what. The system is generic; your process is not, and undocumented process is what walks out the door with an experienced employee.

If you are also standing up the sales side, our CRM onboarding checklist covers that half, and running two systems during a migration covers the overlap discipline.

So there is no confusion after two thousand words of migration advice.

We do not: replace your operational system, post deals to accounting, run a general ledger, service notes, process titles or registration, handle parts or repair orders, or file your state reporting. Those live in whatever dealer management system you choose next, and you should evaluate candidates on those merits with your accountant in the room.

We do: hold the customer and communication layer independently of that system. Lead inbox with distribution rules, SMS and MMS with RCS and SMS fallback, click to call with a VoIP softphone, call recording with transcription, voicemail drop, email inbox with campaigns and bulk email, an email validator and a phone validator, automations, follow up processes and drips, appointments and reminders, DealTracker desking covering loan and lease with a fifty state tax matrix, deal jackets, customer facing deal pages with e signature, lead pages, a free live chat widget, document reading with VIN scanning, and three layers of reporting. Alongside it, SecureWebX handles secure credit applications, apply links, document collection and a compliance module with versioned consent.

We also supply exclusive local leads in a territory you define, if the reason you are changing systems is that the store needs more opportunities rather than better bookkeeping. Nothing is filtered or scored; every submitted lead in your zone is delivered, and problems go through post delivery replacement review. If you are still comparing options rather than committed to a move, the alternative comparison lays out where each side fits, and contact us if you would rather just ask.

Is LeadLocate a replacement for Wayne Reaves?

Not for the operational side. We do not sell dealer management software, so there is no general ledger, deal posting, note servicing or title work. We hold the lead, CRM, communication and desking layer that sits alongside whichever system you choose.

What should we export before giving notice?

Customer records with consent and opt out flags, deal history, inventory with cost, note and payment records, accounting history, scanned documents, and saved copies of the reports you use monthly. Test a sample export before you announce anything.

When is the best time to cut over?

Your quietest month, at a clean accounting period boundary, never during tax refund season and never at month or year end close. Pick the date with your accountant before committing to a vendor timeline.

How long should we run both systems?

Two to four weeks in most independent stores, with new activity in the new system and the old one kept readable. Reconcile inventory counts, receivables and a sample of customer records at least once during that period.

How do we keep sales from stalling during the migration?

Keep leads, communication and follow up in a system that is not part of the move. Because no DMS integration or inventory feed is required to run our platform, it can be live before the migration starts and untouched by it.

Who should own the project?

One named person with authority and time, working from a written checklist, with a daily standup during cutover week. Migrations fail when everybody assumes somebody else was watching a particular piece.

Stand up the lead and CRM layer before the migration starts, so response time and follow up never depend on which system your office is using. Month to month, no long term contract.