What PoolBoss Says
You own it - your customer list, your pools, your visit and chemical history, your invoices. But ownership only counts if the software will hand it back as a file. Ask for a self-serve CSV export of every record type before you sign, not on the day you want to leave.
Every pool service software contract says you own your data. Almost none of them say what that means in practice: which records you can actually pull out, in what format, whether you can run the export yourself or have to email support and wait, and what happens to four years of chemical readings the week after you cancel.
That gap is where operators get stuck. The question sounds like a legal one, so it gets skipped during a demo and asked for the first time on the day someone wants to leave - which is the one day the answer can no longer be changed. It is a five-minute question with a concrete answer, and it belongs on the way in.
At a glance
Key takeaways
- You own your records in any mainstream pool service platform - the real question is whether the software will hand them back as a file.
- Ask about record types by name. A pool route generates about 12 of them, and a vendor can export three and still say truthfully that you own everything.
- Insist on a self-serve export you can run while logged in. An export that needs a support ticket runs on the vendor's schedule, not yours.
- Accept CSV or another delimited text file with the ids intact. A PDF of service reports is a picture of your data, not your data.
- Chemical readings are the record most often left behind and the one you cannot reproduce - name it explicitly, and ask whether the export covers full history or the last 12 months.
- Export requests usually have to be submitted before termination, so the last useful day to pull your files is the day before you cancel.
- Run the export, open the files, check the row counts, and only then cancel the old subscription.
Who owns my data in pool service software?
You do. Every mainstream pool service platform says so in its terms, usually in a clause naming your records as "Customer Data" and the vendor as a processor of it. That is real, and it is worth having in writing. It is also the easy half of the question, because ownership is a legal statement and access is an engineering one, and the two are decided by completely different people.
Ownership tells you who has the right to the records. Access tells you whether there is a button that produces them. A vendor can honestly say you own your data while shipping an export that covers only customers and addresses, because nobody built the one for chemical readings. Nothing in the contract was broken. You simply cannot get to nine of your twelve record types.
So the useful version of the question is narrower: which records come out, in what format, and who has to run it. A pool route generates about a dozen distinct record types - customers, pools, routes and stops, visits, chemical readings, work orders, invoices and their line items, payments, quotes and their lines - and a vendor can export any subset of those and still claim, truthfully, that you own everything. If you have ever gone through bringing an existing customer list in from a spreadsheet or another system, you already know the shape of the problem from the other direction: the import is only as good as the file the last vendor gave you.
Ownership without an export button is a promise, not a right
A right you can only exercise by asking permission is not much of a right. The practical test is whether you can produce the file yourself, logged in, without opening a support ticket - because the moment an export requires a human on the vendor's side, its timing belongs to them. Most privacy policies commit to "commercially reasonable efforts" within 30 days, which is a fine legal standard and a terrible operational one when you are trying to run two systems side by side for a week.
A two-truck operator in Sarasota running 180 pools left a previous system and got exactly what he asked for: a CSV of customer names and service addresses. What he did not get was the chemical history - four years of readings that stayed behind, because the export the vendor had built covered customers and nothing else. Six months later an HOA board asked what the free chlorine had been running on their pool through the previous summer, and the honest answer was that the record existed, was his, and was unreachable.
That is the whole argument for asking early. Nothing was withheld from him and no contract was violated. The export simply did not cover the record type he ended up needing, and he found out at the point where the only remedy was a screenshot. Self-serve matters more than generous, and specific matters more than either.
This is not an exotic thing to build, which is why it is fair to expect it. PoolBoss exports 12 datasets as CSVs from the Settings screen - customers, pools, visits, chemical readings, routes, route stops, work orders, invoices, invoice line items, payments, quotes and quote line items - plus a single download that bundles all twelve into one ZIP, so verifying you can leave takes one click rather than twelve. It is admin-only, and it runs on demand rather than by request.
The records to ask for, and the format to accept
Ask about record types by name. "Can I export my data?" gets a yes from everyone; "can I export chemical readings, with the visit and pool they belong to, as CSV?" is a question with an answer. Below is the list worth walking a vendor through, and what each one costs you if it does not come out.
On format, the bar is low and non-negotiable: CSV or another delimited text file, one row per record, with the identifiers that link the rows together. A PDF is a picture of your data, not your data - a 400-page PDF of service reports cannot be imported anywhere, and re-keying a season of readings is not a real option. If a vendor offers PDF only, treat that as a no.
| Record type | What it costs you if it stays behind | Format to accept |
|---|---|---|
| Customers | Names, addresses, contact details - the book itself | CSV |
| Pools | Gallons, surface, sanitizer type, equipment notes per pool | CSV |
| Routes and stops | The stop order you spent two seasons tuning | CSV |
| Service visits | Proof of every visit: date, tech, status, notes | CSV |
| Chemical readings | The liability record - years of it, unreproducible | CSV, linked to visit and pool |
| Work orders | One-off repairs, what was quoted, what was done | CSV |
| Invoices and line items | What you billed and what it was for | CSV, headers and lines both |
| Payments | What was collected, when, against which invoice | CSV |
| Quotes and line items | Open proposals and your pricing history | CSV |
The five questions to ask before you sign
Run these in a demo, in this order. They take about five minutes and they are answerable on the spot by anyone who knows the product. A sales rep who has to check with engineering on question two has already told you something useful.
Getting out is one half of the due diligence; who can see the records while you stay is the other, and it is worth running the security questions to ask the same vendor in the same conversation.
- Which record types export, by name? Read the list from the table above and make them answer for each one. "All of it" is not an answer; nine of twelve is a common reality and it is fine to know that going in.
- Can I run the export myself, today, without contacting support? Ask them to show you the screen. If the answer is a ticket and a 30-day service level, price the delay into your switching plan now.
- What format do I get, and do the files link together? CSV with the ids intact means the data can land somewhere else. Disconnected files or PDFs mean you own a pile of paper.
- Does the export cover the full history, or the last 12 months? Chemical readings and visits are the records where depth matters, and a rolling window is the most common quiet limit.
- What happens to the export after I cancel, and how long do I have? Get the number of days in writing, and note whether export requests must be submitted before termination rather than after.
What happens to your data after you cancel
Assume the window is short and closes the day you cancel, not the day you finish moving. There is no industry standard here, and the policies that exist run from a 30-day read-only grace period to immediate revocation of access with records anonymized on a schedule after that. The one pattern that shows up in nearly every set of terms is that export requests have to be submitted before termination takes effect - which quietly means the last useful day to pull your files is the day before you cancel, not after.
PoolBoss publishes its own version of this in its privacy terms rather than leaving it vague: closing an account revokes access immediately, or within 14 days if you use the closure grace period, and roughly 90 days after closure personal details - names, contact information, free-text notes - are permanently anonymized. Whatever a vendor's numbers are, the operator's move is the same: run the full export first, confirm the files open and the row counts look right, then cancel.
Do that in the order that keeps you covered. Pull every record type while the account is still live, open the chemical readings file and check that the oldest visit you care about is actually in it, and only then start the clock on the old subscription. If you are mid-switch, it is worth reading what a clean import actually involves before you export, because knowing what the new system wants tells you which columns you need out of the old one.
None of this is a reason to stay somewhere. It is the opposite: an operator who knows exactly how they would leave can evaluate a tool on whether it is good, rather than on how trapped they would be. Put the export question next to the rest of the evaluation checklist, and if you are already partway out the door, what switching looks like end to end covers the sequencing.
FAQ
Frequently asked questions
Does my customer list belong to me if my technician entered it?
Yes. Work an employee does in the course of their job belongs to the business, and a customer record your tech typed into your account on your time is your record, not theirs and not the software vendor's. The place this gets tested is not ownership but access: a technician who leaves with a photo of the route sheet has taken a copy, and the practical protections are contractual, not technical. If your route has real value - and a pool route is usually the most valuable thing a small service company owns - it is worth having a written agreement with anyone who can see the whole book. Ownership settles who has the right to the list. It does not stop a copy from walking out, and no software setting does either.
What should I export before I switch software?
Everything, in one pass, while the old account is still active. At minimum: customers, pools, routes and their stop order, service visits, chemical readings, invoices with their line items, and payments. Export them even for records you do not plan to re-import, because the reference file is what answers a customer question about work done two years ago. Then verify before you cancel anything - open each file, check the row count against what you expect, and confirm the oldest record you care about is actually present rather than trimmed by a rolling window. Budget an hour for this. It is the cheapest hour in the whole switch, and it is the only part that cannot be redone later.
What if my current software has no export button at all?
Ask support directly and in writing before you assume there is none - plenty of platforms have an export that is not linked from the main navigation, and a written request also starts a paper trail if you need one later. If the answer really is no, prioritize ruthlessly: the customer list and pool specs are the records you must have, because they are what the new system needs to run at all. Service and chemical history is what you want, and if it can only be reached one pool at a time, pull it for the accounts most likely to generate a question - commercial pools, HOA properties, and anything with a repair dispute. Screenshots are a poor record, but they are a record, and they are better than nothing when a board asks.
Can I take my customers' saved payment methods with me?
Usually not directly, and the answer depends on who the merchant of record is. Card details are held by the payment processor, not by the pool service software, so the question is whether your business has its own processing account or is billing under the vendor's. If the account is yours, saved cards typically stay with it and can move, subject to the processor's own migration process. If the software resells payments under its own account, the stored cards generally do not transfer and you will re-collect authorization from customers. Ask which arrangement you are in before you sign, because it also decides whose name appears on your customers' statements and who owns the dispute relationship.
Is a PDF service report the same as having my data?
No. A PDF is a rendering of your data at one moment, useful as evidence and useless as data. You cannot import it, sort it, total it, or answer a question like "what has the cyanuric acid been running on this pool since March" without reading every page by hand. For a 60-pool route at weekly service, a year is roughly 3,100 reports, which makes re-keying a non-option. Keep the PDFs if a vendor offers them, because a signed-looking report is worth having in a dispute. Just do not accept them in place of the delimited files, and treat PDF-only export as a no when you are evaluating.
If I am on a free plan, do I still get my data out?
You should, and it is a fair thing to check specifically, because export is exactly the kind of feature that gets held behind a paid tier. Ask whether the export works on the free plan or only once you are paying - the answer tells you a lot about how the vendor thinks. A tool that gives you a way out on the free tier is one that expects to keep you on the merits. A tool that unlocks your own records only after you pay has told you what the paid plan is really selling. The same test applies to a trial: if you cannot export during the trial, you cannot honestly evaluate the tool, because you cannot verify the exit before you commit the book.
