Migrate from OrbisX

This guide is honest about what imports directly from OrbisX and what you'll need to rebuild, so nothing catches you by surprise.

Before you start

You'll need:

• OrbisX admin account (owner-level access), to run a customer export
• Your SalesThumb shop already created and the onboarding wizard completed
• 2-3 uninterrupted hours
• A list of any custom service-tier names you'll want to keep

Step 1 — Export customers from OrbisX

In OrbisX, run a customer export (with vehicle records) to CSV. Save it somewhere you can find it.

OrbisX isn't a preset option in SalesThumb's importer today, so save the file as a standard CSV — the importer's generic column-header matching (name, email, phone, address, vehicle year/make/model, VIN, notes, etc.) picks up most standard OrbisX export columns without any special handling.

Step 2 — Import customers + vehicles

In SalesThumb: Customers → Import. Upload your customer CSV (up to 5,000 rows per file). Since OrbisX isn't a named platform in the source dropdown, pick "Other (CSV)."

SalesThumb guesses your column mapping from the headers and shows you a "Map your columns" step to review and correct it, then a 5-row preview before you confirm. At that point you also choose how duplicates are handled: skip, update existing records with new non-empty fields, or always create new — there's no separate post-import "detect duplicates" tool, so pick the right dedupe strategy up front.

Step 3 — Service catalog setup

There's no service-catalog CSV importer — OrbisX's flat-price services need to be rebuilt by hand in SalesThumb's good/better/best tier model. The recommended path:

1. List your top-20 highest-frequency services from OrbisX.
2. Recreate them in SalesThumb's service builder as 3-tier packages (good/better/best) where it makes sense.
3. Skip the long tail of one-off services until a customer actually needs one — you can always add more later.

Start with the services you sell every week; add the rest as customers ask for them.

Step 4 — Invoice and photo history

SalesThumb's importer doesn't bring over invoice/RO history or photo galleries — it's customer + vehicle records only. Plan for this instead of expecting it:

• Invoices: keep OrbisX accessible read-only (see Step 6) so staff can look up old invoice totals and warranty-adjacent details without cancelling early.
• Photos: old install photos stay in OrbisX for lookup; new jobs in SalesThumb start their own photo gallery going forward.

If you have questions about your specific dataset, reach out to hello@salesthumb.com before you commit to a cutover date.

Step 5 — Validation

Before you cancel OrbisX, validate:

• Customer count matches between OrbisX and SalesThumb (within 1-2% acceptable due to dedup).
• Top 50 customers by lifetime revenue have correct vehicle history in SalesThumb (spot-check).
• Vehicle year/make/model/VIN look right on a sample of records — CSV header-guessing is generally reliable but worth a spot-check.

If anything looks off, contact hello@salesthumb.com.

Step 6 — Run both systems in parallel for 14 days

We recommend running OrbisX and SalesThumb in parallel for 14 days:

• New work goes into SalesThumb only.
• OrbisX stays available read-only for historical lookups.
• After 14 days of confident operation in SalesThumb, cancel OrbisX.

Once your team goes a few days without opening OrbisX, that's the signal to cancel.

What about active OrbisX subscriptions?

OrbisX's pricing page lists no contracts or commitments, so you can usually cancel once your team has moved over. If your own agreement has different terms, check them first — and switch active operations to SalesThumb right away either way. Creating your SalesThumb account is free and takes no credit card, so you can get set up while OrbisX is still running and pick a paid plan when you're ready to move day-to-day work across.