A plain account of moving an activity or tour operation off Peek Pro: what you export, what Treka imports on its own, what you set up by hand, and the week where both systems run side by side. No comparison, just the move.
Updated 7 min read
Book a demoStart free, 30 daysOperators on Peek Pro usually have a catalogue of activities with time slots, a few years of customer records, and a run of future bookings with deposits already taken. Most of that comes with you; some of it should stay where it is until it runs out.
| What you have | Comes to Treka | How |
|---|---|---|
| Activities and tours (names, descriptions, prices, durations) | Yes | The site scan reads them off your public booking pages, or drop your product export on the import page |
| Time slots and seasonal availability | Rebuilt | Treka trips carry their own dates, start times and capacity; set them once per trip, with blackouts for the days you will not run |
| Customers and their history | Yes | Upload the customer CSV; past bookings travel as notes on the client record |
| Future bookings with deposits | Partly | Recreate departures in Treka; deposits already taken stay on the platform that took them |
| Waiver wording | Yes | Paste your text; Treka sends it with the confirmation and collects a signature from every guest |
| Gift cards and store credit | No | Treka does not read another platform's ledger; keep a list of outstanding balances and honour them from it |
| Reviews | Indirectly | Your Google and Tripadvisor reviews follow your business, not the booking tool; Treka shows them on your site |
Use your account's export tools to pull three things while you still have full access: the activity or product list with prices and descriptions, the customer list with emails and phone numbers, and every upcoming booking with the amount paid so far and the balance due. Save the payment and payout reports for the current and previous tax year as well.
If your activities are only described on your public website, you do not need a product export at all: the Treka site scan reads trips from the pages your guests already see.
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.
They see a new booking page and new confirmation emails with your name and branding on them. If you embed the widget in your existing website, the address they visit does not change. Tell returning guests once, in the next email you send, and that is usually the end of it.
Either recreate them in Treka so the whole season is in one calendar, or leave them on Peek Pro and let them run out while every new booking goes to Treka. Deposits already charged stay where they were charged; you collect the balance wherever the booking lives. White-glove migration includes recreating upcoming bookings for you.
Trips, prices and descriptions import automatically from the site scan or your export. Dates, start times and capacity are set per trip in Treka, which takes a few minutes per trip and is the moment most operators tidy up a schedule that had grown by accretion.
No. Export the list of outstanding cards and balances from your old account and honour them from that list until they are used or expire. New gift cards are sold through your Treka site from day one.
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