Switch from DriveCentric in 12 minutes.

1. Step 01

   Export from DriveCentric

   Open DriveCentric, drop into Settings, run the Data Export. Pull leads, customers, and the activity timeline — no date range, no source filter, all rooftops if you have more than one. If you've been heavy on the video-message feature, the URLs port over as clickable links on the Gladius lead record.

   Path: Settings → Data Export → Customer + Lead CSV · Video-message URLs preserved as clickable links on each lead.

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 DriveCentric 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 (DriveCentric + Gladius both live)

   New leads dual-write to both systems through a feature-flagged adapter. Your reps see Gladius on their cockpit, DriveCentric stays read-only as a safety net, and your manager team gets the full Gladius multi-rooftop reporting alongside the DriveCentric dashboards.

   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 DriveCentric goes idle. Reps see no UI change because they've been on the Gladius cockpit for two weeks already. Your DriveCentric 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 DriveCentric: Settings → Data Export → Customer + Lead CSV (the standard DriveCentric export). DriveCentric ships a CSV with leads, customers, vehicles, the video-message history, and the activity timeline. Our importer reads every column verbatim — including the DriveCentric video links — and projects them into Gladius without a schema reshape. Video links stay clickable; the underlying video assets keep playing from their original URLs.

• 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 video messages?

  No. DriveCentric video URLs come out in the export as clickable links and we attach them to the matching lead activity in Gladius. The underlying video assets keep playing from their original URLs as long as your DriveCentric account is live. If you want to mirror them to Gladius storage for long-term continuity, we have a separate playbook for that — it's a one-time job we run for you.

• 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. DriveCentric token names auto-map to our equivalents; anything custom shows up in a review screen during step 3.

• Can I run both systems in parallel during the transition?

  Yes — and we recommend it for the first two weeks. New leads dual-write to both systems through a feature-flagged adapter, your reps see Gladius on their cockpit, and DriveCentric stays read-only as a safety net. When you're confident, we flip the flag and DriveCentric goes idle.

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

  Run both. Most DriveCentric contracts are annual, and the $999 Gladius fee against a typical DriveCentric block plus add-ons is usually still net-cheaper than waiting. We'll send you a calendar reminder for the non-renewal window so you don't miss the cancellation deadline.

• 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.