Checkfront accounts tend to hold more than tours: rental gear, a cabin or two, and bundles that combine them. This guide covers how each of those lands in Treka, what you export first, and how to move without a gap in bookings.
Updated 7 min read
Book a demoStart free, 30 daysThe first thing to decide is which of your items are guided trips and which are things you hand over. Treka keeps them apart on purpose: a guided trip has guides, a waiver and a manifest; a rental has a return date; merchandise ships or is collected. Sorting your item list into those three piles before you import saves the most time later.
| Your item | Where it lives in Treka | Notes |
|---|---|---|
| Guided tours, lessons, charters | Trips | Dates, start times, capacity, deposits, waivers and guide assignment |
| Gear rental (kayaks, bikes, skis) | Gear rental | Rented by the day from your site, with its own page and checkout |
| Merchandise and consumables | Shop | Sold from your site; collected or shipped |
| Lodging and campsites | A trip with overnight dates, or stays off Treka | Treka is built for guided days, not room inventory; a guided multi-day with lodging included works well, a stand-alone room rate usually belongs with a lodging system |
| Bundles (tour + rental) | A trip with the gear included in its price, or a pricing tier | Guests pick the tier at checkout instead of assembling a bundle |
From your account's export tools, take the item list with prices and descriptions, the customer list, and every upcoming booking with the amounts paid. Pull the financial reports for this year and last while you still can. If your items are described on your public website, the Treka site scan can read the trips directly from there and you may not need the item export at all.
Availability rules do not travel
Capacity rules, lead times and date-based pricing are rebuilt in Treka per trip. Write yours down before you start: the number of seats per departure, how far ahead a guest may book, and which dates you never run.
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.
Once the trips are in, switch on gear rental if you hire equipment. Each item gets a daily price and a stock count, and your site gains a rental page with its own checkout. Merchandise goes in the shop the same way. Both share the client list with your trips, so a guest who rented a kayak in June is the same record as the one who books a tour in July.
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.
Treka runs the guided trips, the gear rental and the shop. It does not manage room or pitch inventory on its own, so most operators keep a lodging system for the campsite and link the two from their website. A guided multi-day that includes a night in your cabin works fine as a single trip with the lodging in its price.
As pricing tiers on the trip. A half-day paddle with gear included and the same paddle for guests who bring their own are two tiers of one trip, and the guest picks at checkout. Capacity is counted once, for the departure.
No, but it does not come across as bookings. Export it and keep it; upload your client list so every past guest exists in Treka with their contact details and whatever notes you want on the record.
Guides see the trips they are assigned to: the manifest, waivers and their pay for the day. Rentals and shop orders are on the company side of the portal, not the guide's day sheet.
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