Switching med spa software is mostly a scheduling problem, not a data problem. Your client list, your appointments, your inventory and your service menu move across as a matter of routine. The parts that no export handles are moved by hand. What actually catches clinics out is timing: knowing your notice date before you pick a new system, and rebuilding membership billing dates so nobody gets charged twice in week one.

Most owners put this off for years because they assume they will lose their history. In practice the question is not whether your data comes with you. It is which parts arrive automatically, which parts someone has to carry across, and who is doing that work. Here is how it actually goes.

The three things that actually matter

Everything else is detail. Get these three right and the rest is logistics.

Know your notice date before you shop. Most software agreements renew on their own and ask for notice before the end of a term. Find that date in your own paperwork first, because it sets your earliest sensible move date. Clinics that pick a new system first and read the contract second are the ones who end up paying two vendors for a month or two.

Download your clinical archive while you still have access. Charts, photos and signed consents, exported and backed up somewhere you control. Do this early, whatever else happens. It costs an afternoon and it removes the only genuinely irreversible risk in the whole process.

Treat memberships as their own project. Saved cards can move between processors. The recurring billing schedules attached to them cannot, so every active membership has to be set up again with its next charge date checked. This is the step that actually costs money if it is rushed, and it is the one nobody warns you about.

What moves automatically, and what someone moves by hand

There are two paths, and knowing which one each thing takes is most of the anxiety gone.

What

How it moves

What you do

Client names, contact details, addresses

Automatic. Every system exports this

Nothing

Service menu and staff records

Automatic

Check working hours and commission setup afterwards

Product inventory and stock levels

Automatic

Time the import near go-live so counts are current

Upcoming appointments

Automatic, sometimes with a date limit at the source

Keep a printed or exported forward schedule as a backstop

Past visit history

Automatic, though some systems only release a recent window

Agree how far back you need before the import runs

Gift cards, packages and unused sessions

Balances move; the transaction trail behind them often does not

Reconcile the totals. These are money owed to clients

Membership plans and members

Plans and members move; billing dates are rebuilt

Confirm every member's next charge date before go-live

Charts and treatment notes

Moved as files attached to each client where the old system will not release them as records

Tell us how far back matters to you

Before-and-after photos

Brought across and attached to the client record, by hand when needed

Nothing, but say so early if you have a large library

Signed consent forms

Archived as signed documents on the client record

Nothing

Consent and chart templates

Rebuilt in the new system, usually improved while we are at it

Send us your current wording

Saved cards on file

Processor to processor, under PCI rules, without passing through anyone's hands

Start the request early. Details below

Booking rules, policies, discounts

Set up fresh during onboarding

A short call, not a data task

The important line in that table is the one that repeats: where an export cannot do it, a person does it. That is the whole answer to "will I lose my history". Nothing gets stranded because a file format did not cooperate. It gets carried across manually instead, and the only real variable is how much of it there is.

What to expect from your clinical records

Worth being straight about this part, because it is the one clinics ask about most.

Structured clinical notes rarely move as structured notes between two different systems, because no two platforms model a chart the same way. What happens instead is that your treatment history comes across as documents attached to each client, so it is there, it is readable, and it is where you would look for it. What it will not do on day one is populate a report in the new system the way a note created there would.

In practice this matters far less than it sounds. Your historical notes are a reference you consult occasionally, not a thing you run reports on. New notes created in the new system behave normally from the moment you go live. And if there is a subset of history you genuinely need as structured records, say so during scoping and it can be handled separately rather than discovered later.

The same is true of photos and signed consents. They come with you, attached to the right client, and someone checks that they landed.

Saved cards and memberships: the one fiddly part

Card numbers are portable between payment processors. You never touch them; the old processor sends them encrypted to the new one, and the receiving processor has to be PCI DSS Level 1 compliant for that to happen. Stripe, Braintree, Adyen and Square all publish a process for it, each under a slightly different name, and it is routine.

Two things to plan around. It is not instant, so the request goes in early rather than at cutover. And the recurring schedules do not travel with the cards, which means every active membership gets set up again with its next charge date chosen deliberately.

That second part is the single most common way a migration goes wrong after go-live, and it is entirely preventable. Every member gets checked against their old charge date before the first billing run. On our side that is a checklist item rather than something you need to manage.

A realistic timeline

Step

Who

Move on when

Find your notice date

You

You know your earliest exit

Download your clinical archive

You, with us on a call if useful

Charts, photos and consents are backed up

Scope the migration in writing

Us

You have seen what comes across and what gets rebuilt

Open the card transfer request

Us, with your authorisation

Both processors have confirmed

Import and check

Us

A sample of records has been spot-checked

Team training

Us

Front desk can book, check out and take payment unaided

Run both systems for a week

You

A full week with nothing missed

Go live and reconcile

Both

The checks below pass

Give notice on the old system

You

Only now

Notice goes last, not first. Serve it early and your notice period becomes a deadline instead of a buffer. There is no prize for cancelling sooner.

How to check nothing was missed

Six checks before you sign off. The three in bold are money owed to clients, so those need to match exactly.

Check

Should match

Clients seen in the last two years

Exactly

Upcoming appointments by provider

Exactly

Outstanding gift card balances

To the dollar

Unused package sessions and their value

To the dollar

Active memberships and next charge dates

Every one

A twenty-chart spot check, plus one live payment, refund and membership charge

All working

What we do, and what it costs

We have a team that does migrations full time. That is their whole job, not something squeezed between support tickets.

They pull what your current system will export, and they move the rest by hand: photos, documents, consents, whatever the old platform will not release cleanly. They rebuild your chart and consent templates. They set up every membership and check the next charge date on each one. Then they sit with your team until the front desk can run a normal day without help.

For most clinics this is free. Migration and 1:1 onboarding are included, and the exceptions are clinics with many locations or an unusually large amount of history. A rep confirms exactly what your migration looks like on the demo, before you commit to anything. That is published alongside everything else we charge on our pricing page.

Timing is the part worth raising early. If you are inside a notice period on your current contract, there is usually more room to line the two dates up than clinics expect, and a rep will work the schedule around it on the demo.

One more thing, and it applies to us as much as anyone: before you commit to any vendor, ask them for a sample export. Not a description of one, the actual file. What comes back tells you more about how that company will treat you than any sales conversation. Ask us too.

If you are earlier in the process, our breakdown of what med spa software actually costs covers the subscription and card processing arithmetic, and what a branded client app costs covers the client-facing side of the decision.

Frequently asked questions

Will I lose my client history if I switch?

No. Client records, appointments, inventory and your service menu move across as standard. Treatment history, photos and consents come with you too, attached to the right client, moved by hand where the old system will not export them cleanly. The realistic expectation is that everything comes, and some of it arrives as documents rather than as structured records.

How long does switching take?

Usually a few weeks from scoping to go-live, most of which is not waiting on data. Import and checking are quick. The time goes into training, running both systems in parallel for a week, and lining up the cutover with your notice date.

Do I have to close the clinic?

No. Bookings move to the new system while the old one stays readable, then you cut over on a quieter day. Nobody closes. The only real advice is not to go live in your busiest week or the day before a holiday.

What is the biggest mistake clinics make?

Giving notice before the new system is proven. That turns your notice period from a safety margin into a countdown. Give notice at the end, once everything reconciles.

How much does migration cost?

With us, nothing for most clinics. Migration and 1:1 onboarding are included, with exceptions for many locations or an unusually large amount of data, confirmed by a rep before you commit. Other platforms vary; some publish an onboarding fee and some price it as a service in your contract, so ask for the number in writing.

Can my clients' saved cards come across?

Yes. Card data moves processor to processor under PCI rules, without passing through your hands or ours. Recurring billing schedules do not move with them, so memberships are set up again and every next charge date is checked before the first billing run.

What about my chart and consent templates?

Rebuilt in the new system rather than transferred, and that is usually a good thing. Most clinics are carrying templates that grew by accident over several years. Send us what you use now and we will rebuild it properly.

Can I keep the EMR I already have?

Sometimes that is the right answer. Booking, memberships, rewards and a client app can run alongside an existing clinical system with charting left where it is, which avoids migration entirely and is a reasonable way to try a platform before trusting it with clinical records. We describe how that works on our client app page.

Malik Masmas

CEO

Share