Card-on-File Portability Checklist for Spas

TL;DR: Saved card data lives with your payment processor, not your booking software, so portability depends on who processes your payments and whether they'll release the data. Before you switch platforms, audit your processor relationship, check your current platform's card export policy, and confirm your destination platform's import process. Most businesses skip this step and spend weeks chasing memberships and recurring billing after the cutover.

Switching booking software is already a project. Adding card-on-file migration on top of it, without a plan, turns a clean cutover into a months-long headache. Memberships stop charging. Recurring packages break. Clients who've never thought about their card suddenly have to re-enter it at checkout.

The good news is that saved cards are portable in most cases. The catch is that portability isn't automatic. It requires the right questions asked to the right parties, in the right order, before you give notice. This checklist walks you through each step.

Understand Where Card Data Actually Lives

This is the piece most operators get wrong. Your booking platform shows you a saved card. It does not hold that card. The raw card number, expiration date, and billing details live in a vault controlled by your payment processor. Your booking software holds a token. It is a reference ID that points to the real card in the processor's vault.

What this means in practice:

• If you stay with the same payment processor when you switch booking software, your saved cards can follow you. The processor reissues tokens to the new platform.
• If you switch payment processors at the same time, you're starting a new vault. The old processor would need to release the card data in a portable format (PCI-compliant tokenization transfer), and not all of them do.
• Your booking platform has no control over this either way. It can only request the transfer.

So your first question is not "does my booking software export cards." It's "who is my payment processor, and do they support token portability."

Check Your Current Platform's Card Export Policy

Once you know who your processor is, look at what your booking platform says about card data on the way out. Policies vary widely, and some platforms make this deliberately hard to find.

Two documented examples worth knowing:

Mindbody's support center states, as of September 2026, that card data can be exported to a new provider only when the business cancels its Mindbody subscription completely, and that there is a charge for the export. That means you cannot test the import at the destination before you've already cancelled. The sequence matters.

Fresha's help center states, as of September 2026, that client card details can't be exported or transferred. If your cards are in Fresha's payment system, plan for clients to re-enter payment details after the move.

For other platforms, ask support directly and get the answer in writing. The question to ask: "If I cancel my subscription, can my saved card tokens be transferred to a new payment processor or booking platform? Is there a fee? What is the timeline?"

Past coverage on what booking platforms actually do with card export requests goes into more detail on how these policies work in practice.

Map Which Clients Have Cards on File

Before you do anything else in the migration, pull a client list filtered by payment method. You want to know:

• How many clients have a saved card
• Which of those are on active memberships or recurring billing
• Which have a card saved for deposit or no-show protection only

Membership clients are the highest-stakes group. If their card doesn't transfer, their next billing date will fail. That triggers a collections workflow, a client service call, and sometimes a cancellation. The card-on-file migration guide for salon software switches covers how to triage that list before cutover.

For deposit-only clients, a failed transfer is lower stakes. They'll re-enter their card the next time they book. Still worth knowing the volume so you can staff for the extra friction at checkout.

The Portability Checklist, Step by Step

Work through this in order. Skipping ahead costs you time later.

1. Identify your current payment processor by name. It may be embedded in your booking platform or separate. Check your monthly statements if you're unsure.
2. Ask your processor directly whether they support PCI-compliant tokenization transfers to a new processor or booking platform.
3. Pull your client list and flag everyone on active memberships, recurring packages, or deposit holds.
4. Ask your current booking platform's support team, in writing, what the card export process involves: timeline, fee, and cancellation requirement.
5. Confirm with your destination platform how they handle the card import. Ask specifically: do they request the transfer from your processor, or do you?
6. Align the timing. If your current platform requires full cancellation before releasing card data, plan the import verification window carefully.
7. Keep your old system active until the import is confirmed complete. Cancel after, not before.

When you move to Tersavia, the team requests the transfer of saved cards from your current payment processor on your behalf. The processor controls whether and when the release happens, but having someone coordinate the request removes one step from your plate during an already busy cutover.

Communicate With Clients Before the Switch

Even a successful card transfer is invisible to the client. A failed one is not. Build a communication plan around the clients most likely to be affected.

For membership clients, a short email before the switch date explaining that billing will continue uninterrupted (if you're confident it will) sets the right expectation. If you're less certain about the transfer, tell them they may receive a one-time prompt to re-enter their payment details.

For deposit clients, update your booking confirmation template to note that clients may be asked to re-enter a card when booking their next appointment.

The worst outcome is a client whose card fails silently, doesn't get notified, and shows up for a membership appointment that's technically lapsed. A proactive email costs you thirty minutes. A churned membership client costs you the year.

FAQ

Does switching booking software automatically transfer my clients' saved cards?

No. Card data lives in your payment processor's vault, not your booking software. For cards to follow you, your processor must agree to transfer the tokenized data to your new processor or platform. Some processors do this. Others don't. Ask before you give notice.

What happens to my memberships if saved cards don't transfer?

The next scheduled billing attempt will fail. Depending on your platform's retry logic, clients may get a failed payment notice or simply stop receiving services without warning. Identifying your membership clients before the switch and communicating proactively is the most reliable way to protect that revenue.

Can I migrate card data without cancelling my current platform?

It depends on the platform. Mindbody's policy, per their official terms, as of September 2026, requires full cancellation before releasing card data. Other platforms may allow an export request during an active subscription. Ask your current platform in writing before you assume either way.

How long does a card transfer typically take?

Timelines vary by processor and the volume of cards involved. A small list might resolve in a few days. A larger book of business with hundreds of saved cards can take two to four weeks. Build that window into your migration plan and keep your old system active until you've confirmed the import is complete.