The dealership management system (DMS) market has been dominated by two incumbents — CDK Global and Reynolds and Reynolds — for the better part of four decades. In the last five years, a cloud-native challenger called Tekion has entered the conversation with a fundamentally different architecture, aggressive venture capital backing, and a narrative that the incumbents' technology is decades out of date.
But if you look at what the 10 largest dealership groups in the United States actually run, the story is far more one-sided than the industry buzz suggests. CDK Global holds roughly 80% penetration among the top 10 groups by revenue. Reynolds and Reynolds appears in selective holdover positions — typically stores acquired from smaller groups — but serves as a primary DMS for exactly zero of them. Tekion, despite winning some of the loudest press coverage in automotive technology, has yet to land a top-10 group at meaningful scale.
This article is not just a scorecard of which group runs what. It is a comparison of the three platforms themselves — their architectural philosophies, their go-to-market strategies, their enterprise readiness, and the practical reasons why the top 10 groups have made the choices they have. For franchise dealers evaluating their own DMS path — whether you operate 3 rooftops or 30 — the patterns at the top of the market contain lessons that apply at every scale.
The table below summarizes the DMS landscape among the 10 largest US automotive retail groups, sorted by approximate 2025 revenue. Revenue figures for public groups (Lithia, AutoNation, Penske, Group 1, Asbury, Sonic) are sourced from their most recent annual filings. Private group figures (Hendrick, Berkshire Hathaway Automotive, Holman, Larry H. Miller) are industry estimates based on published rankings and operational data.
| Rank | Group | 2025 Revenue | Primary DMS | Secondary / Legacy | DMS Trend |
|---|---|---|---|---|---|
| 1 | Lithia & Driveway | $36.2B | CDK Global | Reynolds at acquired stores | Stable on CDK |
| 2 | Penske Automotive Group | $30.1B | CDK Global | — | Stable on CDK |
| 3 | AutoNation | $26.8B | CDK Global | Reynolds (acquired stores), Dealertrack (F&I) | Stable on CDK |
| 4 | Group 1 Automotive | $17.4B | CDK Global | — | Stable on CDK |
| 5 | Asbury Automotive Group | ~$16B | Migrating | CDK Global (legacy) | Active migration underway |
| 6 | Sonic Automotive | ~$14B | CDK Global | Reynolds at select stores | Renewed CDK post-ransomware |
| 7 | Hendrick Automotive Group | ~$12B | CDK Global | — | Stable on CDK |
| 8 | Berkshire Hathaway Automotive | ~$10B | CDK Global | — | Stable on CDK |
| 9 | Holman Automotive | ~$10B | CDK Global | — | Stable on CDK |
| 10 | Larry H. Miller Automotive | ~$8B | CDK Global | Reynolds at select stores | Stable on CDK |
Revenue figures: public filings for Lithia, AutoNation, Penske, Group 1; industry estimates for private groups Asbury, Sonic, Hendrick, Berkshire Hathaway Automotive, Holman, and Larry H. Miller. DMS assignments based on published technology profiles, job postings, dealer group reporting, earnings call disclosures, and public documentation.
The headline is impossible to miss: nine of the top 10 groups use CDK Global as their primary or exclusive DMS platform. The only exception — Asbury — is a legacy CDK shop currently in the middle of a migration, not a group that started on something else. Even Sonic Automotive, which publicly re-evaluated its DMS strategy after CDK's June 2024 ransomware attack, chose to renew with CDK.
This level of concentration at the enterprise tier is unusual in automotive technology. For comparison, the CRM landscape among the same 10 groups includes Salesforce Automotive Cloud, CDK CRM, Reynolds ERA-IGNITE, and proprietary in-house builds. Website platform choices range across Dealer.com, DealerOn, Dealer Inspire, and custom solutions. Parts procurement systems vary. But at the DMS level — the operational backbone that runs accounting, inventory, service, parts, F&I, and compliance — the answer is almost universally CDK.
Understanding why requires a deep look at each platform's architecture, go-to-market approach, and the structural dynamics of the enterprise DMS market.
CDK Global is the product of a 2014 spin-off from ADP's dealer services division. Before that, it was ADP's Dealer Services group, which had been building dealership management software since the early 1970s. The company runs three core DMS product lines:
CDK Drive is the flagship enterprise platform. It is a thick-client Windows-based system that has been continuously modernized over decades — bolting on web modules, cloud-hosted infrastructure, API layers, and third-party integration gateways. Drive handles multi-location consolidations, inter-company accounting, and the franchise-specific compliance workflows that enterprise groups require. For a 200-rooftop group running 15-plus OEM brands, Drive's general ledger structure supports separate books per location, consolidated tax filings across multiple states, and visibility layers that let regional VPs see their stores without exposing corporate-level data downward.
CDK DMS Light (formerly CDK Service) is a lighter-weight platform aimed at smaller operations. It has been less relevant at the top-10 level.
CDK Blueprint is the company's cloud-hosted DMS offering — a full rebuild of the core DMS for browser-based deployment. Blueprint is CDK's answer to the cloud-native threat posed by Tekion. It runs on Microsoft Azure, supports modern REST APIs, and has a significantly more modern UI than the legacy Drive client. As of early 2026, Blueprint remains in phased rollout. CDK has not yet mandated a migration timeline for Drive customers, which means most enterprise groups are still on the legacy platform.
CDK's dominance among the top 10 groups is not inertia alone. Three structural factors make CDK disproportionately valuable at scale.
OEM integration depth. A group like Lithia or AutoNation operates franchise agreements with 20 or more automakers. Each OEM runs its own warranty processing system, parts ordering portal, vehicle invoicing workflow, incentive tracking database, and compliance reporting requirements. CDK has spent more than 50 years certifying and maintaining integrations with every major manufacturer — and most minor ones. When a $36.2B group like Lithia needs warranty claims to flow seamlessly for Chevrolet, BMW, Toyota, Honda, Mercedes-Benz, Hyundai, Kia, Subaru, and Ford across the same DMS, CDK's integration catalog has no competitor even in the same tier. Dealertrack (Cox Automotive) has the second-best OEM integration breadth, with particular strength in F&I workflows. Reynolds' integrations are deep for the franchises it certifies but narrow relative to CDK's catalog. Tekion's integration layer is modern and well-architected but covers fewer OEMs with less depth per brand.
Multi-location financial architecture. Enterprise accounting for a dealership group with 300-plus rooftops is not simply 300 copies of single-store accounting. It requires a general ledger that supports inter-company transactions between stores, consolidated P&L statements at the regional and corporate level, allocation of shared expenses (marketing spend, administrative overhead, centralized BDC costs), tax filings across dozens of state jurisdictions, and role-based data permissions that give corporate finance full visibility without exposing store-level operational data to unwanted eyes. CDK's Drive platform was architected for this from the ground up. Most mid-market DMS products — including several cloud-native contenders — simply do not have this capability, which automatically disqualifies them from enterprise consideration regardless of how good their UX or AI features are.
Switching cost as a moat. A full DMS migration for a 50-rooftop group takes 12 to 18 months and costs $2 million to $5 million in implementation fees, data migration tools, staff overtime, integration rebuilding, productivity loss, and parallel-system overlap. For a 200-rooftop group, multiply those figures by three to five times. The cost is not just financial — it is operational risk. Every integration that breaks during a DMS migration creates a business disruption that hits the P&L immediately. For publicly traded groups reporting quarterly earnings, the risk of a botched DMS migration is an existential concern that no board of directors will greenlight lightly. CDK knows this. The incumbency advantage is self-reinforcing: the harder it is to leave, the harder it is to stop winning enterprise deals.
The June 2024 CDK ransomware attack is the most consequential vendor reliability event in automotive retail history. Two full weeks of systems downtime across 15,000-plus dealerships. Operations forced back to pen-and-paper processes. Billions in estimated lost revenue across the US dealer body. The event permanently changed how dealers evaluate DMS vendor reliability, data sovereignty, and disaster recovery planning.
And yet — nine of the top 10 groups are still on CDK.
This fact is less paradoxical than it first appears. The ransomware attack was a catastrophic failure of CDK's security posture. But it did not change the underlying economics of DMS switching costs. The same factors that made CDK hard to leave before the attack — OEM integration breadth, multi-location accounting depth, the sheer organizational disruption of a migration — still apply after it. CDK offered affected customers service credits and contract concessions in the attack's aftermath. More importantly, the company invested heavily in infrastructure improvements: additional Azure redundancy, enhanced security monitoring, incident response retainer agreements with multiple firms, and a cybersecurity advisory board with outside specialists.
For enterprise groups, the calculus was straightforward: absorb the risk of another CDK incident (with improved but still imperfect security) or absorb the certain cost and disruption of a 12-to-24-month platform migration. The majority chose the known risk over the known cost.
Sonic Automotive's decision is the most instructive case. Sonic went through a formal DMS evaluation process following the ransomware attack. The company evaluated alternatives including Tekion and Reynolds. It ultimately renewed with CDK. The details of that evaluation are not public, but Sonic's outcome suggests that even after a vendor failure large enough to make national headlines, the challenger platforms could not demonstrate sufficient enterprise readiness to justify the migration cost at Sonic's scale.
Asbury, by contrast, used the ransomware disruption as a catalyst for a migration that was already under consideration. The group absorbed DMS implementation costs as an earnings headwind in Q1 2026 — a rare transparent disclosure from a top-10 group about technology migration expense.
Reynolds and Reynolds has been in the dealership software business longer than any active competitor. Founded in 1866 (predating the automobile itself), the company built its modern DMS business on the ERA platform, a green-screen system that was state-of-the-art in the 1980s and has accumulated interface layers ever since. ERA-IGNITE is Reynolds' web-enabled modernization, but the underlying architecture remains fundamentally the same: a centralized, on-premises or hosted system with a proprietary data model and a walled-garden integration philosophy.
Reynolds' approach to integration is the single most important factor distinguishing it from CDK and Tekion. The company historically required all third-party software that touches the DMS to go through Reynolds' own integration framework — and to pay for the privilege. This "approved vendor" model gave Reynolds tight control over the dealership technology ecosystem but created significant friction for dealers who wanted to use best-of-breed tools from non-Reynolds-approved vendors. In practice, it meant that a dealer on Reynolds had fewer integration options, longer lead times to connect new tools, and less flexibility to swap out underperforming software.
Reynolds does not appear as a primary enterprise platform among the top 10 groups. But it does appear in specific secondary positions.
The dominant pattern is acquisition inheritance. When a top-10 group acquires a dealership from a smaller operator that was running Reynolds, the economics of a forced migration rarely justify the disruption. The acquired store continues on Reynolds until its contract expires — typically three to seven years — at which point the group evaluates whether to migrate to its primary CDK platform or renew the Reynolds arrangement. AutoNation and Sonic both explicitly acknowledge running Reynolds at some individual franchise locations through exactly this mechanism.
The secondary pattern is franchise-specific fit. Reynolds has historically maintained particularly strong integrations with certain OEMs — notably Ford and General Motors — where its DMS workflows align closely with manufacturer requirements. For a group running a single-location Ford store acquired as part of a multi-brand portfolio, the calculus of migrating that store off Reynolds to CDK may not pencil out, especially if the franchise-specific integration quality is higher on Reynolds.
But the notable absence tells the story: no top-10 group has chosen Reynolds as its primary enterprise DMS platform in a greenfield decision in recent memory. The company's per-user pricing model, multi-year lock-in contracts, and legacy architecture make it a poor fit for enterprise groups that need flexibility at scale. Reynolds' core strength today is in the mid-market — groups of 5 to 50 rooftops where its accounting depth, operational stability, and manufacturer-certified workflows outweigh its integration limitations and cost structure.
Reynolds has been slower than CDK to announce cloud-native DMS plans. The company offers hosted versions of ERA-IGNITE but has not committed to a full architectural rebuild in the way CDK has with Blueprint or Tekion has from its founding. This matters because the industry direction is unmistakably toward cloud-based, API-first platforms. Every major DMS vendor — including CDK — has accelerated cloud migration timelines in response to Tekion's market entry, even if they remain years behind in delivery.
Reynolds' strategy appears to be to defend its mid-market stronghold while selectively adding cloud capabilities to its existing platform rather than rebuilding from scratch. Whether this strategy proves viable over the next decade depends on how quickly mid-market dealers start demanding the same cloud-native experience that Tekion offers at the premium tier. If mid-market adoption of cloud DMS crosses a tipping point — say, 20% of new DMS purchases — Reynolds will face the same architectural pressure that the enterprise vendors are already navigating.
Tekion is the only DMS platform in this comparison that was built from the ground up as a cloud-native, API-first, AI-embedded system. Its founding premise is straightforward: if you were designing a DMS for a modern automotive retail environment — digital retailing, omnichannel service booking, real-time inventory syndication, AI-driven recommendations — you would not start with a 1980s-era green-screen architecture and try to modernize it. You would build on a modern cloud stack (Tekion runs on Google Cloud Platform and AWS), with a unified data model, RESTful APIs for every function, and machine learning models embedded at the application layer rather than bolted on as an afterthought.
The architectural difference has real consequences for dealers who use the system:
Unified data model. Tekion stores all dealership data — sales, service, parts, F&I, accounting — in a single database schema rather than in siloed modules that communicate through batch exports or middleware. This means real-time inventory accuracy between service and sales, a single customer record across every touchpoint, and no reconciliation headaches between departmental systems.
API-first design. Every function in Tekion is accessible through a documented API. This makes it dramatically easier for dealers to connect their preferred third-party tools — DMS-integrated websites, CRM systems, marketing platforms, inventory syndication services — without waiting for Tekion to build an integration or pay integration fees. For a dealer who values best-of-breed tool selection over platform lock-in, this is a structural advantage that no incumbent matches.
Native AI. Tekion embeds machine learning at the DMS level rather than offering it as an add-on module. Predictive service scheduling, parts demand forecasting, vehicle pricing recommendations, and service labor optimization are features of the core platform rather than separate products that require additional contracts and integration work.
Modern UX. Tekion's interface is browser-based, responsive, and designed for the workflows of a modern dealership — digital deal jackets, online service check-in, mobile approvals. Dealers who demo Tekion frequently describe it as "the DMS that looks like it was built this decade," which is a damning comparison for the incumbents but an accurate description of the user experience gap.
For all its architectural advantages, Tekion's adoption among the top 10 dealer groups is effectively zero.
The company has made well-publicized wins with smaller groups — typically 1-to-15-rooftop operations — and individual dealerships. It has built a strong brand among digitally progressive operators and has received significant venture capital funding (over $500 million raised, including a $250 million Series D at a $3.5 billion valuation in 2021). CEO Jay Vijayan is a former Tesla CIO and was instrumental in building Tesla's in-house DMS, which gives the company a founding narrative rooted in automotive technology reinvention.
But none of this has translated into enterprise wins at the scale of the top 10 groups.
AutoNation was Tekion's highest-profile enterprise customer. The group piloted Tekion in a subset of its stores beginning in 2021, making it the first top-10 public group to give the challenger platform a serious evaluation. If the pilot had succeeded and expanded, it would have been the transformative enterprise reference that Tekion needed to validate its platform for the largest groups.
Instead, AutoNation declined to expand the partnership. The group eventually returned to CDK as its primary platform. AutoNation's public statements attributed the decision to Tekion's inability to handle the group's scale and complexity — specifically in multi-OEM integration depth, enterprise accounting, and the operational reliability required for a $26.8B group running hundreds of rooftops. Tekion's public rebuttal was that the AutoNation pilot was never intended to be a full-scale deployment and that conclusions about the platform's enterprise readiness should not be drawn from a limited-scope trial.
The truth likely lies between these positions. The AutoNation pilot was probably truly limited in scope and did not exercise Tekion's enterprise features at the level of a full 300-rooftop deployment. But the outcome was the same regardless of who was right: the largest public dealer group in the country publicly declined to scale with Tekion, creating a reference story that every subsequent enterprise prospect has had to evaluate.
Tekion faces a classic enterprise adoption dilemma. It cannot prove that it can handle top-10 group complexity without winning a top-10 group as a customer. But it cannot win a top-10 group as a customer without proving it can handle that complexity.
The gap is widest in three specific areas:
OEM integration depth. CDK maintains certified integrations with every major OEM (and dozens of minor ones). These integrations are not simple API connections — they are deeply embedded workflows that handle franchise-specific compliance, warranty claim formatting, vehicle ordering protocols, incentive tracking, and manufacturer reporting. Tekion has to build each of these from scratch or negotiate OEM certification, which takes years for major manufacturers. A top-10 group cannot afford to run a single franchise brand without fully certified integrations.
Multi-location enterprise accounting. As discussed, the accounting requirements of a 200-rooftop group go far beyond what a single-store DMS can handle. Tekion's unified data model gives it architectural advantages in this area — a single customer record, real-time consolidation, automated inter-company transactions — but the feature set for enterprise accounting is not just about functional completeness. It is about auditability, compliance with automotive-specific accounting standards, tax filing support across 50 states, and the institutional trust that comes from having hundreds of dealership financial controllers running the same system for years.
Service and parts depth. DMS systems were originally built to manage parts inventory and service repair orders — these are the most complex operational workflows in a dealership. Top groups run massive service operations with hundreds of technicians, complex warranty processing requirements, parts supply chains across multiple brands, and manufacturer-specific repair procedures. Tekion's service and parts modules are modern and well-designed, but the depth and breadth of CDK's service module — built and refined over four decades — is hard to match in a single product generation.
As of early 2026, Tekion's estimated market share among US franchise dealerships remains under 5% by rooftop count. Among the top 10 groups by revenue, its share rounds to zero.
This understates Tekion's influence on the market in an important way. Every DMS vendor — including CDK — has accelerated their cloud migration plans, increased investment in API connectivity, and improved their UI specifically because Tekion raised the standard for what dealership software should be. CDK's Blueprint initiative, launched in response to competitive pressure from cloud-native platforms, would almost certainly not exist in its current form without Tekion proving that a cloud-native DMS could work. The architectural pressure Tekion has applied to the industry will outlast any individual deal win or loss.
But the headline for franchise dealers evaluating their own DMS decisions is this: Tekion is a legitimate platform with a genuinely differentiated architecture, but its enterprise track record is thin. For a 1-to-5-rooftop group with a single major franchise, it may be an excellent choice. For a 20-plus rooftop multi-brand group, it is a bet on a company that has not yet proven it can operate at that scale.
The June 2024 CDK ransomware attack is the pivot point around which every current DMS decision turns. Understanding what happened after the attack — and what it means for future platform decisions — requires parsing both the visible outcomes and the structural changes that are harder to see.
Dealer expectations for disaster recovery. Before the attack, most dealers did not have a DMS disaster recovery plan. After the attack, every group above 5 rooftops should have one. The CDK outage demonstrated that the largest, most established DMS vendor can fail catastrophically for an extended period. Dealers who previously treated DMS uptime as a given now ask pointed questions about data backup frequency, recovery time objectives (RTOs), recovery point objectives (RPOs), and whether the vendor has experienced a public security incident before.
Contract negotiation leverage shifted to dealers. Post-ransomware, CDK has faced tougher negotiations with every customer above a certain revenue threshold. Enterprise groups have successfully negotiated shorter contract terms, frozen annual price escalations, and secured concessions on module pricing. Several groups now have contractual language requiring CDK to maintain specific cybersecurity certifications and to notify customers of security incidents within a defined timeframe. The exact savings are not public — enterprise DMS contracts are among the most closely guarded documents in automotive retail — but the direction of travel is clear: the ransomware event moved negotiating leverage toward dealers.
Multi-platform strategy became respectable. Before the attack, running multiple DMS platforms was seen as operational inefficiency — a tax on acquisition-driven growth that smart groups would eventually consolidate away. After the attack, several groups have deliberately maintained multi-platform DMS footprints as a risk mitigation strategy. Running CDK as the primary platform while keeping a Reynolds relationship alive at a subset of stores means the group can survive a vendor outage with less operational disruption. The complexity cost is real, but for groups with the IT resources to manage middleware-based data reconciliation, the insurance value of platform diversity now justifies the overhead.
The migration math. The ransomware attack did not change the fundamental economics of DMS switching costs. Asbury proceeded with a migration that was already in progress. Sonic evaluated alternatives and renewed. The remaining groups made a rational calculation: the certain millions of dollars and years of disruption required to migrate were larger than the expected cost of a future ransomware incident with improved security in place. This math is not flattering to CDK — it is a commentary on how expensive and difficult DMS migration is at enterprise scale.
CDK's enterprise position. Despite losing Asbury (which is migrating but has not announced its destination platform) and facing tougher contract terms, CDK's overall share among the top 10 groups is essentially unchanged. No top-10 group has publicly executed a full-platform migration from CDK to a competitor. This means CDK enters every enterprise renewal with the asymmetric advantage of incumbency: the group can leave, but it is expensive and risky to do so, while staying is the default.
The real migration activity in the DMS market is happening below the top 10, in two distinct tiers.
Tier 1: Mid-market groups (15 to 100 rooftops). This is where Tekion's strongest growth is happening. Groups at this scale have complex enough operations to benefit from Tekion's unified architecture and modern UX, but they are small enough that the migration cost (typically $500,000 to $2 million for a 30-rooftop group) is an investment decision rather than a board-level existential risk. Several mid-market groups have publicly announced Tekion migrations in the last 18 months, and this segment represents the most credible path to enterprise validation.
Tier 2: Independent single-point stores and small groups (1 to 15 rooftops). This is the bulk of Tekion's current deployment base. The economics of a DMS migration for a single store are manageable — typically $30,000 to $100,000 in implementation costs with a 3-to-6-month timeline — and the benefits of modern UX, API connectivity, and native AI are significant for operators who manage their own technology stack. Dealertrack (Cox Automotive) also competes heavily in this segment with its month-to-month contract flexibility and F&I lender network.
The Asbury wildcard. Asbury Automotive Group remains the most watched migration in the industry. With roughly $16 billion in revenue and 100-plus dealerships, Asbury is a top-10 group actively moving off CDK. The company has not publicly named its destination platform. Industry speculation has centered on Tekion — which would be the most significant enterprise validation the company has ever received — but also includes the possibility of a Cox Automotive stack (Dealertrack DMS plus vAuto and the Cox ecosystem) or a multi-platform approach. Asbury's Q1 2026 earnings release explicitly named DMS implementation costs as an earnings headwind, confirming the migration is real and ongoing. If Asbury confirms a Tekion deployment at scale, it reshapes the enterprise DMS competitive landscape overnight. If it lands on a different platform or a multi-vendor strategy, Tekion's enterprise narrative faces a significant setback.
The table below summarizes the key differences between the three platforms across dimensions that matter for dealers evaluating their DMS strategy.
| Dimension | CDK Global | Reynolds & Reynolds | Tekion |
|---|---|---|---|
| Architecture | Thick-client (Drive) with cloud overlay (Blueprint) | Green-screen ERA with web front-end (ERA-IGNITE) | Cloud-native, API-first, from founding |
| OEM Integration Breadth | Widest in industry (50+ years of certs) | Strong for major OEMs, narrow for imports | Moderate; building rapidly but gaps remain |
| Enterprise Accounting | Deepest multi-location GL in DMS industry | Strong single-store accounting; limited enterprise | Promising architecture; thin enterprise track record |
| Integration Philosophy | Open ecosystem (API gateways, third-party marketplace) | Walled garden (approved vendor program) | API-first (any third-party tool can connect) |
| AI/ML Features | Incremental (add-on modules, mostly post-acquisition) | Minimal (limited to core DMS workflows) | Native (embedded in platform from day one) |
| Contract Terms | 3-7 years; enterprise groups can negotiate down | 5-7 years; notoriously hard to exit | 3-5 years; generally more flexible |
| Pricing Model | Per-user + OEM module costs | Per-user; premium pricing | Subscription-based; all-inclusive tiers |
| Typical Monthly TCO (single store) | $2,000 - $30,000+ | $3,000 - $15,000+ | $5,000 - $15,000 |
| Top-10 Group Penetration | ~80% primary / ~90% present | ~0% primary / ~30% secondary | ~0% |
| Best For | 10+ rooftop multi-brand groups; enterprise scale | 5-50 rooftop single-brand groups; accounting depth | 1-15 rooftop tech-forward groups; digital retailing |
Note: TCO figures are base licensing and standard modules only. Enterprise groups face additional costs for custom integrations, dedicated account management, multi-year implementation consulting, and internal IT headcount — typically adding 30-50% to published ranges.
The fact that 9 of the 10 largest dealer groups in the United States run the same DMS platform carries implications that extend beyond those groups themselves.
CDK's enterprise concentration gives the company a structural advantage that shapes pricing, product development, and competitive dynamics across the entire DMS market. Because the largest groups are effectively locked in, CDK can invest margin percentage from those accounts into acquiring mid-market competitors, funding cloud modernization (Blueprint), and sustaining the OEM integration certification program that is its deepest moat. Challengers who want to compete at the enterprise level must first win at the mid-market level — a necessary but not sufficient condition — and then convince a top-10 group to absorb the migration cost. The concentration at the top creates a winner-take-most dynamic where CDK's enterprise revenue funds competitive advantages that compound across the entire market.
Market concentration in DMS means market concentration in dealer data. When 9 of the 10 largest groups run the same platform, that platform holds an unprecedented volume of operational data about US automotive retail — transaction prices, service demand patterns, parts consumption rates, customer behavior, F&I product attach rates, and labor productivity. CDK's policies on data usage, data sharing with OEMs, and third-party data access therefore have industry-wide implications. Post-ransomware, several groups have demanded stronger data ownership and portability language in their CDK contracts. But for the broader dealer body — especially mid-market and independent dealers — the concentration at the top means the largest DMS vendor sets industry standards for data policies that affect everyone.
When 80% of your enterprise market is effectively captive, the incentive to innovate is structurally weaker than it would be in a competitive market. CDK has been slower than market expectations to deliver Blueprint at scale, to modernize its UI, and to ship AI features as core platform capabilities rather than add-on modules. The company's R&D spending as a percentage of revenue — which is not separately disclosed — is widely believed by industry analysts to be lower than what a challenger like Tekion spends. This does not mean CDK is a bad product — it means the competitive pressure that drives rapid innovation is muted by the switching costs protecting the enterprise installed base.
The counterargument is that Tekion's market entry has already changed this dynamic. CDK's Blueprint investment, its API gateway initiative, and its acquisition of data and AI capabilities are direct responses to the competitive threat. The question is whether these improvements come fast enough to meet the expectations that Tekion has set for dealers who have seen what a cloud-native DMS can do.
The CDK ransomware attack raised a question that the industry has still not fully addressed: what happens when the single most important software platform in automotive retail — used by 80% of the largest groups and 35-40% of all franchise dealerships — is rendered inoperable for an extended period?
The answer, as we saw in June 2024, is that the industry can survive on manual processes for a week or two but cannot sustain that indefinitely. If a future CDK outage lasted a month — or if a simultaneous attack hit CDK and another major vendor — the economic damage to US automotive retail would be measured in tens of billions. The concentration of DMS infrastructure under a single vendor creates a single point of failure for the industry that no amount of disaster recovery planning can fully mitigate.
This is the strongest argument for multi-platform strategy that exists. Groups that have deliberately maintained diversity in their DMS footprint — even at the cost of operational complexity — are better positioned to survive a future vendor-level outage than groups that have consolidated everything under one roof. The question for the industry is whether the cost of maintaining that diversity is worth the insurance value, or whether the economics of enterprise DMS concentration make it unsustainable for all but the largest groups.
The DMS strategies of the top 10 groups are not directly replicable for mid-market and independent dealers — the economics, scale, and vendor leverage are fundamentally different. But the patterns at the top contain lessons that apply at every level of the market.
Lesson 1: Your switching cost is higher than you think, but lower than AutoNation's.
If a $26.8B group with a dedicated IT team of 200-plus people struggles to migrate off CDK, it is natural to conclude that smaller dealers should never try. That conclusion is wrong. The switching cost for a 1-to-5-rooftop group is dramatically lower in both absolute and relative terms: 3 to 6 months of implementation instead of 12 to 24 months, $30,000 to $150,000 instead of $2 million to $10 million, one general ledger to migrate instead of 300. The incumbency advantage that protects CDK at the enterprise level is real but does not translate linearly to smaller scale. Mid-market dealers who can see the value in a different platform — better UX, modern APIs, native AI — should evaluate their options with the confidence that the migration math works differently at their scale.
Lesson 2: OEM integration depth is the single most important evaluation criterion.
The top 10 groups run 20-plus OEM brands. Most mid-market dealers run 3 to 8. But the same principle applies: if the DMS you are evaluating does not have certified, production-tested integrations for every OEM brand you carry, the platform will not work for your business regardless of how good its UX or AI features are. This is especially important for dealers evaluating Tekion. Check with your OEM representatives about whether Tekion (or any alternative platform) has certified integration status for your specific franchises. Do not rely on the vendor's claim without OEM confirmation.
Lesson 3: Contract terms matter more than monthly price.
The top 10 groups have negotiated shorter contract terms, frozen escalators, and better data portability language in the wake of the ransomware attack. Mid-market dealers should do the same. A 3-year initial term with a mutual renewal option is significantly better than a 7-year term with auto-renewal, even at a slightly higher monthly cost. The flexibility to evaluate alternatives at contract end is worth more than a few hundred dollars per month in savings. Data portability language — the contractual right to export your data in a usable format without additional fees — is non-negotiable in any modern DMS contract.
Lesson 4: Multi-platform is not just for the top 10.
Running two DMS platforms is operationally complex for a 3-rooftop group and may not justify the overhead. But the principle of not putting all your operational eggs in one basket applies at any scale. The minimum viable version of this strategy is: (a) maintain offline backups of critical data (customer records, inventory, service history) independent of your DMS vendor, (b) know exactly what it would cost and how long it would take to switch platforms, and (c) keep your contract terms short enough that you have a credible threat of switching at renewal. You do not need to plan a migration. You need to have the option.
Lesson 5: Tekion is real, but evaluate with clear-eyed expectations.
Tekion's architecture is genuinely differentiated. Its cloud-native design, API-first integration approach, unified data model, and native AI capabilities represent the direction the entire industry is moving. For a dealer who values modern UX, API connectivity, and platform flexibility, Tekion is worth placing on the evaluation shortlist. But the enterprise adoption gap is real. Tekion has not yet proven that it can handle the complexity of a 20-plus rooftop, multi-brand, multi-OEM group. If your operation fits that description — or if you plan to grow to that scale in the next 3 to 5 years — Tekion may not be ready for you, and the incumbents may still be the safer choice despite their architectural age.
Lesson 6: The post-ransomware world requires a new kind of vendor diligence.
Before June 2024, asking a DMS vendor about their cybersecurity certifications, incident response history, and disaster recovery procedures was a checkbox exercise. After the CDK attack, it is a primary evaluation criterion. Every dealer should ask every DMS vendor: Have you experienced a ransomware or security incident in the last 5 years? What is your recovery time objective in hours? Do you maintain independent backups that are not accessible from your production network? Do you have cyber insurance and what does it cover? What contractual protections do you offer customers in the event of a prolonged outage? A vendor that cannot answer these questions satisfactorily should be disqualified regardless of price or features.
The DMS landscape among the top 10 US dealer groups in 2026 is characterized by remarkable stability at the top and significant movement at the margins. CDK Global holds roughly 80% penetration by revenue, and no top-10 group has executed a full-platform migration to a competitor — even after the most catastrophic vendor reliability event in automotive retail history. Reynolds and Reynolds holds secondary positions at specific stores but has been effectively eliminated as a primary enterprise contender. Tekion has the best product architecture in the industry but the thinnest enterprise track record, and its highest-profile pilot (AutoNation) ended without expansion.
The market dynamics that sustain this concentration are structural, not accidental. OEM integration breadth, multi-location enterprise accounting, and switching costs form a competitive moat around CDK's enterprise installed base that no challenger has breached. But the moat is not unbreachable. Asbury's active migration, mid-market Tekion wins, the gradual commoditization of OEM integrations, and the post-ransomware shift in negotiating leverage all create conditions under which a top-10 group could credibly switch in the next 3 to 5 years. The question is not whether it will happen — the history of enterprise software shows that incumbent lock-in eventually breaks — but when, and which challenger will be the one to break it.
For franchise dealers evaluating their own DMS choices, the top-10 patterns suggest a framework that works at any scale: understand your OEM integration requirements before you evaluate architecture; negotiate contract terms harder than you think you need to; prioritize platforms with flexible exit options; maintain the organizational readiness to switch; and treat vendor cybersecurity diligence as a primary evaluation criterion rather than a compliance checkbox. The cost of being locked into the wrong platform at the wrong terms is higher than the cost of being ready to leave.