Migration guide
Switching platforms without breaking a single live booking
The reason operators stay on software they have outgrown is fear of the switch — live duties, open invoices, drivers mid-trip. This is how a migration is run so none of that is at risk.
How a switch actually runs
Zero downtime to live bookings is the standard, not the exception. City-by-city cutover is available for multi-city operators.
- Week 0 — discovery: current tariffs, clients, vendors, vehicles, duty history and invoice formats are mapped.
- Week 1 — data migration: masters and open duties are imported; billing formats are matched line for line.
- Week 2 — parallel run: both systems live, invoices reconciled side by side until they match to the rupee.
- Week 3 — cutover: dispatch, duty slips and billing move fully to Fleetoz; the old system becomes read-only.
- Ongoing — a named onboarding owner stays with you through the first two billing cycles.
What gets migrated
| Data | Handling |
|---|---|
| Clients and contracts | Imported with billing entities, cost centres and contacts |
| Tariffs | Rebuilt rule by rule and validated against past invoices |
| Vendors and attached vehicles | Imported with compliance documents and payout terms |
| Vehicles and drivers | Imported with registration, permit and licence validity |
| Open duties | Carried over live so nothing in progress is lost |
| Duty and invoice history | Imported for reporting; old system kept read-only for audit |
How risk is controlled
- Parallel run until invoices reconcile to the rupee against the old system
- City-by-city cutover for multi-city operators, never a big-bang switch
- Driver and dispatcher training before cutover, not after
- A named onboarding owner through the first two billing cycles
- Rollback plan documented before go-live, though it is rarely used
What Fleetoz gives you, in one platform
- AI-assisted allotment across owned fleet, attached vehicles and a 450+ supplier network
- GPS-verified digital duty slips — no paper, no disputed hours or kilometres
- GST-compliant e-invoicing with per-cost-centre, per-project and per-entity splits
- White-label corporate booking portal so your clients book you directly
- Employee app (CARVA) so your client's staff self-book inside policy
- Live P&L by client, vehicle, driver, city and route — not month-end guesswork
- MIS, dashboards and dimension-wise spend analysis, including CO₂ per trip
- Trip ratings and NPS captured after every duty, broken down by supplier
- WhatsApp automation: confirmation, driver details, on-the-way, closure, feedback
- Native integrations with SAP, Oracle, Workday, Concur, Darwinbox and SSO
A note on fairness
Fleetoz is not affiliated with, endorsed by or partnered with any other vendor named on this page. Product names and trademarks belong to their respective owners. Feature notes about other vendors are based on publicly available information and buyer feedback at the time of writing — always confirm current capability directly with the vendor before you sign.
Frequently asked questions
How long does migration take?+
Two to three weeks per city end to end, including parallel billing.
Will bookings be interrupted?+
No. Open duties are carried over live and the parallel run means both systems work until you sign off.
Who does the data work?+
The Fleetoz onboarding team does the mapping and import; your team validates tariffs and invoice formats.
What does migration cost?+
Migration and parallel running are included in onboarding — there is no separate implementation fee.
Can we migrate one client first?+
Yes. Many operators start with one corporate account, prove the billing, then move the rest.