Your business should own the records the software holds: every customer, job and booking, with its history. Whether you do in practice comes down to what the contract says and where those records live, so check both before any work starts.
This article is about the data only. Who owns the software itself is a separate question for the contract, with its own answer.
What counts as your data?
More than the customer list. Everything your business puts into the software, and everything the software records about your customers and your work:
- names, phone numbers, emails and postal addresses
- every job, booking, quote or invoice, with its history
- messages and notes, and the files attached to them
- your prices and the rules and settings that hold how you work
- the record of who changed what, and when, which matters most in a dispute
If any of it would be painful to rebuild by hand, it belongs on the list.
Why is "it's yours" not enough?
Because records you cannot reach are yours in name only. Three things turn ownership into something you can use.
Where it lives. Records kept in accounts in your business's name are within your reach. Records in an account in the developer's name depend on the developer.
How you get it out. On request, at any time, and not only when you leave. In a file another tool can open, such as a spreadsheet file, with every record and every field. A screenshot or a PDF report is a picture of your data, not a copy of it.
What happens at the end. Returned to you, deleted from the developer's systems, and confirmed in writing with a date.
Where should the records live?
As close to you as possible. Where a system can store records in a tool or an account the business already owns, that is the safer default, because the records stay where they are whoever looks after the software.
That is how we build. Your data is yours, and it stays in your own systems. Access is limited to what each part of the system needs, and nothing is resold, pooled or shared across clients.
What does Australian law expect?
Two things are worth knowing, and neither depends on who built the software.
If the Privacy Act covers your business (the OAIC sets out who it covers), Australian Privacy Principle 10 asks you to take reasonable steps to keep the personal information you collect accurate, up to date and complete. That is hard to do with records you cannot see or correct.
The ATO says you need to keep most records for five years, and that you need to be able to reconstruct your original data if your record-keeping system changes. Moving away from a system is a change. So the way out has to leave you with records you can still read.
Who else handles it?
Usually more than one company. A developer uses outside services to run the software: hosting, sending email, sending texts, storing files. Each of those holds some of your data.
Ask for the list: which services, what each one holds, and which country it is stored in. Ask to be told before the list changes.
What should the contract say?
Six lines cover most of it.
- The business owns its data, including what the software records about its customers and work.
- The developer will give a full export on request, at any time, in a named file format, within a set number of days.
- Where the data is stored, and which outside services handle it.
- What happens at the end: a final export, then deletion, confirmed in writing.
- Who tells you, and how fast, if something goes wrong with your data.
- The developer will not use your data for anything except running your software.
If a supplier's standard terms already say all six, good. Read them before you sign, not after.
Where does it go wrong?
- Accounts in the developer's name. The hosting, the email sending service, the domain. Each one is a door only they can open.
- An export that only exists on the way out. Ask for one in the first month, and open it.
- A format nobody can open. A file that needs the old system to read it is no help once the old system is gone.
- Forgetting the backups. Records deleted from the live system can sit in backups until they expire. Ask how long that takes.
- Assuming it is covered. The day you want to leave is the worst day to read the data clause for the first time. List what you pay for before you add a tool includes the step to take before any tool goes.
In short
- Your business should own every record the software holds about your customers and your work.
- Ownership only counts if you can reach the records, export them at any time and read the file.
- Keep records in accounts in the business's name wherever you can.
- Australian privacy and tax rules expect you to keep accurate records you can still read after a system changes.
- Put the export, the storage and the ending in the contract.
One step for this week
Pick the system that holds most of your customer records. Export everything from it today. Open the file, and check that every customer, job and payment is there, with its dates.
Whatever is missing goes on the list for your next conversation with that supplier. In any custom software we build, your records stay yours and stay in your own systems.

