Many operators leaving FareHarbor have two things to move: the bookings, and a website that was built on top of the booking tool. This guide covers both, plus the exports to take, the Treka import steps and how to keep selling during the week you switch.
Updated 8 min read
Book a demoStart free, 30 daysIf your public website is hosted by your current platform, switching booking tools also means switching websites, and the website is the part guests see. Decide that first. You have three options in Treka, and they are not exclusive: embed the booking widget in a site you already own, switch on the hosted booking site on your own domain, or have Treka's team build a site around your trips as an add-on.
| Your situation | What to do | Cost |
|---|---|---|
| You own a website (Squarespace, WordPress, Wix, hand-built) | Keep it; embed the Treka booking widget where the old booking buttons were | Included |
| Your website is hosted by your booking platform | Switch on the Treka hosted site and point your domain at it; the site scan has already imported your trips into it | Included |
| You want a site designed for your brand | Custom website build: designed with you, built by Treka, live on your domain | Quoted after a demo |
Before anything else, use your account's export tools to download the customer list, the item or product list, every upcoming booking with amount paid and balance due, and the payment and payout reports for the current and previous year. If your website is hosted by the platform, also save the text and photos from each page: the site scan reads trips, not your About page.
Do not close the old account before the domain moves
If your domain points at a site the old platform hosts, moving the DNS is the last step, after the Treka site is live and checked on a phone. Change the DNS first and guests land on nothing for the hours it takes to propagate.
Sign up with Google or Apple (30 days of Core free, no card). Under Website in the portal, point the site scan at your current booking site or your own website: it crawls the pages, extracts every trip it finds with its price, duration and description, and adds them as unpublished drafts. Trips it cannot fully read are flagged for review rather than guessed at.
Anything you exported from your old account, whether a spreadsheet, a PDF or a screenshot, can be dropped on the import page. The importer reads it and creates the trips it finds: a trip with a price, a duration and a location is published straight away, and anything missing one of those waits in the review list until you fill it in.
Paste or upload a CSV of your guests. The client importer recognises a header row (name, email, phone, notes, and common store exports) and maps the columns for you, so past guests are in the system before you send a single confirmation from it.
On each trip, set the deposit as a percentage or a fixed amount and decide whether the balance is charged automatically before the trip or collected on the day. Put your cancellation and refund wording in the company policies once and every booking carries it.
Paste the waiver you already use. It is sent with the confirmation and signed by every guest in a party, not only the person who paid, and the signed copies sit against the booking.
Connect your Stripe account so deposits and balances settle to you. Add your guides, set what each is paid per trip, and assign them to dates; the schedule and the payouts come from the same place.
Publish the trips you reviewed. Either embed the booking widget in the website you already have, or switch on the hosted booking site and point your domain at it. Both work from the same trips and the same calendar.
Nobody should switch a live operation in an afternoon. The pattern that works is one week where both systems are alive and each has a clear job.
Keep the old exports
Download your booking history, client list and payment reports before the old account closes, even the parts you will never import. Chargebacks and tax questions arrive months later and the export is the only copy you will have.
| Route | Who does the work | Typical time | Cost |
|---|---|---|---|
| Self-serve | You, with the site scan and the importers | An afternoon to a few days, depending on how many trips you review | Free |
| White-glove migration | The Treka Relations team moves trips, clients and upcoming bookings with you | About a week, scheduled around your season | $749 one-time on monthly plans, free on annual plans |
Either way the 30-day trial starts when you open the account, not when you go live, so most operators do the move inside the trial and decide at the end of it.
FAQ
Something else? Ask the people who build it.
You will leave it, so plan the replacement before you cancel. Treka's hosted site is built from the trips you import and runs on your own domain; the site scan has usually already brought the trips across by the time you look at it. Save your page text and photos first, since the scan reads trips rather than your About page.
Keep the same domain, point it at the new site, and keep the trip names the same. Treka writes a title, description and canonical address for every trip page and lists them in a sitemap, so search engines re-read the new pages at the old addresses' home. Expect a few weeks of settling either way.
Yes. Open Treka, import, review and publish while the old booking buttons keep working. The switch is the moment you replace those buttons or move the domain, and the cutover week below is how to do it without a gap.
Bookings that arrive from third parties come in as they do now, by email or by the partner's system, and you enter them in Treka so the manifest is complete. Treka's own channel, the Treka Marketplace, lists your live trips and sends travelers to them; you choose which trips appear.
No. You can keep the website you have and embed the Treka booking widget into it, or use the booking site Treka hosts on your own domain. If you want a site designed around your trips, our team builds custom sites, scoped and quoted on a demo call.
Every company starts with 30 days of Core, free. After that Core is $99 a month, or $79 a month billed yearly ($948). Pro is $399 a month, or $329 a month billed yearly ($3,948), and adds custom AI agents, SEO optimization and a named contact. A 3% booking fee is added at checkout and paid by the guest; Stripe's card processing (2.9% + 30¢) is billed at cost. No contract.
Yes. White-glove migration with the Treka Relations team is $749 one-time on monthly plans and free on annual plans. The team moves your trip catalog, your client list and your upcoming bookings, and walks your guides through the portal before the first departure runs on it.
30 days of Core free, no card required
Thirty minutes with someone who has done this migration before: what transfers, what you rebuild, and when to cut over so no booking is lost.
Book a demoStart free, 30 days See pricing