Data Ownership and Export: Questions to Ask Before You Sign
Owning your data and being able to leave with it are not the same question.
Almost every booking platform's terms will tell you that you own your data. Most of them mean it. And it is close to irrelevant, because ownership is rarely what traps operators — portability is.
A contract can affirm the data is yours and still leave you unable to extract it in any form that would let you rebuild elsewhere. That gap is what to check before signing, and it takes about twenty minutes.
What the contract actually says
Three clauses are worth finding, and they are usually in different sections of the terms.
- Ownership. Look for language confirming you retain ownership of your customer and booking data. Be wary of anything framing your access as a licence granted by the platform.
- Export rights. Separate, and the one that matters. Does the agreement commit them to providing your data in a usable format, on request, without charge?
- Post-termination. How long after you cancel can you still retrieve anything? Some retention windows are short, and they start the day you leave — when you are least likely to be thinking about it.
If the terms affirm ownership but say nothing about export, that is not a contradiction. It is the gap, and it is worth asking about in writing before you sign rather than discovering later.
What a full export should contain
Your business lives in seven categories of data. Here is what a typical export covers, with indicative rebuild times for what it does not:
| Category | Usually exported? | Rebuild |
|---|---|---|
| Bookings, past and future | Yes | — |
| Customer records and contacts | Yes | — |
| Products and pricing config | No | ~6h |
| Schedules and availability rules | No | ~3h |
| Payment history | No | ~4h |
| Guest communications | No | ~2h |
| Reviews and feedback | No | ~1h |
Two categories of seven — about 29% of what you would need. Add roughly sixteen hours rebuilding the rest, plus re-entering the bookings that did not transfer cleanly, and leaving a platform with a "full export" runs to around twenty-two hours of your time.
That is the number to have in mind when a vendor says export is supported. The question is not whether it exists — it is which of those seven rows it actually covers.
Lock-in patterns
Rarely malicious. Mostly the accumulated result of nobody having a reason to make leaving easy.
- Exports that are documents, not data. A PDF or a formatted report is not an export. You want CSV or similar — something another system can read.
- Marketplace connections in their name. If your Viator or GetYourGuide relationship sits under the platform's account rather than yours, leaving means renegotiating rather than reconnecting.
- Merchant of record. If the platform is legally the seller for your transactions, your payment history, chargeback record and processing relationship are all theirs — worth understanding before you sign.
- Minimum terms and notice periods, which convert a decision to leave into a decision to leave in nine months.
- Export fees. Uncommon and worth asking about explicitly, because the answer is revealing either way.
- Short post-termination retention, which turns a delayed migration into a permanent loss.
None of these should necessarily stop you signing. They should all be known quantities rather than discoveries.
Data protection when you move
Moving guest records between systems is a data protection matter, and the specifics depend on your jurisdiction and your circumstances. This is not legal advice — if you hold significant volumes of personal data, get advice from someone qualified in your market.
What is worth having on your radar as practical considerations:
- Where data is stored and processed, by both the old platform and the new one, since cross-border transfer can carry its own requirements.
- What agreements exist between you and each platform about how they handle data on your behalf.
- What you actually need to move. Moving only what has a purpose is simpler to justify than moving everything by default — and is less work.
- What happens to the old copy after you leave, and whether deletion can be confirmed.
- Consent for marketing, which is a narrower question than consent for delivering a booking, and does not automatically travel with the record.
That last point catches people. A guest who gave you their email to receive a booking confirmation has not necessarily agreed to marketing, and importing them into a new system does not change what they agreed to.
Test the export during the trial
The single most useful thing in this article, and almost nobody does it.
During a trial, everyone tests whether their data goes in. The test that matters two years later is whether it comes out — and you can run it in ten minutes while you still have no commitment at all.
- Build a couple of products and enter some test bookings, including one with a deposit paid and a balance outstanding.
- Run the export. Find it yourself rather than asking support to do it for you — if it needs a support ticket now, it will need one then.
- Open the file. Is it structured data? Are the fields labelled? Is payment status there?
- Check what is missing against the seven categories above.
- Ask about anything absent, in writing, before your trial ends.
Getting the most from a trial covers what else to test in the time available. This one belongs on the list precisely because it feels premature — testing the exit before you have entered is exactly when you have the leverage to ask.
A ten-question checklist
Send these to any vendor on your shortlist. Written answers, compared side by side.
- Do I retain ownership of my customer and booking data?
- Can I export it myself, without asking support?
- In what format — is it structured data rather than a document?
- Which of the seven categories above does the export include?
- Does the export contain payment status, deposits and balances?
- Is there any charge for exporting my data?
- How long after cancelling can I still retrieve it?
- Are my marketplace connections held in my name or yours?
- Who is merchant of record for payments taken through the platform?
- Is there a minimum term, and what notice do I need to give?
How Travelity answers these
Fairly, since this page argues you should ask: your data is yours, and the practical test is one you can run yourself during a 21-day trial that needs no card. Build a product, enter a booking with a deposit, export it, and see what comes out — before you have committed anything.
For anything on the checklist that matters to you, ask us in writing during the trial. A vendor unwilling to answer these in writing has told you something useful.
Frequently asked questions
Who owns your data in booking software?
In most agreements you do, and the platform processes it on your behalf. But ownership and portability are separate questions — a contract can affirm that the data is yours while offering no practical way to extract it in a usable form, which is the situation worth checking for.
What should a full data export include?
Bookings past and future with every field, customer records with contact details, your product and pricing configuration, schedules and availability rules, payment history showing what was paid and what is owed, guest communications, and any reviews collected. Most exports provide only the first two.
How do I move existing bookings into new booking software without losing data?
Export everything before cancelling anything, scope the move to bookings that have not yet travelled, and run both systems in parallel until the last of them has been and gone. Check that payment status came across correctly, because that is the field most often lost and the hardest to reconstruct.
What are common lock-in patterns in booking platforms?
Exports delivered as PDFs or reports rather than structured data, marketplace connections held in the platform name rather than yours, the platform acting as merchant of record for your payments, minimum contract terms, charges for extracting your own data, and short retention windows after cancellation.
Should I test data export during a free trial?
Yes, and almost nobody does. Everyone tests whether data goes in; the test that matters later is whether it comes out. Run an export during the trial, open the file, and check whether you could actually rebuild your business from it before you commit anything.
Bottom line
Stop asking who owns the data — the answer is almost always you, and it almost never helps. Ask instead which of the seven categories an export actually covers, because a "full export" delivering bookings and contacts alone leaves you rebuilding the other five.
Then run the export during your trial, while you still have every bit of leverage and nothing at stake. Ten minutes now is worth considerably more than the twenty-two hours you would otherwise spend finding out the hard way.
Related guides
- Switching booking software without losing your data
- How to choose tour booking software: a scoring framework
- How to get the most from a booking software free trial
- Best tour booking software in 2026: a buyer's guide
- From a shared calendar and inbox to booking software
- Moving from spreadsheets to tour booking software
See Travelity in action. Book a Personalized Demo.
30 minutes that can completely change the way you run your travel business. See how Travelity can help you work smarter, sell more, and operate with less stress.