Moving off spreadsheets without losing a booking

The fear is legitimate — plan around it, don't dismiss it

Every operator who has run a fleet on spreadsheets and chat threads for a few years has the same worry about switching to real software: what if something gets lost? An open agreement disappears, an outstanding balance doesn’t carry over, a customer’s document expiry silently vanishes. That fear is reasonable, and the right response isn’t to promise it won’t happen — it’s to build a process that catches it before it can.

Step 1: export everything, even the messy parts

Start with a full export of vehicles, customers, currently open agreements, and outstanding invoices — from whatever you use today, spreadsheet or software. Don’t clean it up first. A messy export you can verify against is more useful than a tidy one you’ve already half-rewritten by hand, because you lose your ability to check it against the source.

Step 2: count before you trust

Before anything goes live, three numbers should match exactly between your old system and the new one: the number of vehicles, the number of active customers, and the total outstanding balance across open invoices. These three counts catch the overwhelming majority of migration problems on their own — a missing agreement almost always shows up as a mismatch in one of these three numbers.

• Vehicle count: does every car you actually own appear, with no duplicates?
• Customer count: do currently active customers all carry over, without merging two people into one record?
• Outstanding balance total: does the sum of unpaid invoices match, to the cent, before and after?

Step 3: rehearse before you commit

The safest way to do this is in a private rehearsal environment that isn’t visible to your customers or staff yet — import the data there first, run the three counts above, fix any mismatches, and only then treat that environment as the real one. This turns migration from a single risky leap into a checked, reversible step.

Step 4: keep the old system reachable, just in case

Even after go-live, don’t delete access to your old system immediately. Keep it in read-only mode for a transition window — a few weeks is usually enough — purely as a safety net. If something turns up that the counts didn’t catch, you can still look it up.

Step 5: check the small stuff a count won't catch

Counts catch missing records, but not necessarily details within a record — a mistyped phone number, a swapped pickup and return date. Spot-check a handful of records by hand, focused on ones with unusual data (a very long rental, a customer with multiple vehicles, an agreement with a dispute attached) since edge cases are where formatting assumptions tend to break.

This is the exact process behind Lanevo’s migration flow — rehearsal first, counts checked before anything goes live, and your old system kept reachable during the transition. If you’re planning a move, it’s worth reading regardless of which system you land on.