Blog

Switching

How to Prepare for a Dealership Software Cutover

Most cutovers that go sideways were lost weeks before go-live. Here's a step-by-step playbook to get parts, service and accounting on the same plan before your data moves.

Dealership manager walks two shop staff through a go-live checklist on a laptop, with a tractor and skid steer in the service shop behind them
On this page

    Key takeaways

    • The software is rarely the problem. Cutovers stall when parts, service and accounting each have a different idea of what moves, what closes and who checks it.
    • Pick the date around your season and your books. Go live in a slower month, right after a clean month-end close.
    • Clean before you move. Dead parts, duplicate customers and stale open work orders are easier to fix in the old system than in the new one.
    • Write down the cutoff rules. Every open work order, special order, rental contract and deposit needs an owner and a plan for cutover day.
    • Your first month-end close is the real finish line. Plan support through it, not just through day one.

    Your new dealer management system goes live on a Monday. By Wednesday, the parts counter can't find half its bin locations, the shop is re-keying open work orders by hand, and the controller is asking why the AR aging doesn't match the general ledger.

    None of that is a software problem. It's an alignment problem.

    Most dealership software implementation trouble starts weeks before go-live, when parts, service and accounting each walk into the project with a different idea of what's moving, what's closing and who's checking the numbers. The data migration is only as good as the decisions behind it.

    This playbook is for the operations leader who owns the switch. It walks through how to get every department on the same plan before the data transfer starts, and how to run cutover week so the dealership keeps selling parts, closing work orders and getting paid.

    1. Name one owner and a lead in every department

    A cutover needs one person who can make the call when parts and accounting disagree. That's usually the GM or operations leader, not the vendor and not IT.

    Under that owner, name a lead for each department: the parts manager, the service manager, the controller, and whoever runs sales and rental. Put all of them in the same weekly meeting from kickoff to go-live. Each lead decides for their department and signs off on its data.

    Then give them the time. Your parts manager can't validate 20,000 part numbers while running the counter. Decide now who covers the counter, the service desk and the books while the leads do project work.

    2. Pick a go-live date that works for the shop and the books

    Go-live timing decides how much pain your customers feel. Two rules cover most dealers:

    • Stay out of your busy season. Spring for OPE, planting and harvest for ag, peak jobsite months for construction. Nobody learns a new system well with a line at the counter.
    • Go live right after a clean month-end close. Accounting starts the new system with a closed period, and every department starts its first full month on the same day.

    Also check what else is on the calendar. A physical inventory, a new location opening or an accounting system change all compete for the same people. If you're mid-rollout on another system, waiting a few months is often the smarter call. Two migrations in one year is one too many.

    Once the date is set, put it on every calendar and plan backward from it.

    3. Map every system and spreadsheet that touches the DMS

    A software deployment touches more than the DMS. Before any data moves, list everything your team opens in a day:

    • OEM portals, price files and warranty systems
    • Your accounting system, if it sits outside the DMS
    • Card payments and ACH
    • Telematics, your website and any online parts store
    • The spreadsheets, whiteboards and paper logs nobody mentions until they're gone

    Ask each department lead one question: What do you open every day besides the DMS? The PM schedule your service writer keeps in a spreadsheet counts.

    For each item, decide whether it connects to the new system, gets replaced by it, or stays separate. Then name who tests it before go-live.

    4. Decide what data moves, then clean it first

    This is the core of implementation planning. Agree on what moves before anyone pulls an export: customers, equipment and serial numbers, the parts master, service history, open AR and AP, and how many years of closed transactions you actually need.

    Then clean it in the old system, where your team already knows how to fix things. A simple rule helps: if nobody would miss it, don't move it.

    • Parts: retire dead and obsolete part numbers, merge duplicates, fix bin locations, clear negative on-hand and schedule a physical count close to cutover.
    • Service: close or clean out stale open work orders, merge duplicate customers and equipment records, and check serial numbers and hour meters on active machines.
    • Accounting: reconcile AR and AP, write off what should be written off and review the chart of accounts. If your books live inside the old DMS, the chart of accounts may need to be rebuilt, so plan that time now.
    • Sales and rental: confirm unit inventory, rental fleet status and customer deposits.

    5. Write the cutoff rules for everything that's open

    The hardest part of any data migration is the work still in flight on cutover day. Each department needs a written rule for its open items:

    • Open work orders: finish them in the old system, or move them with labor and parts to date?
    • Special orders and back orders already placed with the OEM
    • Rental contracts out on the yard and on jobsites
    • Customer deposits and prepaid orders
    • Open purchase orders and parts receipts
    • Warranty claims submitted but not yet paid

    Put it on one page: the item, the rule, the owner and the deadline. Share it with every department so the counter and the shop give customers the same answer.

    6. Validate the migrated data with the people who use it

    Migration validation reports aren't for IT. They're for the people who'll live in the data every day.

    • Parts manager: check on-hand quantities, costs and bin locations on a sample of your top movers.
    • Service manager: pull 10 regular customers and check their equipment, serial numbers and repair history.
    • Controller: tie AR aging, AP and inventory value back to the general ledger.

    Get a written sign-off from each department lead. And ask your vendor, before go-live, which records didn't migrate cleanly and what happens to them.

    7. Train by department, then test the whole workflow

    Train each department on its own work, using your migrated data: a counter sale, a work order with parts and labor, a warranty claim, a rental checkout, a month-end close.

    Then test across departments. Follow one part from the counter to a work order, to an invoice, to a payment, to the books. Handoffs are where cutovers break, and no single department will catch them alone.

    Pick a go-to person in each department, someone who learns the system first and answers the floor's questions during week one.

    8. Run cutover week on a written schedule

    Cutover week should feel boring. Freeze changes in the old system, run the final count and the final data transfer, go live, and hold a short huddle at the end of each day. Here's how it breaks down by department.

    Cutover week checklist by department
    DepartmentWeek before go-liveCutover dayFirst 30 days
    PartsPhysical count on fast movers, receive open POs, freeze new part numbersConfirm on-hand and bins on top movers, test a counter sale and an OEM orderWatch negative on-hand, check price file updates, recount anything that looks off
    ServiceClose every work order you can, list the ones moving over with labor and parts to dateOpen the moved work orders, test clock-in and parts on a jobCheck warranty claims in flight, rebuild PM schedules, confirm tech time posts correctly
    AccountingClose the month, reconcile AR, AP and bank, record opening balancesTie opening balances to the GL, test one payment from sale to postingRun the first month-end close with vendor support, compare to the old system
    Sales and rentalConfirm unit inventory, rental fleet status and depositsCheck rental contracts out and units on the lotReview open quotes and follow-ups, confirm rental billing cycles

    9. Plan support through your first month-end close

    Day one isn't the finish line. Your first month-end close in the new system is.

    For the first two weeks, hold a 15-minute daily huddle with the department leads and keep one shared issue log. Then plan for the controller, and your vendor's support team, to work the first close together. After that close, look at which spreadsheets are still running on the side and decide which ones the new system should replace.

    Get every department on one plan

    A dealership software cutover goes well when the decisions are made before the data moves. One owner, one date, one list of systems, one set of cutoff rules, and a sign-off from every department. Do that, and go-live week is mostly answering questions, not putting out fires.

    The new system should make that easier, too. When parts, service, sales, rental and accounting run on one platform instead of a stack of connected tools, there are fewer handoffs to map, fewer systems to test and fewer places for data to fall through. That's the core difference between a cloud DMS and a legacy DMS.

    How Flyntlok handles the switch

    Flyntlok was built by a former equipment dealer, so implementation runs on the dealer's calendar, not the vendor's. And implementation and migration are $0, for every customer.

    • Your team picks the go-live date. The Migration Planner flags a go-live that lands in your busy months and suggests a cleaner one.
    • We do the data migration. Every record is validated in staging. Records below a confidence threshold go to a person before they reach production, and you hear about anything that can't migrate cleanly before go-live.
    • Parts, service, sales, rental and accounting move together. One system, one database. Your controller can keep QuickBooks Online, Sage Intacct or Xero, and OEM connections are set up and tested before go-live.
    • Training fits your schedule. Five department training sessions are scheduled around your operations.
    • Support doesn't stop at day one. The 8/8 Support Guarantee: response in 8 minutes, solved in 8 hours.

    A single-location dealer with fewer than 20 users gets a fixed 5-week plan that includes support after go-live. Multi-location groups get a custom plan, typically 2 to 6 months, timed around the busy season.

    Plan your switch with the Migration Planner or request a demo.

    Filed under

    Switching

    Share

    Nicholas Fazzino

    About the author

    Nicholas Fazzino

    Head of Marketing

    Connect on LinkedIn

    Switching

    See Flyntlok in your dealership

    Get a demo built around the way your team works today.

    Request a demo

    What dealers ask.

    Quick answers to the questions this article raises.

    How long does a dealership software implementation take?

    It depends on your locations, users and data. With Flyntlok, a single-location dealer with fewer than 20 users gets a fixed 5-week plan that includes support after go-live. Multi-location groups get a custom plan, typically 2 to 6 months, timed around the busy season.

    When is the best time to switch dealer management systems?

    Outside your busy season, and right after a clean month-end close. That way accounting starts the new system with a closed period and every department starts its first full month on the same day.

    What data should we move to the new DMS?

    Customers, equipment and serial numbers, the parts master, service history, open AR and AP, and the closed history your team will actually use. Clean it in the old system first. If nobody would miss it, don't move it.

    What happens to open work orders during a DMS cutover?

    Write a cutoff rule before go-live. Either finish them in the old system or move them with labor and parts to date. Do the same for special orders, rental contracts out, deposits, open POs and warranty claims in flight.

    Who should be on the implementation team?

    One owner with the authority to make calls, usually the GM or operations leader, plus a lead from parts, service, accounting, and sales and rental. Each lead signs off on their department's data before go-live.

    Can we keep our accounting system when we switch to Flyntlok?

    Yes. Flyntlok syncs with QuickBooks Online, Sage Intacct and Xero, so your controller can keep the system they already use.

    Inside Flyntlok

    Switch on your schedule, not ours.

    Flyntlok's team runs the data migration, validates every record in staging and goes live on a date your team picks.

    • Your go-live date, checked against your busy season
    • Every record validated before it reaches production
    • Five department training sessions around your operations
    Keep learning

    Switching

    See all resources
    No items found.
    No items found.