Swap a ~9% per-booking take rate (6% booking fee + 2.9% + $0.30 processing) for a flat $23/mo + 2% subscription. This self-serve guide covers the 30-day post-termination export window, the wallet-to-Stripe payments switch, OTA re-linking across 13 direct channels, and parallel-run cutover — typically 5–7 business days. No concierge, no sales call.
From
To
WHY OPERATORS SWITCH
The common thread: operators pass the 6% fee to guests, see conversion drop, and start looking for a flat subscription. Here's what usually triggers the move.
$0/mo looks attractive until you do the math. On $20k/mo bookings, TripWorks takes ~$1,780/mo. EquipDash takes ~$423. That's ~$16k/year back in your pocket.
Operators report conversion drops when passing the fee to customers — particularly on premium bookings (multi-day, boat charters, VIP). EquipDash's 2% is operator-side, optional to pass through.
TripWorks has inventory-tracking checkboxes, but no serial/item-level tracking, no check-in/out flow, no maintenance logs. If rentals are a real revenue line, the fit breaks down quickly.
TripWorks ships a PWA (Progressive Web App) — a browser app installed to your home screen. For staff working in the field with poor signal, a native app is a different experience. EquipDash is live on Android; iOS pending Apple approval.
BEFORE YOU START
Do these three things first. They prevent the most common migration problems — especially around the 30-day data window and payment wallet.
STEP BY STEP
Each step assumes the previous one is complete. Run them sequentially, not in parallel.
TripWorks grants up to 30 days post-cancellation to export data before archive; additional exports are available on request. The "Import & Export" feature supports offline analysis; webhooks and API access are Enterprise-plan only. Pull everything while your account is still active.
Pull these, in this order:
TripWorks column headers don't match EquipDash import templates. Download EquipDash's templates (Settings → Import) and remap:
Keep original TripWorks CSVs untouched. You'll want them if anything looks off after import.
Import in this order: Products → Customers → Open bookings. Don't try to import historical bookings — EquipDash treats your switch date as day zero, with customer history imported as notes.
This is the trickiest step. TripWorks operates its own payments wallet (not Stripe passthrough), so saved customer cards can't transfer. You'll connect your own Stripe Connect account to EquipDash, and returning customers re-enter payment on their next booking.
For one week, take new bookings in EquipDash while TripWorks fulfils anything already booked there. Keep TripWorks read access open for the full 30 days as your reconciliation safety net.
AFTER MIGRATING
Predictable flat subscription, real rental depth, a native mobile app for your team, and your own Stripe merchant account.
HONEST WARNINGS
We'd rather tell you up front than have you discover it day three.
TripWorks grants up to 30 days to export data before archive; additional data on request. Don't rely on post-termination for waivers or gift card balances — pull everything before you cancel.
TripWorks uses a native payments wallet, not Stripe passthrough. Tokenized customer cards can't migrate to your new Stripe Connect account — returning customers re-enter payment on their first EquipDash booking.
Each of TripWorks' 13 direct OTA connections (Viator, Expedia, GetYourGuide, Klook, Musement, Tiquets, Civitatis, Tripster, Tourbase, EBG, Sightseeing Pass, Booking Radar, Google Things To Do) needs re-certification. Budget 1–2 weeks per priority OTA.
Outstanding TripWorks gift cards don't transfer automatically. Pull the liability report before cutover, then either honor them manually or issue equivalent EquipDash store credit to customers.
TripWorks' cart-recovery and engagement data may not export cleanly. For your top customers, document manually before cutover — otherwise those retention signals reset to zero on EquipDash.
We don't offer paid migration. This guide is what we'd tell you on a call. If you hit a block, email support — but we won't run the migration for you.
MIGRATION FAQ
Everything operators ask before pulling the trigger from TripWorks.
Contact Us5–7 business days for the data migration itself. Add OTA re-certification time — up to 2 weeks per priority OTA connection — if you run channel bookings. Start OTA paperwork in parallel with data export so the timelines overlap.
Export TripWorks data, connect your own Stripe, reconnect OTAs. Flat $23/mo + 2%, native mobile app, real rental depth. 21-day free trial, no sales call.
