Skip to content
Not sure what you need yet?Scope your system

Who owns your data — and what happens if your provider disappears

"What if you go under?" is a fair question to ask any software provider. Here's what to check about data ownership, exit and continuity — before you commit.

4 min read
Person using a laptop with digital security icons representing data protection, payments, cloud storage and online privacy.

The short answer: you should own your data outright, be able to export it in a usable format at any time, and have a written exit and continuity plan — including protection if the provider disappears. These aren't paranoid questions; they're basic due diligence, and a good provider will have clear, confident answers.

The short version

  • You should own your data, exportable on demand, in a usable format.
  • Ask what happens to the software if the provider goes under.
  • Look for source-code escrow and a written exit process.
  • Vague or evasive answers here are a serious red flag.

Why does this matter?

Your business will come to run on this system. If you don't truly own your data, or you can't get it out, or the whole thing depends on a provider who might vanish, you've built your operation on someone else's foundation. The questions below protect you from being trapped or stranded.

It's easy to skip this at the start, when the relationship is new and everyone's optimistic. But ownership and exit are exactly the things you can't fix later. Once your operation is running on the system and your history lives inside it, your leverage is gone. The time to settle these questions is before you sign, while you still can.

What to check on data ownership

  • Do you own your data? — outright, not "licensed" back to you. Your customers, orders and records are yours; the arrangement should say so plainly.
  • Can you export it? — on demand, in a documented, usable format, not a locked or proprietary one you'd need the provider to unlock.
  • Is it accessible? — you can get to it whenever you need, without asking permission or waiting on a request.

If a provider can't clearly say "your data is yours and you can take it anytime," be cautious. Hesitation here often means the commercial model quietly depends on you not being able to leave.

For Australian businesses there's an extra layer: where does the data physically live? Data sovereignty — your data held onshore, under Australian rules — matters for compliance and for peace of mind. It's a fair thing to ask, and a good provider will answer it without flinching.

What happens if the provider disappears

  • Source-code escrow — the code held with a neutral third party, released to you if the provider fails, so you're not left with a system no one can maintain.
  • A written exit and transition process — agreed before you sign, so leaving (or being left) is orderly, not a crisis.
  • Continuity of the system — a clear picture of how the software keeps running if the relationship ends, so a provider's bad day doesn't become your operational emergency.

This is the scenario people most often forget to plan for, precisely because it's uncomfortable to raise. But "what if you're not around?" is a reasonable question to ask anyone you're about to build your operation on, and the answer tells you a lot about how the provider thinks.

What does "owning your data" actually mean day to day?

It's easy to nod at "you own your data" without picturing what it buys you. Concretely, it means that at any moment you could ask for a full copy of your customers, orders, invoices and history, and receive it in a format you or another provider could actually use — a spreadsheet, a standard database export, well-structured files — not a screenshot or a locked archive. It means if you decided tomorrow to move to a different system, your history could come with you rather than being held hostage. And it means the provider treats your records as your property that they look after, not as an asset of theirs that you happen to access.

A quick test: ask to see a sample export before you sign. A provider confident in your ownership will happily show you what a data extract looks like. One who stalls, or can only offer a proprietary format, is telling you something important about who really controls your operation's history.

A scenario worth planning for

Imagine your provider is a small outfit and, two years in, they wind up the business. If you own your data, hold a usable export, and have source-code escrow in place, this is an orderly problem: you take your data, you take the code, and you engage someone to keep the system running. If you have none of those, the same event is an operational emergency — your business is running on software no one can maintain, holding data you can't get out. Same event, wildly different outcome. The difference is entirely the questions you asked before you signed.

Why a good provider welcomes these questions

A confident, honest provider makes leaving possible — clear ownership, easy export, escrow, a real exit plan. Ironically, that's exactly why you won't need to leave: a provider secure enough to make exit easy is one that's confident in the value of staying. They're not relying on lock-in to keep you; they're relying on doing good work.

Providers who dodge these questions are the ones to worry about. Evasiveness about ownership or exit is rarely an oversight. It usually means the business model depends on the very thing you're trying to avoid — being stuck. No lock-in isn't just a nice policy; it's a signal about the whole relationship.

The honest first step

These are questions to ask any provider before you commit. A partner who answers them clearly and confidently — and builds ownership and exit into the arrangement from the start — is one you can trust with your operation.

Tell us what you run, and we'll show you what's possible.

One question to start

Let's find out what's actually slowing down your .

That’s the first thing we ask. Tap the word and answer it in your own terms.