This page is for taxi operators who run on Uber Fleet (sometimes called "Local Cab" by Uber's white-label team) and want to move to BetterSuite. We want to be upfront about what the platform automates and where you'll still be doing real work.
What that means in practice
Because Uber controls the data and the relationship with your drivers and riders, you can't lift either side over wholesale. Realistically, the move looks like this:
| Thing | What you can carry over | How |
|---|---|---|
| Driver list (name, phone, license) | Whatever Uber Fleet lets you export | Manual re-onboarding into BetterSuite |
| Vehicles | Whatever Uber Fleet exports show | Manual entry, or batched if you have an export |
| Trip history | Read-only, for your own records | Keep the Uber Fleet account open through the dispute window; export from Uber's UI for tax/accounting |
| Customer / passenger list | Nothing | Uber doesn't expose rider contact details to fleets |
| Driver bank accounts | Nothing | Drivers re-onboard payouts via Stripe Connect — a security requirement, not a BetterSuite limitation |
| Ratings | Nothing | Uber treats these as proprietary |
There is genuinely no shortcut here — the value you carry over is mostly the relationships with your drivers, not the system records.
A reasonable shape for the move
We can't tell you to follow a 14-day plan because the platform doesn't enforce one. What we've seen work, in rough order:
- Stand BetterSuite up alongside Uber Fleet. Finish sign-up, connect Stripe, and configure your fleet to roughly match what you have in Uber today — same service classes, similar pricing. Get parity at cutover, then improve from there.
- Brief your drivers before you invite anyone. Drivers re-onboard themselves into BetterSuite (phone verify, ID, Stripe Connect for payouts). They complete the flow much faster when they know it's coming. Use whatever channel you already use to reach them — WhatsApp, Telegram, in-person, your existing app's announcements.
- Start with a small group. Five to ten drivers who you trust to give honest feedback. Run real trips. Fix what's broken.
- Cutover when the small group is happy. Invite the rest. Stop accepting new dispatches in Uber Fleet — most operators wind down naturally over a day or two rather than at a hard switch.
- Keep Uber Fleet open for the dispute window. Refunds, complaints, and chargebacks from Uber-era trips have to be handled in Uber's tooling. Most tenants keep the account live for ~60 days after the last Uber trip.
Don't over-engineer the schedule. The bigger your fleet, the more value there is in a phased rollout; for a 30-driver shop, "everyone next Monday" is fine.
Where you'll find the migration runner
The runner lives at Owner Dashboard → Migrations. If Uber Fleet were a supported source, this is where you'd configure it. Today, opening New migration shows a single provider option — Legacy Ridy taxi platform — which is for operators leaving a different family of self-hosted platforms. If your current system happens to be one of those, see Migrating from a Legacy Ridy Taxi Platform for the full playbook. If you're on Uber Fleet, it does not apply.
We'll add this page to the runner's provider list when an Uber Fleet importer ships. Until then, the page is here so you can plan the move with eyes open.
What about trip history for tax / accounting?
Export trip CSVs from Uber Fleet's own reporting UI and keep them in your accounting system. BetterSuite doesn't currently ingest those as a queryable archive — for a tax audit you'd reference the Uber-side records, and for everything from cutover day onward you'd reference BetterSuite. Two systems for one tax year, then one from year two onward. Not elegant, but accurate.
Practical friction points
- Phone number formats. When you re-onboard drivers, BetterSuite expects international format (
+44…). If your Uber Fleet export has national-format numbers, plan to clean those before you bulk-message drivers about the switch. - Branded apps. If your drivers currently use the generic Uber Fleet driver app, decide before cutover whether you want them on BetterSuite's default driver app (
<your-slug>-drive.bettersuite.io, web-installable PWA) or your own branded iOS/Android build. Branded apps are a Pro+ add-on — see Plans & Billing. - Payouts. Drivers connect Stripe Connect themselves on first login. There's a small window where they'll have completed trips in BetterSuite but haven't yet connected payouts — Stripe holds those balances until they finish onboarding. Brief drivers to complete Stripe setup before their first shift.
What's next
- Sign Up — register the tenant.
- Stripe Payments — Stripe Connect is what drivers re-onboard payouts through.
- Dashboard Tour — the rest of the owner dashboard, including where Migrations lives.
- Migrating from Yelo — same honest-status story for a different source.
