"Days, not weeks" sounds like a marketing line until you've sat through an actual legacy migration. Here's what the days are actually spent on.

Day 1 to 2: pulling the export

We ask for an export from your current system, usually Caren or something comparable. The ETL tool maps your vehicles, categories, active bookings, and customer records into NetRent's schema. Most of the friction lives in the mismatches: your categories aren't quite our categories, a vehicle has two IDs in two systems, that kind of thing. That's where the actual engineering time goes, not in a slow data transfer.

Day 3 to 4: reconciliation

Someone on your team and someone on ours sit down with the migrated data side by side against your current system. Fleet counts should match. Open bookings should match. Anything that doesn't gets fixed before anyone sees a live rate proposal, because a pricing model trained on wrong availability data is worse than no pricing model at all.

Day 5 onward: proposals go live, staff approve

Once the reconciled data checks out, staff start seeing pricing proposals inside NetRent for approval. Nothing goes live automatically. You're watching real proposals against your real fleet from day one, which is a different experience than watching a sales demo.

The whole point of building the migration tool before the rest of the product was that switching cost is the actual barrier keeping most rental companies on software they don't like. If it still took six weeks and a consultant, none of the rest of this would matter.