Direct answer: how should a dealer group choose between CDK and Reynolds?
CDK and Reynolds are both dealership operating-system decisions. Choose the provider that can document the stronger fit for your group’s workflows, interfaces, data rights, conversion controls, support model, and exit terms. Public product pages establish each vendor’s stated scope; they do not establish a universal winner, total cost, outage exposure, or migration outcome.
This RFP guide assumes you already know the operating question. If you do not, start with how to choose a dealer management system. For the broader vendor set and migration framework, use the DMS category buyer hub. Public product pages are not independent proof; the research methodology states what we will and will not infer. After a shortlist, the operating document is the DMS migration guide.
Method: what this 2026 comparison verifies—and what it cannot
Last verified September 15, 2026. We reviewed current public CDK and Reynolds product pages for stated DMS scope, integration approach, data-access claims, and published support information. We do not infer current implementation duration, pricing, service levels, data-export rights, third-party coverage, or contract terms from marketing material. Those items are labelled unknown until each finalist confirms them in its current proposal and contract.
Vendor product pages document vendor-stated capabilities. They are not independent proof of implementation quality, interoperability, uptime, pricing, or a dealer group’s outcome. This guide labels those facts unknown until they are confirmed in the current proposal and contract.
What public evidence distinguishes CDK and Reynolds?
The table compares only statements published by the vendors. Each linked cell identifies its source. It does not score either DMS or infer unavailable commercial details.
State of Automotive DMS migration-risk framework
This editorial framework converts a DMS shortlist into six accountable workstreams. It is a documented evaluation model, not first-hand product testing or a vendor score. A group should assign an executive owner and written acceptance criterion to every workstream before a selection decision.
- Workflow fit:map sales, F&I, parts, service, accounting, and group reporting processes; record exceptions and control owners.
- Interfaces and data rights: inventory every CRM, OEM, website, inventory, lender, accounting, warehouse, and vendor dependency; identify its data owner, permitted use, cost, and fallback.
- Conversion and reconciliation: define historical records to move, field-level mapping, test samples, balance checks, defect ownership, and sign-off.
- Cutover continuity: document sequence by rooftop and department, downtime tolerance, manual procedures, rollback criteria, and customer communication.
- Training and support: name role-based training, staffing coverage, escalation contacts, severity targets, and post-launch hypercare measures.
- Contract and exit: confirm scope, term, fee changes, renewal, export format and timing, transition assistance, and termination rights in writing.
Why DMS migration risk deserves an explicit continuity plan
DMS disruption can affect sales, service, inventory, CRM, and accounting workflows. For example, Lithia’s June 2024 Form 8-K reported disruption after CDK suspended systems in response to a cybersecurity incident. This is a case-specific continuity lesson, not a claim that either current product has a particular outage risk.
What should a single rooftop validate?
A single rooftop should begin with the daily workflows that cannot fail: deal finalization, repair orders, parts billing, accounting close, and the interfaces that feed them. Require a working demonstration with representative users and real exception cases. Group capabilities, license terms, and implementation timing remain unknown until quoted.
What should a multi-rooftop group validate?
A dealer group must additionally test shared chart-of-account rules, cross-store reporting, role and permission governance, OEM-specific requirements, centrally owned interfaces, sequencing by rooftop, and local exception handling. Do not assume a documented feature is configured consistently across brands or stores; require that evidence in the rollout plan.
What alternatives belong on a DMS shortlist?
Alternatives may be appropriate when the group’s operating requirements differ from either proposal. Include a provider only after it can document support for the required workflows, interfaces, conversion approach, commercial terms, and governance model. The scope and current fit of any alternative are unknown until evaluated against the same RFP criteria.
Six next steps after the DMS shortlist
- Approve the six-workstream framework and name accountable owners.
- Give every finalist the same module, workflow, and interface inventory.
- Request written data rights, export, security, support, and exit terms.
- Run a conversion and reconciliation test with representative historical data.
- Rehearse cutover, continuity, escalation, and rollback with each implementation team.
- Score only evidence supplied for the group’s documented requirements and retain it with the RFP record.
Frequently asked questions
Is CDK or Reynolds better for a dealer group?
Neither is universally better. Choose the proposal that proves fit for your operating model, interfaces, conversion controls, support commitments, data rights, governance requirements, and exit terms.
What is the biggest DMS migration risk?
The biggest risk is an unowned dependency: a process, interface, report, data set, user role, or control without a named conversion and acceptance owner. Inventory those dependencies before comparing implementations.
What should a dealer group require in a DMS proposal?
Require a named scope, module and interface inventory, data-conversion and reconciliation plan, role-based training plan, cutover and continuity plan, support escalation path, pricing schedule, data-rights terms, and exit assistance.
Source register and corrections
Sources were accessed September 15, 2026. Product pages and proposal terms can change. This review has no named individual reviewer or first-hand vendor implementation test; it is maintained by the State of Automotive Research Desk. Send a correction with a current primary source through the vendor-recommendation flow.
