The r/MedSpa post asks salon owners and med spas a single question, and it is one of the most consequential questions a service business can answer: how hard is it to export your client lists from your booking platforms, and how are you going about it?
It is consequential because the client list is the most valuable asset a treatment business owns. Not the equipment, not the lease, not the brand β the list of people who have been treated, what was done, what they responded to, and when they are due back. Everything else can be replaced. That list is the business, and whether the business can take it out of its software determines whether it owns its client relationships or rents them from a vendor.
What "export" should actually mean
Most platforms will tell you that your data is yours. Very few will hand you something that makes that statement useful. The practical test is whether the following can be produced on demand, in a machine-readable format, without a fee and without asking permission.
Client contact records with names, phone numbers, email addresses and any profile fields the practice actually uses.
Appointment and visit history β the dates and services performed, which is what makes a lapsed-client campaign possible at all.
Treatment notes and records, or at minimum the ability to retrieve them in a usable form. A record that can only be read inside the platform is not portable, and treatment records carry obligations that survive a platform change.
Package, series and gift card balances. These are liabilities, and a practice that changes systems without carrying the balances across will end up honouring them from memory.
Marketing consent status β who has agreed to receive marketing, and under what terms. Rebuilding this after a migration means re-obtaining consent, or risking sending marketing to people who never agreed to it.
Payment and purchase history, which is what allows revenue reporting to continue across the change.
A PDF of the client list is not an export. It is a screenshot with extra steps, and it cannot be imported anywhere. The format to insist on is a plain data file β CSV or JSON β with the fields above, and the way to know whether you have it is to try it.
The test to run before you need it
The single best practice here is also the simplest: request the export early in the relationship, not during a dispute.
Do it in the first month, or at whatever point the practice is new to the platform, while the vendor still wants to keep you and the data set is manageable. Export everything, open the files, and check three things. Are the fields there, or is the appointment history missing? Are the records complete, or truncated at some earlier date? And do package and gift card balances appear, or are they invisible outside the platform's own screens?
Then repeat the exercise on a schedule β quarterly is enough β and keep each export in the practice's own storage, labelled with the date. Two things follow from this habit. The first is a backup that does not depend on any vendor's availability, which matters the day a platform has an outage, changes its pricing, or shuts down. The second is negotiating position: a practice that can demonstrate it is able to leave at any time negotiates from a different place when the renewal comes around.
A spreadsheet of client records with treatment notes is sensitive data, and it should be stored accordingly β access limited to the people who need it, and a defined policy about where the files live. A backup that leaks is worse than no backup.
Contract terms that decide the answer
Portability is partly a technical property and partly a contract term, and the contract is where the surprises are. Six clauses are worth reading carefully before signing anything.
Term and auto-renewal. A multi-year contract with automatic renewal and a long notice period is a commitment that outlives a change of mind, and it limits the value of portability.
Data access after termination. Whether the practice can retrieve its data after the contract ends, for how long, and in what format. Some agreements are silent, which is the worst outcome, because it means the answer is decided by whoever is answering the phone that week.
Export fees and migration charges. A charge for exporting your own client records is a small amount of money and a large statement about the relationship.
Price escalation. What the platform may charge in year two and year three, and on what basis.
Ownership and permitted use of client data. Who is considered to hold the data, and what the vendor is permitted to do with it. This is the clause most practices never read and most should.
Service levels and continuity. What happens to access during an outage, and what notice the vendor must give before discontinuing a service the practice depends on.
The privacy side of the same question belongs with a lawyer rather than with a sales representative. Which party is responsible for what under the applicable privacy rules, and what client consent covers for marketing versus treatment records, are jurisdiction-specific questions. A practice that migrates client information between systems should confirm its obligations rather than assume that the way it has always done things is sufficient.
The migration playbook, if it comes to that
When a practice does change platforms, the failure mode is not usually the export. It is the import.
The sequence that works starts with a full export from the outgoing system, taken twice β once as a portable working file and once as an untouched archive. Then the fields are mapped to the new system deliberately, because most migrations lose data in the mapping rather than in the transfer: a service category that does not exist in the new platform, a note field with nowhere to go, a consent flag with no equivalent field. Then the balances are reconciled: package and gift card balances need to be carried over as commitments, not as notes.
For marketing consent, the safe assumption is that a migration does not refresh permission. Contacts whose consent can be evidenced can be used; contacts whose consent cannot be evidenced need to be handled carefully or excluded, and re-consented if they are to receive marketing. That is slower than importing everything, and it is the difference between a clean migration and a privacy complaint.
Finally, run a first-month reconciliation. Total client count before and after. Last month's appointments. Outstanding balances. Anything that does not match gets found now, while the old system is still accessible, rather than in six months when it is not.
Portability as a selection criterion
The strategic shift worth making is to treat export capability as a headline feature when choosing a platform, alongside price and functionality, rather than as a detail discovered later.
The reasoning is straightforward. Software vendors compete for a practice's business, and their pricing and terms reflect how easily the practice could leave. A practice that cannot extract its client list has effectively been acquired by its vendor, and the terms it is offered in the following years will reflect that. A practice that can leave at any time, and can prove it in ten minutes, is a customer the vendor wants to keep. Portability is therefore not just a contingency plan. It is what maintains the practice's negotiating position for as long as it uses the software.
There is a resilience argument that costs nothing to make either. Booking platforms go down, change ownership, raise prices, discontinue features, and occasionally shut down. In every one of those scenarios the practices that are inconvenienced and the practices that are damaged are separated by a single fact: whether they have their client list in a file they control.
The answer to the question
It should be easy to export your client list, and in practice it usually is not, because the useful parts β visit history, treatment notes, and prepaid balances β are the parts most likely to be locked up. The way to find out is to ask in the first month, request a machine-readable export, open it, and check the fields. Then diarise the exercise and keep the files.
The practice that treats its client list as an asset it holds, rather than as data it is allowed to see, is the practice that can change software, negotiate from strength, and survive a vendor's bad year. All of that is decided by a question that takes a few minutes to ask, and the good time to ask it is before signing rather than after.