Reynolds ERA vs Ignite 2026: Which DMS Is Right for Your Store? | DealerInt

The Reynolds transition: ERA to Ignite

Reynolds and Reynolds has been a fixture of dealership technology for decades. Their legacy DMS, ERA (Enhanced Retail Application), has powered thousands of dealerships through multiple industry cycles. In 2023, Reynolds began rolling out Ignite — a cloud-native platform designed to replace ERA over time.

For dealership decision-makers, this transition creates a consequential choice: stay on ERA, migrate to Ignite, or use the migration window to evaluate the entire DMS landscape. This guide covers what each platform offers, how they compare, what migration actually involves, and the critical gap that exists in both.

Reynolds ERA: the legacy platform

ERA has been Reynolds' core DMS for over 15 years. It's a client-server application that runs on-premise (or in a Reynolds-hosted environment). Key characteristics:

Depth of functionality. ERA covers accounting, deal management, parts and service, F&I, CRM, and OEM reporting. The feature set is comprehensive. Stores that have been on ERA for years have built deep workflows around its capabilities.

Stability. ERA is mature software. Bugs are well-documented and well-understood. The platform doesn't change rapidly, which means training investment persists. Staff who learn ERA once rarely need retraining on core workflows.

OEM integration. Reynolds has deep relationships with most OEMs. ERA's OEM data exchange, warranty processing, and incentive management modules are among the best in the industry. For stores where OEM compliance is a primary concern, ERA delivers.

Customization. ERA supports extensive customization — custom reports, custom fields, custom workflows. Large dealer groups have invested significantly in ERA customization over years, and that investment represents a real switching cost.

Limitations of ERA:

• User interface. ERA's interface reflects its era. Navigation is menu-driven, screens are dense, and workflows require multiple clicks. Younger staff accustomed to modern web applications often find ERA frustrating.
• Remote access. ERA's client-server architecture makes true remote access challenging. While remote desktop solutions exist, they're workarounds rather than native capabilities.
• Mobile. ERA's mobile story is limited. Some companion apps exist, but the core platform is desktop-bound.
• Integration flexibility. ERA's integration with third-party tools can be complex. Reynolds' approach historically favors its own ecosystem, and third-party vendors sometimes report friction with ERA integrations.

Reynolds Ignite: the cloud platform

Ignite is Reynolds' answer to the cloud-native DMS trend. It's a browser-based platform built on modern architecture. Key characteristics:

Modern UI. Ignite's interface is a significant upgrade from ERA. Clean layouts, intuitive navigation, and responsive design make it accessible on any device with a browser. Training time for new staff is lower.

Cloud-native. Ignite runs in the cloud. No on-premise servers, no VPN required, no client software to install. Access from any device, anywhere. This matters for dealer groups with distributed management and for GM-level reporting across rooftops.

Mobile-first design. Ignite is designed for mobile access from the ground up. Managers can approve deals, review dashboards, and manage workflows from phones and tablets — a meaningful upgrade for GMs who spend time on the lot or traveling between stores.

Faster updates. Cloud architecture means Reynolds can push updates continuously rather than scheduling on-premise upgrade windows. Features and fixes arrive faster.

API-first architecture. Ignite's modern architecture promises better third-party integration through APIs. This is important for stores that rely on best-of-breed tools alongside their DMS.

Limitations of Ignite:

• Feature parity. As of early 2026, Ignite has not achieved full feature parity with ERA. Some advanced modules — particularly in parts and service, advanced accounting, and certain OEM-specific workflows — are still being built out. Stores with complex requirements should verify feature-by-feature during evaluation.
• Migration complexity. Moving from ERA to Ignite involves data migration, workflow redesign, staff retraining, and a parallel-run period. Reynolds provides migration support, but the process is non-trivial — especially for large stores with extensive ERA customization.
• Track record. Ignite is newer. ERA has decades of field-proven reliability. Ignite's stability and performance at scale are still being established. Early adopters report generally positive experiences, but the platform hasn't faced the full range of edge cases that ERA has survived.
• Customization depth. Ignite's customization capabilities are growing but may not yet match ERA's depth. Stores with heavy ERA customization may find Ignite's current options insufficient.

Feature-by-feature comparison

Pricing considerations

Reynolds doesn't publish list prices for either ERA or Ignite. Pricing is negotiated based on rooftop count, modules selected, and contract terms. That said, some general observations:

• Ignite pricing tends to be subscription-based with per-rooftop, per-month fees. This aligns with the cloud model.
• ERA pricing may include hosting fees if running in Reynolds' data center, or on-premise infrastructure costs if self-hosted.
• Migration costs are real. Data migration, parallel running, training, and temporary productivity loss during transition should be factored into the total cost comparison.
• Contract terms matter. Reynolds contracts are typically multi-year. Understand renewal terms, auto-renewal clauses, and exit provisions before signing.

During evaluation, request itemized pricing for each module on both platforms. Ask for total cost of ownership over three and five years, including migration costs for Ignite.

Migration: what to expect

If you're on ERA and considering Ignite, here's what the migration typically involves:

1. Assessment (4–8 weeks). Reynolds evaluates your ERA configuration, customizations, and integration points. This assessment identifies what migrates cleanly and what requires rework.

2. Data migration (4–12 weeks). Historical deal data, customer records, parts inventory, accounting history, and OEM data must be migrated. Reynolds provides migration tools, but validation and cleanup are the dealer's responsibility.

3. Configuration (4–8 weeks). Ignite needs to be configured to match your workflows — user roles, permissions, report templates, desking defaults, and integration settings.

4. Training (2–4 weeks). Staff need training on the new interface and workflows. Even though Ignite is more intuitive than ERA, habits built over years of ERA use take time to change.

5. Parallel run (2–4 weeks). Running both platforms simultaneously to verify data accuracy and workflow completeness before cutting over.

6. Cutover and stabilization (2–4 weeks). Going live on Ignite and addressing the inevitable issues that arise in production.

Total timeline: 4–9 months for a typical single-rooftop store. Multi-rooftop groups should expect longer, with staggered rollouts recommended.

The override intelligence gap: present in both ERA and Ignite

Whether you stay on ERA or migrate to Ignite, one gap persists: neither platform captures structured override intelligence.

ERA records deal transactions — the final price, gross, finance terms, and F&I products. When a desk manager changes the price, ERA records the new number. It does not require or capture a structured reason for the change. The same is true for Ignite.

This means:

• No aggregated override reporting. You can't run a report showing "total margin lost to competitive matching this month" in either platform.
• No pattern detection. You can't identify that one manager approves 30% more overrides than peers, or that one deal type accounts for 60% of override losses.
• No policy enforcement. Neither platform can require a reason before allowing a price change. Policy compliance is voluntary.
• No real-time visibility. Override activity is invisible until month-end, when gross numbers reveal the damage after it's done.

This gap isn't a bug — it's a design limitation. DMS platforms are built to record transactions, not decisions. The desk decision that determines the transaction is outside their scope.

How DealerInt fills the gap on both platforms

DealerInt works alongside both ERA and Ignite. The Chrome extension sits in the browser and captures override decisions as they happen — on either platform.

For ERA users, DealerInt adds the real-time decision capture that ERA's client-server architecture can't provide. For Ignite users, DealerInt fills the override gap that Ignite's modern architecture still doesn't address.

What DealerInt captures that Reynolds doesn't:

• Structured override reasons (competitive match, manager approval, aging inventory, loyalty)
• Override approver identification
• Real-time gross impact calculation
• Policy compliance scoring per deal, per manager, per department

The result: GMs get dashboards showing override volume, reasons, and margin impact — in real time, not at month-end. Whether you're on ERA or Ignite, the decision layer is the same.

Making the ERA vs. Ignite decision

Here's a framework:

Stay on ERA if:

• Your ERA customizations are extensive and business-critical
• Feature parity gaps in Ignite affect your core workflows
• Your staff is productive on ERA and resistant to change
• You're within 12 months of a contract renewal and want to negotiate from a position of strength

Migrate to Ignite if:

• Mobile and remote access are strategic priorities
• You're recruiting younger staff who expect modern interfaces
• Your ERA infrastructure is aging and requires investment
• You're a multi-rooftop group that needs cloud-based cross-store reporting
• You're planning a broader technology modernization

Evaluate alternatives if:

• You're dissatisfied with Reynolds' pricing or service
• The migration window is an opportunity to assess the full market
• Cloud-native alternatives like Tekion offer compelling features

Regardless of which Reynolds platform you choose, the override gap persists. Address it independently.

Compare DealerInt vs Reynolds for a detailed side-by-side. See how DealerInt integrates with Reynolds for setup instructions. Or start a free trial to see your override exposure data within 30 days.

Book a demo. View pricing. Install the Chrome extension to start capturing desk-level decisions today.