How to Switch From SimplePractice Without Losing Your Mind (or Your Data)

You've wanted to leave for months. Maybe a year. Then the price-increase email landed on a Tuesday morning between sessions, and something in you finally said: enough.

And then you didn't leave. Not because you changed your mind — because of the weight of the thing. Seven years of charts live in that system. Next week's sessions are scheduled in it. There's a claim in flight right now, somewhere between your submission and a payer's adjudication queue, and the idea of pulling the plug while it's out there makes your stomach drop. So you keep paying. The fear of the move is worth exactly one subscription fee a month, and SimplePractice knows it.

I want to name that fear precisely, because naming it shrinks it. It isn't really about losing data — exports exist, and you'll have three copies before this is over. It's about continuity: the dread of a Tuesday-morning client staring at a dead video link, a note you can't find during an audit, a payer check that vanishes into the gap between systems. Every one of those has a specific, boring prevention. That's what a migration plan is: a list of boring preventions, done in order.

Here's the truth that dissolves most of that fear: the data is yours, the export exists and works, and the therapist down the street has already done this. Changing EHRs is changing moorings, not crossing an ocean — you slip the lines in a particular order, and the order is knowable. This is the order. Done right, it's a weekend, not a month.

1. Before you cancel anything: get everything out

The single most expensive mistake in an EHR migration is canceling first and exporting second. So before you compare a single feature on the new system, take full inventory of the old one. In SimplePractice, the main tool lives under Settings as a data export, and an account owner can run it for the whole practice, a single clinician, or one client. It takes minutes to a few hours to process, then you download a ZIP. Inside, you'll find two kinds of cargo:

• Client demographics as CSV files — names, contact information, birth dates, insurance details, emergency contacts. This is the structured, machine-readable part, and it's what your next EHR can actually import.
• Clinical records as PDFs — a folder per client holding their chart: progress notes, assessments, intake documents, uploaded files. Complete, but frozen — documents, not data.

Check the folders against your own account, because the layout shifts over time — recent exports have included separate folders for billing documents, psychotherapy notes, and stored documents alongside the medical records. If you keep psychotherapy process notes, confirm they're in the ZIP with your own eyes; those are the pages you can least afford to discover missing in two years.

That's the main export. It is not everything. Billing history, superbills, insurance claims, and payment reports live in the reports section and need to be exported separately — do it now, while you're in there. Appointment history exports are past-only and can be spotty, so print or save your calendar a few months back and every scheduled session going forward.

Then there's the category nothing exports at all: your custom note templates, intake form wording, reminder timing, cancellation-policy text, automations, settings screens. For these, the humble screenshot is your friend. Open every settings page you ever configured and capture it. Twenty minutes of screenshots will save you hours of "wait, how did I have that worded?" on the other side. For the deeper story on why exports look like this — and what a real data standard would change — see what happens to your data when you leave your EHR.

2. The timing plan

A migration fails on timing more often than on data. Four rules keep you off the rocks:

• Pick a cutover date between billing cycles. SimplePractice doesn't refund partial billing periods, so cancel near the end of one you've already paid for. A Friday cutover with the weekend to import is the classic move.
• Deal with claims in flight first. Submit everything outstanding while you're still on the old system, then either let those claims pay out before you cancel or write down each one — client, date of service, amount, payer — and track them manually. Payers will keep paying you either way; the claim belongs to you, not to your software. You just need to know what you're owed.
• Export after your last session on the old platform. Run the big export early as a rehearsal, sure — but the final one comes after your last documented session, so it captures every note you'll ever write there.
• Assume there is no safety net after cancellation. You may have heard there's a 30-day grace window to pull data after you cancel. I could not verify one, and SimplePractice's own support documentation is blunt: recommendations are to export before canceling, a canceled account can't be reactivated, and once it's gone the data in it can't be recovered. Your paid access runs through the end of the billing period you've paid for — treat that as the real deadline, and finish exporting well before it.

One more habit worth its weight: if your budget allows, keep the old account alive one extra month after you've moved. Not as a crutch — as a harbor light. It's the cheapest insurance you'll ever buy against "did I miss a folder?"

3. The import on the other side

Here's what actually happens when the ZIP file meets your new EHR, told honestly, because vendors tend to fudge this part.

Demographics import cleanly. The CSVs are structured data, and a decent import tool reads them directly: names, contacts, birth dates, insurance. Practice Harbor's importer ingests the SimplePractice export as-is — it even runs a second pass to detect couples and rebuild them as couple files instead of two strangers who happen to share an address. Ten minutes, and your caseload exists in the new system.

Historical notes come along as documents. Those per-client PDFs attach to each chart as files — readable, printable, legally intact. What they don't become is structured notes: no EHR meaningfully parses another system's PDF exports back into editable fields, whatever the sales page implies. In practice this matters less than you'd fear. You'll open the old records the way you'd open any records from a prior treater: occasionally, to check history. New notes start fresh in the new system, and within a month the chart that matters is the one you're writing now.

Some things you rebuild by hand. Note templates, intake forms, recurring schedules, reminder settings — this is what the screenshots were for. It sounds like the horror-story part and it isn't: a solo practice rebuilds its templates and re-enters its recurring appointments in an afternoon. Half a day. You will also, almost certainly, use the occasion to delete the three templates you built in 2021 and never used.

4. Telling your clients (and their credit cards)

Clients experience your migration in exactly four places, and each has a clean fix.

The portal. New system, new portal, new invitations. Send them a few days before cutover so clients can log in before they need to. Expect a handful of "is this email legit?" replies; a heads-up message beforehand cuts those in half.

Telehealth links. Every standing video link changes. Update calendar invites, your email signature, and anywhere a client might have an old link bookmarked — the most common day-one hiccup is a client sitting in the old waiting room while you sit in the new one.

Cards on file do not transfer. Ever. This is not your new EHR being difficult; it's PCI security working as designed. Card numbers live with the payment processor, not in your EHR, and those stored credentials don't move between platforms. Every client re-enters their card once. Send something like this the week before:

Intake paperwork stays put. Existing clients already signed your consents; those PDFs came over with their charts. Don't make forty people re-do intake forms. The new forms are for new clients, starting day one.

5. The first two weeks: run parallel, then let go

For the first two weeks, keep the printout of your old calendar next to the new one and check them against each other each morning. You're looking for the recurring appointment that didn't recur, the biweekly client entered as weekly. You'll catch one or two. That's the system working, not failing.

When the first insurance payment arrives on the new system, reconcile it line by line against your list of claims in flight. That first ERA is the moment the money side of the move proves out — after it posts clean, you can stop holding your breath. If a payment for an old-system claim shows up in this window, it goes on your tracking list, not into a panic: the payer owes you the same dollars regardless of which software you were running on the date of service.

Somewhere in week two, a strange thing happens. You stop opening the old calendar. You write a note and realize you didn't brace for the software first. The migration you postponed for a year turns out to have been two evenings, a Saturday, and a stack of screenshots — and the monthly fee you were paying out of fear is just money again.

And the export archive itself? Keep it forever. Encrypted drive, plus a backup. Record retention rules outlive every software subscription you will ever hold, and that ZIP file is now a legal record of seven years of care. It costs nothing to keep and everything to need.

6. Try the crossing before you commit to it

The old advice was to trust the demo and jump. Better advice: run a trial migration first. Practice Harbor's free tier means the test costs nothing — export from SimplePractice today, import the file, and look at your actual clients in the actual system: the couple it linked, the charts with history attached, the calendar waiting to be filled. Move one client folder, see how it lands, then move the fleet. If it doesn't feel right, you've lost an evening. If it does, the scariest part of leaving is already behind you — and you haven't canceled anything yet. (While you're deciding, the full SimplePractice pricing breakdown is worth a read — knowing exactly what you're paying for makes the decision quieter.)