Your Client List Is the Only Thing in the Salon You Can't Replace

Every physical thing in your salon can be replaced by Thursday. Chairs, dryers, the terminal, the shampoo bowls, the sign out front. Insurance exists for exactly this reason.

Your client list cannot be replaced at all. Neither can eleven years of appointment history, or the colour formula that took your senior stylist three appointments to dial in for a client who is very particular about her ends.

Which makes it strange how few owners have ever tried to get that data out of the system it lives in.

Not because they're planning to leave. Because the day you need the export is never a calm day. It's the day pricing changed, or the platform had an outage during Saturday's rush, or you got an email about an acquisition. Doing it now, while nothing is wrong, is a fifteen-minute job. Doing it under pressure is a different job entirely.

The five things you're actually asking for

“Export my clients” is not a complete request. There are five distinct data sets, and platforms are inconsistent about which ones they'll release.

Client records. Name, phone, email, address, date of birth, and — critically — marketing consent status and the date it was captured. That last field is the one nobody asks for and everybody needs. Without it, your new platform has contacts but no legal basis to message them, which is its own problem.

Appointment history. Past and future. Future bookings matter most: if you switch platforms with 340 appointments already on the books and can't import them, you are rebuilding a calendar by hand while clients are arriving.

Formula and treatment notes. The hardest export in the industry, and the most valuable. More on this below.

Financial balances. Outstanding gift card values, prepaid packages, memberships, loyalty points, account credits. Every one of these is a liability you owe a real client. Losing the record doesn't extinguish the obligation — it just means the client tells you what it was.

Products and inventory. Service menu, prices, retail SKUs, costs, current stock levels, supplier codes.

What usually breaks

Exports rarely fail outright. They degrade, quietly, and you find out three weeks later.

Phone number formatting. (905) 555-0142, 9055550142, and +1 905 555 0142 are three different strings. Import them without normalisation and you get duplicate client records — the same person twice, with the history split between them.

Date formats. A CSV that doesn't declare whether 05/06/2024 is May 6th or June 5th will silently reorder your appointment history. This one is common and genuinely nasty, because nothing looks wrong.

Character encoding. Every accented name in your database — every Québécois client, every stylist named José — is a candidate for mojibake if the file isn't UTF-8. Open the export in a text editor before you trust it.

Multi-line notes. Formula notes contain line breaks and commas. In a CSV, those break the row unless they're properly quoted. This is the single most common way formula history is destroyed in migration.

Deleted and archived clients. Some exports include them, some don't. If your list of 3,200 clients comes back as 2,100 rows, find out why before you conclude the platform “just doesn't have” the rest.

The formula problem

Ask a salon owner what she'd most hate to lose and she'll say her client list. Ask her senior colourist and she'll say the formulas.

Formula data is the worst-structured data in the industry. It's usually a free-text note field — sometimes several, sometimes appended over years, sometimes with a stylist's private shorthand that only she can read. There is no standard. 6N + 6.3 20vol 1:1 35min means something precise to the person who wrote it and nothing to a parser.

Two things follow. First, export the notes field even if it looks like a mess. Messy history is infinitely better than no history. A stylist can read a badly formatted note. She cannot read a note that no longer exists.

Second, this is the strongest argument for moving formula data into a structured field rather than a text box the moment you're on a new system. A formula stored as products, weights, developer volume, and processing time survives every future migration. A formula stored as a paragraph survives exactly as long as that paragraph does.

This is the problem NeonO's Migration Mapper was built around — it reads exports from Fresha, Vagaro, Phorest, and Encore, normalises the field structures against each other, and parses free-text formula notes into structured records rather than dumping them into another text box.

Two things worth knowing about your obligations

The client data in your booking platform is personal information about identifiable people, and under PIPEDA you're the organisation accountable for it. Two practical consequences.

You have a right to it, and so do they — individuals can request access to their own personal information held by your business, which is difficult to honour if you can't get it out of your software.

And when you migrate, the security of that file is yours. An unencrypted CSV containing 2,500 clients' names, phone numbers, emails, and birthdates sitting in a Downloads folder or emailed to a developer is a breach waiting to be reported. Move it deliberately, delete the copies afterward, and don't send it over anything you wouldn't send a passport photo through.

The parallel run

The mistake is treating migration as a switch you flip on a Sunday night.

Week one — export and audit. Pull all five data sets. Count the rows against what the old platform reports. Open the files. Spot-check twenty clients you know personally, including one with an accented name and one with a long formula history.

Week two — import and verify. Load into the new system. Check the same twenty clients. Then check the awkward ones: the client with two phone numbers, the one who's also a staff member, the one with an outstanding package balance.

Week three — parallel run. New bookings go into the new system. The old one stays live and readable. Nobody is trusting anything yet.

Week four — switch the channels. Instagram bio, Google Business Profile, website, the QR code at the desk. This is the real cutover, and it's the last step, not the first. Keep read access to the old platform for at least ninety days after.

Do the export today anyway, even if you have no intention of going anywhere. A current export of your client list, stored somewhere you control, is a business continuity document. Everything else in the room is insured.

Menu paths and export capabilities in third-party platforms change frequently. Verify current functionality in each platform's own help documentation before planning a migration.

Related reading: Switching to NeonO · What Fresha actually costs in Canada · NeonO vs Vagaro · CASL for salons