Switch from Reynolds & Reynolds in 12 minutes.

1. Step 01

   Export your Reynolds data dump

   Open Reynolds, drop into ERA Reports (or eHQ on the older interface), run the Customer Master export to CSV. Pull everything — no date range, no source filter, all rooftops. If your store is on a data-services-gated tier, we'll help you draft the request ticket; the unlock usually clears in 1-2 business days.

   Path: ERA Reports → Customer Master → Export to CSV · We have walked dealers through this export on 30-min screen-shares.

2. Step 02

   We map your fields to Gladius schema in 48h

   Drag the CSV onto the Gladius admin import surface (or email it to us — we'll run the import for you). The file streams up over HTTPS, lands in an immutable archive table (ImportSourceRow), and we hand back a column map within 48 hours. Custom Reynolds fields land in importCustomFields (JSON), searchable from day one.

   Files up to 250 MB stream in chunks. The original CSV is preserved verbatim, queryable forever.

3. Step 03

   Two-week parallel run (Reynolds + Gladius both live)

   New leads dual-write to both systems through a feature-flagged adapter. Your reps see Gladius on their cockpit, Reynolds stays read-only as a safety net, and your manager team gets the full Gladius reporting stack alongside the Reynolds dashboards. Two weeks is the standard parallel window; longer if your team wants it.

   Dual-write is per-source. ADF, web forms, and DNI all stream into both stacks simultaneously. No lost lead during the cutover window.

4. Step 04

   Flip the switch — your reps see no downtime

   When you're ready, we flip the feature flag and Reynolds CRM goes idle. Reps see no UI change because they've been on the Gladius cockpit for two weeks already. Your Reynolds contract keeps running until renewal — we don't ask you to break it — but the floor is fully on Gladius, with rollback still available if anything looks off.

   Rollback window stays open for 24h post-cutover. Per-batch, atomic, one button.

Inside Reynolds & Reynolds: ERA Reports → Customer Master → Export to CSV (or the legacy Reynolds eHQ export if your store is still on the older interface). Reynolds exports a wide CSV that includes the customer master, vehicle history, the long deal notes, and the custom fields your store has been writing for years. Our importer reads every column verbatim — including the Reynolds-specific custom fields — and projects them into Gladius without a schema reshape. If your data is gated behind a Reynolds data-services SOW, we have a separate playbook for that path.

• Every row archived in ImportSourceRow

  The raw CSV is stored verbatim before any projection. The original payload is recoverable forever, even after column-map changes.

• Rows without identifiers are QUARANTINED, never dropped

  If a row is missing a phone, email, or external ID, it does not silently disappear. It lands in a Quarantine bucket you can review and re-process by hand.

• Custom columns preserved in importCustomFields JSON

  Custom DealerCenter / VinSolutions / Elead fields the standard schema doesn’t recognize survive the move as a typed JSON blob, queryable from day one.

• Full audit trail with timestamps + user attribution

  Every projected row carries the importBatchId, the operator who ran the import, the source row ID, and the exact timestamp. Compliance teams love this part.

• Per-batch rollback via single button

  If the first 24 hours show anything you don’t like, one click reverses the entire batch. The archive table is untouched, so a second import can run after we tune the column map.

Want the full matrix? See gladiuscrm.com/compare for the 40+ row breakdown.

• Will I lose my call recordings?

  No. If your call recordings live in the Reynolds call vault (or a Reynolds-bundled vendor), the recording URLs come out in the export and we backfill them onto the Gladius lead record. If a recording is gated behind a Reynolds-only system, we wire a forwarding rule so all new calls land in the Gladius vault from day one — and we keep a link to the legacy recording for the old ones.

• What about my existing texting and email templates?

  Templates port over as plain markdown and we re-bind them to the matching Gladius communicationTemplate slots. Reynolds token names auto-map to our equivalents; anything custom shows up in a review screen during step 3.

• Can I keep my Reynolds DMS?

  Yes — Gladius is DMS-agnostic. The Reynolds DMS is the most common reason dealers say 'we can't switch CRM' — we explicitly designed Gladius so you don't have to. We integrate with the Reynolds DMS over the standard ADF + direct feeds, and your reps see one cockpit while the DMS keeps doing what it does in the background.

• What if my Reynolds contract isn't up yet?

  Run both. The $999 Gladius fee against a typical Reynolds seat block is usually still net-cheaper than waiting — and you start banking the rep productivity gain on day one instead of at renewal. Watch the non-renew notice window (Reynolds contracts usually require 90 days); we'll send you a calendar reminder on the day you sign with us so you don't miss it.

• How long until my reps are productive in Gladius?

  Same day. The Gladius cockpit was designed by a 20-year operator (Sales → F&I → GSM) and the muscle-memory paths — search a lead, log a call, write an appointment, send a text — are 1-3 keystrokes each. We run a 90-minute live training the morning of cutover, and our team is on the floor (literally or via screen-share) for the first three days.