Dominion DMS plans to shut down by the end of 2026, while support for its Vue dealership management system is scheduled to end Dec. 31, according to an Automotive News report published July 24, 2026. Dealers should treat those as related but distinct statements: The report places both developments in the same year-end window, but it does not establish whether the corporate shutdown and the Vue support cutoff are the same event for contractual, data-access or service purposes.
That distinction is not academic. A store could lose routine product support on one date while retaining limited access to records, archives or transition assistance under different terms. Each affected dealer should obtain its customer notice, review its contract and ask Dominion to confirm the dates and obligations that apply to that specific rooftop in writing.
A review of Dominion DMS’s main public website did not identify a clearly labeled, dated Vue transition guide as of July 26. Unless more detailed public instructions are released, the notice sent directly to customers—and written responses from the dealer’s Dominion representative—should be treated as the controlling operational guidance.
Why the Dominion DMS deadline requires action now
A DMS change touches nearly every department that opens the doors in the morning and closes the books at month-end. Accounting balances, vehicle inventory, repair orders, parts counts, customer records, payroll-related processes and deal posting all have to remain dependable while employees learn a different system. Connected vendors may also need new arrangements, revised contracts or replacement products.
The calendar is the immediate risk.
If many Vue dealerships pursue the same group of replacement providers, desirable conversion dates and training resources may tighten well before Dec. 31. Holiday schedules, year-end accounting work and employee vacations make the final weeks of the year a poor time to discover that a vendor cannot accommodate the store’s preferred launch date. I’d argue that waiting for perfect clarity from every party is now riskier than beginning vendor reviews with reasonable assumptions and documenting what still needs confirmation.
Put one executive in charge—and name department owners
The dealer principal or general manager should appoint one executive sponsor with authority to settle priorities, approve spending and hold vendors to dates. That person should not personally perform every task. The controller should own accounting validation and record-retention requirements; the fixed operations director should cover repair orders, appointments, parts and warranty workflows; and the variable operations lead should verify inventory, deal status, titles, receivables and customer follow-up.
A dealership technology manager or outside adviser can coordinate connected products and vendor dependencies, but department managers still need to sign off on whether the new setup works in practice.
- Executive sponsor: Set the deadline, approve the provider and resolve cross-department conflicts.
- Controller: Reconcile balances, define retention needs and approve financial records before launch.
- Variable operations leader: Validate inventory, open deals, title status, receivables and vehicle cost information.
- Fixed operations director: Review open repair orders, appointments, parts quantities, special orders and warranty work.
- Human resources or training lead: Schedule role-based instruction, track attendance and plan coverage for employees pulled away from daily work.
- Vendor coordinator: Maintain the contact list, contract status, dependencies and written commitments from every affected provider.
Get the high-risk answers in writing
Verbal assurances are not enough for a deadline that could affect access to financial and customer records. Dealers should ask Dominion and the selected replacement provider for dated written answers, then store those answers with the conversion plan and relevant contracts.
- What exactly ends on Dec. 31: routine support, emergency assistance, system access, record access or all of the above?
- How long will historical records remain available, what will that access include, and will any continuing fees apply?
- Which records can be transferred, which may require separate archiving and who is responsible for confirming completeness?
- What are the final dates for requesting records, correcting problems and receiving transition help from Dominion?
- What implementation date can the replacement provider commit to, and what happens if that date slips?
- Which connected dealership products will continue working, which require changes and which may need to be replaced?
- Who owns the resolution of missing records, duplicate entries, incorrect balances or interrupted department workflows?
- What support will be available during the first month on the replacement system, including nights, weekends and month-end?
Contracts deserve the same attention. A dealer may still owe fees to a connected vendor even if that vendor no longer works with the replacement DMS. Managers should identify notice periods, early-termination provisions, renewal dates and installation charges before signing a new agreement.
Used-car managers need their own validation plan
Used-vehicle records can become especially messy when a conversion catches units between acquisition, inspection, reconditioning, merchandising and sale. The used-car manager should create a dated inventory snapshot showing each unit’s stock number, acquisition source, title status, mileage, cost, reconditioning spend, aging and current sales status. Vehicles at auction, in transit or at an outside repair facility should be included.
Do not assume a correct unit count means the inventory transferred correctly.
Managers should compare a sample of high-value, aged and recently acquired vehicles record by record. They should also review sold-but-not-delivered units, open trade payoffs, title exceptions and deals awaiting funding. Even a small number of incorrect costs or missing title notes can distort appraisal decisions, gross reporting and aging reviews long after the new system launches.
Build the schedule backward from the confirmed cutoff
The store should select a replacement provider and reserve an implementation window as soon as practical, rather than treating Dec. 31 as the decision date. Next, department leaders should document essential daily, weekly and month-end work; identify connected vendors; and decide which historical records must remain readily searchable. Managers should then complete an early test review, correct discrepancies and repeat the review closer to launch.
Training should be role-based and scheduled around actual store coverage. A desk manager, warranty administrator and office clerk do not need identical instruction, and pulling all experienced employees into training at once can create a second operational problem. Each department should also name a backup employee who can perform critical work if the primary user is unavailable.
Dealers can estimate the exposure by looking at normal daily volume: deals posted, repair orders closed, parts transactions completed and accounting entries processed. Management should decide how much unfinished work the store could absorb after one disrupted day, how quickly employees could clear that backlog and whether overtime or temporary coverage would be needed. The exercise will not predict every issue, but it converts a vague conversion risk into a staffing and cash-flow discussion.
The operating takeaway
Dealers should leave July with an executive owner, a written question list, an inventory of affected vendors and active discussions with replacement providers. The selected provider should then be held to a documented schedule covering record review, employee preparation, launch support and post-conversion validation.
The Dec. 31 Vue support deadline may still receive clarification, but the dealership’s plan should not depend on an extension. The safest objective is to complete the change early enough to reconcile financials, verify inventory and correct workflow problems while Dominion support is still scheduled to be available.