DMS Go-Live Checklist for Equipment Dealers, With AI Checks

Dealership leads reviewing a DMS go-live checklist

A dealer management system is ready to go live when five things are true: your migrated data reconciles, your real workflows run end to end, your people are trained, your cutover has been rehearsed, and someone with authority has signed a go/no-go decision against written criteria. This checklist covers each gate in order, adds the checks that matter if your system includes AI features, and finishes with a post-go-live support plan for the first 30 days.

It is written for dealership owners and department managers in sales, service, parts, rental and finance who are about to switch from a legacy DMS or ERP.

Moderndms

moderndms.com.au

Bring dealership workflows together

MDMS is a purpose-built system for equipment dealerships, with modules for sales, service, parts, rental and finance.

Book a demo

TL;DR

Treat go-live as a decision against written, measurable criteria, not a calendar date.
Reconcile migrated data in layers: record counts, field accuracy, business logic, then integrations such as your accounting package.
Run real scenarios in each department, from quote to invoice, work order to warranty claim, hire contract to return.
Rehearse the cutover once, with named owners, timings and a rollback point.
If you use AI features, set permissions, review rules and data boundaries before launch, then plan a daily issue review for the first two weeks.

The readiness gates at a glance
Gate 1: Data you can trust
Gate 2: Real workflows with real data
Gate 3: People, training and day-one support
Gate 4: Infrastructure, access and compliance
Gate 5: AI readiness for a DMS or ERP
Gate 6: Cutover plan and rehearsal
The go/no-go meeting
Post-go-live support plan: the first 30 days
Perspective
Start with the module that matters most
FAQ
Sources

The readiness gates at a glance

A go-live checklist works best as a set of gates. Each gate has an owner and evidence, and the project does not move on until the evidence exists. Industry readiness checklists such as Project Perfect’s go-live readiness checklist group the criteria the same way: signed-off user acceptance testing, closed defects, tested infrastructure and backups, trained users with day-one support, measurable acceptance criteria with an authorised go/no-go decision, an approved deployment schedule, and a plan to close down the old system.

For an equipment dealership, we translate that into the table below.

Gate	What must be true	Evidence	Typical owner
Data	Migrated records reconcile to the old system	Signed reconciliation sheets	Finance lead and system admin
Workflows	Each department has run real scenarios	UAT sign-off per department	Department managers
People	Every user trained at the right level	Attendance and competency check	Operations manager
Integrations	Accounting, payments and portals tested	Test transactions traced end to end	Finance lead
Infrastructure	Devices, access, backup and restore tested	Test logs	System admin
Cutover	Timed rehearsal done, rollback point agreed	Written plan, signed	Project lead
Support	Issue owner, severity scale and contacts live	Support roster	Project lead
Decision	Criteria met, risks accepted in writing	Go/no-go record	Dealer principal

The sections below take these gates one at a time.

Gate 1: Data you can trust

Bad data is the most common reason a launch week goes wrong, and it is the part of a project most often underestimated. Plan for more than one trial migration. BusinessHub recommends multiple rounds of validation because the first migration rarely succeeds perfectly.

A layered approach keeps the checking manageable. Interactive Australia’s data migration framework describes four levels: volume reconciliation, field-level validation, business logic validation and integration validation. Applied to a dealership:

Volume. Compare record counts for customers, suppliers, equipment units, serial numbers, parts, open work orders, open rental contracts and open quotes between the old and new systems.
Field accuracy. Pull a sample across different years and record types. Check that serial numbers, model codes, bin locations, cost and sell prices, and customer contacts match the source.
Business logic. Check the numbers that drive decisions: inventory on hand and its value, debtor and creditor balances, open purchase orders, warranty claims in progress, and rental fleet status.
Integrations. Confirm that a migrated customer, a new invoice and a payment all flow through to your accounting package and land in the right accounts.

Before sign-off, trial migrations should land cleanly, validation checks should pass and reconciliation scripts should balance, in line with the framework above.

Dealer-specific data traps

Serial numbers and unit history. A machine’s service history, warranty status and hire history should stay attached to the serial number, not to a customer who has since changed.
Parts supersessions and kits. Check that superseded part numbers still resolve and that kit components deduct correctly.
Open work in progress. Decide whether open work orders and hire contracts are migrated in flight or finished in the old system. Write the rule down.
Tax cases. Include GST-free, mixed and adjusted transactions in your test sample.
Credits and adjustments. One credit note against a multi-invoice job tells you more about data quality than a hundred clean records.

If you are moving from a legacy platform, our guide on migrating data from a legacy DMS without losing history walks through the history side of this in more detail, and our DMS migration page explains how we approach the switch.

Gate 2: Real workflows with real data

A system can be correctly configured and still fail the business. Test cases should reflect end-to-end scenarios including hand-offs between teams, approvals, exceptions and reporting, as SoftLabs advises. For a dealership, that means each department runs its own scripts, plus a few that cross departments.

Sales and quoting

Create an enquiry, build a quote with options and attachments, convert it to a deal and generate the build or commissioning order.
Check margin, discount approval and GST on the final document.

Service workshop and field service

Book a job, issue a work order, allocate a technician, record labour and parts, and invoice.
Run the same job on the mobile app with the device offline, then reconnect and confirm the data syncs. Check this in the places your technicians actually work.

Parts and warehouse

Look up a part by number and by description, reserve it to a work order, raise a purchase order, receive stock and check the bin.
Transfer stock between branches and confirm both locations update.

Rental

Quote a hire, create the contract, deliver, extend, return with a damage or meter-hours charge, and invoice.
Confirm utilisation and downtime reporting reads correctly from migrated assets.

Warranty and finance

Raise a warranty claim from a work order, track it to recovery, and trace the credit through to the ledger.
Run the month-end reports your accountant expects.

Use the pattern these testing guides recommend: complete scenarios built on imported test records, such as a customer with several units, a changed owner or a job with several invoices. Point of Sale’s ERP migration testing guide suggests tracing an order from a migrated customer through pricing, tax, inventory reservation, invoice, payment and accounting entries.

For the cross-department test, trace one machine from quote to delivery to first service to warranty claim. If the serial number follows it without re-keying, your data is travelling once, which is the goal.

Gate 3: People, training and day-one support

Project Perfect’s checklist asks for more than a training roster: all users trained, the success of training validated, documentation available, training ready for new hires, people on the floor on day one, and a help desk ready. The Jiwa transition guide adds that several classes at different levels beat one session for everyone.

A practical split for a dealership:

Counter and parts staff: lookup, quoting, picking, receiving, returns.
Service advisors and technicians: work orders, time capture, mobile app, inspections, sign-off.
Rental coordinators: contracts, extensions, returns, charges.
Finance and admin: invoicing, supplier bills, reconciliation, reporting.
Managers: dashboards, approvals, exception reports.

Validate by watching someone complete a task unaided, not by counting who attended. Put the answers to the questions people keep asking into one short internal guide with screenshots from your own configuration.

Gate 4: Infrastructure, access and compliance

The infrastructure items on the Project Perfect list still apply to a cloud system in a modified form: devices configured and tested, network and remote access tested, security profiles implemented, printers installed, and a backup and restore approach created and tested. For a cloud DMS, add: single sign-on or password rules, role permissions by department, and a check that every branch and workshop bay has connectivity or a tested offline fallback.

Printer and tablet set up at a workshop counter

Privacy, tax and records

Three Australian requirements are worth checking on the launch checklist. Confirm the detail with your accountant or a privacy adviser for your situation.

Data breaches. Under the Notifiable Data Breaches scheme, organisations covered by the Privacy Act 1988 must notify affected individuals and the OAIC when a breach is likely to result in serious harm. Make sure your launch support plan names who decides whether an incident is notifiable.
Record keeping. The ATO says businesses must keep their records for at least five years, and its record-keeping rules say you need to be able to reconstruct original data if your record-keeping system changes. Before you close the old system, confirm you can still produce its historical records, for example through a full export. Our guide to exporting data from a DMS covers what to ask for.
GST. Test tax codes on real documents, as in the scenarios above, and have your accountant review a sample of invoices and a trial BAS-ready report.

Data ownership matters here too. Know before launch how you would get your data out, in what format, and how fast. We cover the contract points in three contract demands to test for DMS data ownership.

Gate 5: AI readiness for a DMS or ERP

AI features in a DMS or ERP, such as natural-language search, suggested actions, drafted documents or help with routine admin, add a layer to the go-live checklist. They do not replace any of the gates above. The same principle applies: the output is only as reliable as the data and permissions underneath it. We would not switch AI on for a department until that department has passed its data and workflow gates.

AI checklist

Clean source data first. Confirm that the records AI will read, such as parts, units, customers and open jobs, passed reconciliation. Suggestions built on duplicate customers or stale stock are only quicker mistakes.
Permissions. AI should see only what the person asking is allowed to see. Test with a counter user, a technician and a manager, and confirm each gets the right scope.
Review rules. Decide which AI outputs a person must approve before they leave the business: customer quotes, invoices, warranty submissions, supplier orders. Write the rule per document type.
Test with real prompts. Collect 20 questions staff would actually ask (‘which units are due for service’, ‘what is on order for this customer’) and check each answer against a known source.
Data boundaries. Ask your vendor in writing where your data is processed and how it is used. Record the answer in your privacy documentation.
Seats and cost. Decide who needs AI access in week one. Our MDMS AI is priced at $449 AUD per month, and each AI-enabled user is $29 AUD per month per seat, so a pilot with one team is easy to size. See the MDMS AI options.
Measure. Pick two or three measures before launch, such as time to quote, time to find a part, or admin hours per week, and compare after 30 days.

One good first use is the branch-transfer process, where an assistant can help staff move stock between locations without creating a false sale. Our article on branch transfers with an AI DMS shows how that works in practice.

Gate 6: Cutover plan and rehearsal

The cutover is the transition itself, and it is worth a written plan. BusinessHub recommends a detailed plan that identifies every task, assigns responsibility, sets timing and is practised at least once through a dry run. ERP Sherpas adds that stakeholders should agree the plan beforehand, sign it off, and mark the rollback points where go-live can be abandoned.

A dealership cutover plan usually covers:

Freeze date and time for new transactions in the old system.
Final extraction, conversion and load, with a measured duration from the rehearsal.
Validation: counts, balances and a short list of key transactions.
Integration switch-on, including accounting.
User access, devices and mobile app logins.
Communication to customers, suppliers and staff.
First live transactions in each department, watched by a named person.

Choose a quiet trading window for your own business, not a month-end or the peak of a seasonal rush. The ERP Search Australia roadmap describes the same timed rehearsal, with owners and checkpoints for each step.

Phasing can reduce the risk. Starting with the module that hurts most, then adding departments, keeps each cutover small. Our articles on phased DMS rollout and DMS implementation time explain how dealers sequence this.

The go/no-go meeting

Hold the decision meeting a few days before cutover, so that a no-go still leaves time to fix things. ERP Sherpas lists minimum exit criteria: signed-off integration and end-to-end testing, a performance test that simulates a day in the life, and no high-priority issues outstanding.

Use a one-page scorecard.

Criterion	Go if	No-go if
Data reconciliation	All counts and balances agree, variances explained	Unexplained variances in stock or ledgers
UAT	Signed by each department manager	Any critical scenario failing
Defects	No open critical or high issues	Any open critical issue
Training	Every user passed a hands-on check	Key roles untrained
Integrations	Test transactions reach accounting correctly	Mismatch in invoices or payments
Cutover rehearsal	Completed within the planned window	Not rehearsed, or overran
Rollback	Point and trigger agreed	Not agreed
Support	Roster, severity scale and contacts published	No named issue owner

The dealer principal, or whoever holds that authority, should sign the decision. If one item fails, record whether you are fixing it, accepting the risk, or delaying. A recorded decision beats a hallway agreement.

Post-go-live support plan: the first 30 days

Go-live is the start of stabilisation. CTO Input’s 30-day stabilization plan advises assigning one person to own the issue list, holding a short daily review, offering a single path for support tickets, using a clear severity scale and giving fast answers on workarounds. Its first week focuses on safety and continuity with non-critical enhancements frozen, and its second week on workflow friction and adoption.

A plan that fits a dealership:

Day 1 to 7: protect continuity

Run smoke tests each morning: one invoice, one work order, one parts pick, one hire return.
Hold a 15-minute review at the start of every day. Review new issues, severity and owners.
Keep floor support in the workshop, parts counter and rental yard.
Freeze feature requests, and log them for later.
Check the accounting sync daily and compare end-of-day totals with the old system if you are running both for a short period.
Define severity. For example, critical means a team cannot invoice or issue parts; high means a workaround exists but costs time; normal means a cosmetic or training issue.

Day 8 to 14: remove friction

Ask each department what takes longer than before and why.
Fix permissions, templates and defaults that cause repeat questions.
Run top-up training where the issue log shows the same confusion.
If AI features are on, review a sample of outputs and the corrections staff made, and adjust the review rules.

Day 15 to 30: stabilise and measure

Move from daily to twice-weekly reviews once critical issues stop appearing.
Run the first month-end close and reconcile against your accountant’s expectations.
Compare the measures you set before launch.
Plan the next module or department, using what the issue log taught you.
Decide when the old system is closed down, and confirm you hold a complete export of its records.

At the end of the 30 days, hold a review. Look at what went live, what is outstanding, who owns each open item, and how support moves into normal operation with named contacts and a response target.

Perspective

We built MDMS for equipment dealers because the usual go-live problem is not the software, it is the scavenger hunt: data in one place, quotes in another, and parts and rental in a third.

That is why we favour modular adoption. Starting with the department under the most pressure means the checklist above applies to a small, testable scope, not the whole business at once. Setup can take under an hour for a module, and the real effort goes where it should: validating your data and training your people.

We also think AI belongs after the fundamentals, not before them. When your serial numbers, parts and customers are reconciled and your workflows are proven, AI can help your team find, draft and decide faster. We designed MDMS AI to sit on that foundation, with your data staying yours and no lock-in.

Our aim is for your data to travel once, and for the checklist to be short because the system made the work simple.

ModernDMS

Start with the module that matters most

MDMS is a dealer management system built for equipment dealerships, with modules for service workshop, parts, rental, sales and quoting, warranty, field service and finance. Individual modules are $59 AUD per month, and the General Ledger & Operations and Equipment Dealer Suite plans are $259 AUD per month each. A data upload service is $259 AUD one-off per module, and a training package is $499 AUD one-off per module. Current pricing is on our pricing page.

Moderndms

If you want a go-live plan for your own dealership, start a trial or talk to us through the MDMS site, and we will map the gates above to your modules.

FAQ

How long before go-live should we start the checklist?

Start when you choose the system, not when the date is set. Data checks and training take the longest, so begin trial migrations and scenario scripts early. Our articles on implementation time explain how phasing affects the timeline.

Who should sign off the go/no-go decision?

The dealer principal or general manager should make the call, with written input from each department manager, the finance lead and whoever runs the system. Each department head signs the UAT for their area.

Do we need to run the old and new systems in parallel?

A short, defined period of dual entry in one department can reveal configuration, training or scope problems, as some implementation guides suggest. Keep it brief and limited, because double entry tires teams quickly. Choose a pilot team instead of the whole business.

What should we check before turning on AI features?

Check that the underlying data has reconciled, that permissions limit what each user sees, and that you have written rules on which AI outputs need human review. Then pilot with one team and measure time saved before extending seats.

What records must we keep after the old system is closed?

The ATO requires business records to be kept for at least five years and expects you to be able to reconstruct original data if your system changes. Keep a complete export of the old system and confirm the details with your accountant.

DMS Go-Live Checklist for Equipment Dealers, With AI Checks