No sugar-coating. The stuff that's identical, the stuff that's different, all on one page — so you can plan for the differences before you flip the switch.
Products + activities
— Your FareHarbor activity + timeslot configuration imports as TripStub products and schedules. No rebuild.Availability calendars
— Existing future availability carries into TripStub; past bookings import as read-only history.Customer database
— Contact records, booking history, marketing-consent flags — all imported with FareHarbor IDs preserved as external references.Payment provider
— If you're on Stripe via FareHarbor, you keep the same Stripe account — just reconnect it to TripStub. No new gateway onboarding.Reviews
— FareHarbor does not enforce review lock-in. Any ratings you've published stay on the destination platforms (Viator, TripAdvisor).No booking fee passed to customer
— FareHarbor's 6% service fee (typically on top of your price, charged to the customer) disappears. Your posted price is the price.Payment processing model
— FareHarbor acts as merchant-of-record. TripStub routes through your own Stripe account — funds land with you directly, clearer reconciliation.Booking-engine look
— FareHarbor's signature widget is replaced by TripStub's own-site checkout. Different aesthetic; we have a mini-migration guide for rebuilding your booking button.Channel distribution model
— FareHarbor's distribution network through Booking.com becomes direct Viator/Klook/GetYourGuide via TripStub. You pick the channels; we handle the sync.If you have a CSV export from FareHarbor, a morning coffee, and an hour of uninterrupted afternoon, you'll be taking bookings on TripStub by tomorrow morning.
FareHarbor's full data export is a support-ticket request — submit that first thing in the morning. Turnaround is 4–8 hours. Create your TripStub workspace while you wait.
Upload the FareHarbor export. Map activities → products, price types → rate plans, time slots → schedules. TripStub's importer does 80%+ automatically; the remaining 20% is your call on product structure cleanup.
Reconnect your Stripe account to TripStub (takes 5 minutes; Stripe Connect flow). Reconnect Viator, Klook, GetYourGuide via TripStub adapters. Test the full flow on a sandbox booking.
Update your own-site booking button to point at TripStub's checkout. Run a parallel week if you want; most operators just cut over — FareHarbor historical bookings stay accessible via read-only records in TripStub.
Does cancelling FareHarbor require a formal process?
Yes — they ask for a written notice 30 days ahead. File it when you create your TripStub workspace, so you're not paying for overlap beyond your parallel-run week.
What happens to the 6% service fee my customers were paying?
It disappears. Your posted price becomes the final price the customer pays. If you want to add a processing fee, TripStub supports it as a line item — but it's optional and rarely used by operators who have the option.
FareHarbor integrated with my resource planning. Does TripStub?
Yes — TripStub has native resource pools (kayaks, bikes, guides, equipment) that are shared across products and schedules. Configuration is different from FareHarbor's model; we have a mapping guide.
I use FareHarbor's Dashboard reports. What's the equivalent?
TripStub's Reports page covers the top 8 FareHarbor report types (revenue by product, by date, by channel, refunds, etc.). For anything custom, all raw data is CSV-exportable or accessible via the REST API.
My staff is trained on FareHarbor. How long is the learning curve?
Most operators report a 2–3 day adjustment period. The core booking actions (find a booking, check in a guest, reschedule, refund) are 2–3 clicks in both. The config screens are where the curve lives.