This page is for tenants who run on Yelo, Tookan, or another Jungleworks vertical and want to move to BetterSuite. We want to be honest about what's automated and what isn't.
The shape of the move
Yelo is a per-vertical product family (Tookan for taxi/delivery, Yelo for marketplace, Hippo for messaging). BetterSuite is one platform with verticals you toggle on. So even ignoring the import question, you're collapsing what may be two or three Jungleworks accounts into a single BetterSuite tenant.
Because Jungleworks doesn't ship a database export and we don't (yet) have an importer that talks to their APIs, here's what actually moves over:
| Thing | What you can carry over | How |
|---|---|---|
| Drivers / agents | Whatever Tookan's export gives you | Manual re-onboarding into BetterSuite (phone verify, ID, payouts) |
| Vehicles | Whatever Tookan exports show | Manual entry |
| Catalog (products, categories) | Yelo's merchant export | Manual recreate / bulk add in BetterSuite (no automated catalog importer today) |
| Vendors / merchants | Yelo's merchant export | Manual re-onboarding |
| Customer list | Yelo lets you export customer phone numbers | Customers re-sign-in with OTP on their phone; you don't need to import them as a precondition |
| Order / trip history | Read-only, for your records | Export from Tookan / Yelo and keep alongside your accounting |
| Driver / vendor bank accounts | Nothing | Re-onboarded via Stripe Connect (security requirement) |
| Ratings | Nothing automated | Could be re-seeded manually if it matters to you |
| Hippo chat history | Nothing | Operational data; doesn't migrate |
If a Yelo / Tookan importer ships, this table will get noticeably shorter. We'll update this page when that happens.
A reasonable shape for the move
The platform doesn't enforce a particular cadence, so this is advisory:
- Stand BetterSuite up alongside Yelo. Finish sign-up, enable the verticals you currently run (taxi, shop, parking — toggle each one), connect Stripe, and aim for rough parity with how things are configured in Yelo. Don't over-fit — you'll improve from there.
- Decide your consolidation. If you run Tookan and Yelo separately today, you'll have one BetterSuite tenant for both. Pick the brand name that survives, decide whether operating hours and staff are shared across verticals, and think about how customer support routes across them.
- Brief your drivers and merchants. Both groups re-onboard themselves (identity, payouts). They'll move much faster if they know the switch is coming. Use whatever channel you currently use to reach them.
- Start with a small group. A handful of drivers and a couple of merchants. Run real trips, place real orders, refund a test order, verify a payout actually hits the right Stripe Connect account. Fix what surfaces.
- Cutover when the small group is happy. Invite everyone else. Stop accepting new orders in Yelo / Tookan — most tenants do this naturally over a day or two rather than at a hard switch, finishing any open Yelo orders in Yelo.
Where you'll find the migration runner
The runner is at Owner Dashboard → Migrations. Opening New migration today shows one provider — Legacy Ridy taxi platform — for operators on a different family of self-hosted MariaDB-backed taxi apps. Pick this only if it describes your current system; if you're on Yelo or Tookan, it does not.
The runner page (list and detail) is built and operational, with all the surrounding pieces you'd want — dry-run mode, run history with phase-level coverage, idempotent re-runs, watermark-based incremental sync. So when a Yelo importer ships, this is where it'll plug in.
Multi-vertical consolidation
This is the most useful work you can do while you wait for the importer.
- One tenant, multiple verticals. Decide which verticals you'll enable in BetterSuite. Each one shows up in the Ops Console with its own Overview / Dispatcher / Orders / Management sections — see Dashboard Tour for the layout.
- Pick the brand that survives. Most tenants pick the most-recognized of their Yelo / Tookan brands and rebrand the others to match.
- Operating hours can differ per vertical. Don't force them to align unless it's a deliberate choice.
- Staff and roles. Most tenants share the operator team across verticals; on Enterprise you can scope roles per vertical if you need to.
Catalog cleanup is worth doing during the move
If you're moving a shop catalog, the relaunch is a good opportunity to drop SKUs you haven't sold recently. Yelo exports cover everything including disabled / deleted items. Manually re-adding only what you actively sell is more work upfront but produces a cleaner customer experience day one.
What about Hippo (Yelo's chat)?
BetterSuite has its own in-app chat that's enabled by default. Hippo conversation history doesn't migrate. Most operators find that acceptable because chat is operational data — anyone in an active conversation is still reachable via phone for the bridge period.
What's next
- Sign Up — register the tenant and enable the verticals you need.
- Stripe Payments — Stripe Connect is what drivers and merchants re-onboard payouts through.
- Dashboard Tour — find Migrations and the rest of the owner dashboard.
- Migrating from Uber Fleet — same honest-status story for a different source.
