The most common path into a medspa CRM is not a deliberate choice. It is whatever the original esthetician used when the practice opened with one chair, which then survived through provider hires, second locations, and the introduction of medical-grade services. By year three, the software is doing 60% of what the practice needs and the front desk is doing the other 40% in spreadsheets, paper forms, and a separate payment terminal.
That state is workable. It is also expensive in ways that do not show up on the invoice. This piece is for operators who have started feeling those costs and are weighing whether to migrate.
Three signals you have outgrown a salon CRM
1. Your consent forms live anywhere but the chart
Salon-first platforms shipped without per-treatment consent because hair salons do not need it. The workarounds — paper forms in a filing cabinet, PDF e-sign in a separate tool, consent forms scanned and emailed — accumulate compliance risk in a way most operators do not see until a state board inspection. If your medspa books Botox or filler and the consent does not auto-attach to the appointment when it is booked, the system is wrong, not your staff.
2. Your daily close-out involves the word "reconcile"
A daily close-out where the CRM's number does not match the terminal's number is a flag. It usually means the CRM treats payment as informational — a record that someone paid, but the actual money flowed through a separate system the CRM has no visibility into. Multiply that across three payment methods and you are doing reconciliation work every evening that should not exist in a modern system.
3. You have started building reporting in Google Sheets
The clearest signal. When a manager exports a CSV from the CRM every Monday, opens it in Sheets, and runs the actual report the practice needs — that is software-shaped work the platform should be doing. Reporting gaps are the operational equivalent of leaks: small at first, expensive at scale.
What is actually different for medspas
Five operational differences between salons and medspas that the major salon platforms either do not model or model thinly:
- Per-treatment consent recurrence. Hair salons need one intake form per client, signed once. Medspas need a fresh consent at every Botox, filler, and laser visit, because the risk profile is per-procedure. Salon platforms attach forms to clients, not appointments.
- Treatment-cycle scheduling. Botox at 12–14 weeks. Filler at 6–12 months depending on product. Laser series at 4–6 weeks. The next-visit suggestion at checkout should be deposit-on-book, not "we will see you whenever."
- Provider commission and treatment attribution. Medspas often pay providers per-treatment commission, not flat hourly. The CRM must split revenue by provider per line item, and report it that way.
- Medical-grade audit logging. If your state medical board asks who viewed a chart on a specific day, you need to answer in seconds, not days. Salon platforms generally do not write that log.
- The BAA cascade. If you are a HIPAA-covered medspa (most are, even when they don't realize it), every vendor that touches PHI needs a Business Associate Agreement on file. Most salon platforms gate the BAA behind a premium tier or do not offer it at all.
What to export before you sign anywhere
The single biggest migration mistake: signing the new contract before confirming you can actually get your data out of the old one. The export shape matters more than the new vendor's import promise.
The data you must extract:
- Customer records: contact information, birthday, allergies, medical history, treatment history, loyalty status. Confirm fields like allergies and notes come out in a structured format, not as free-text blobs.
- Appointment history: past appointments, including no-shows and cancellations, with timestamps, provider, service, and outcome. Two years minimum.
- Signed consent forms: as PDFs, with timestamps and signature metadata. This is often the hardest export, because some platforms only return the form image without the metadata that makes it audit-defensible.
- Invoice and payment history: for AR aging, revenue history, and tax records. Confirm payment-method breakdown comes out (cash vs card vs check), not just totals.
- Memberships and packages: outstanding balances, expiration dates, attached clients. Skipping this on migration is how spas lose revenue they had already collected.
- Gift card balances: outstanding balances and the underlying ledger. Mishandled gift cards become accounting and customer-service problems for years.
- Marketing audience and opt-in status: who consented to SMS, who consented to email, when. TCPA opt-in does not transfer if the underlying consent record does not.
The platforms that make this hard
Aesthetic Record has been reported on Capterra and Software Advice to charge a $1,120 fee to export patient data after the first two years. That is a contract clause to read carefully before signing.
Mindbody and Vagaro typically permit CSV exports but limit the level of detail; some structured fields come out as free-text. Boulevard's exports are reasonably complete but may require a support ticket for historical data beyond a certain age.
Ask every vendor — yours and the new one — three questions in writing:
- What is included in a standard data export?
- Are there any fees for export, ever?
- What is the timeline from request to delivery?
Any vendor that cannot answer those in writing is a vendor you are not in control of.
The cost of staying
Migration is real work. Estimating the cost of the status quo is how you justify the work.
Rough math for a one-location medspa with three providers:
| Hidden cost | Estimated annual hit |
|---|---|
| Front desk time on workarounds (2 hr/day × $20/hr × 250 days) | ~$10,000 |
| No-shows above industry-best from missing deposit flow (10pt × ~$300 × 1,200 appts) | ~$36,000 |
| Card-volume markup at 1.5% on $1.5M annual volume | ~$22,500 |
| Premium-tier upgrades for features that should be standard (Forms, QuickBooks, etc.) | ~$1,500 |
| Compliance gap (un-quantifiable until it becomes very expensive) | — |
The numbers vary by practice. The order of magnitude — a five-figure annual cost for a single-location medspa — does not.
A realistic 2–4 week migration timeline
Week 1: Scoping
Pull a sample export from the current platform. Map fields between source and destination. Identify any data that requires manual cleanup (free-text fields, photos, unstructured allergy notes). Write a one-page migration spec — what moves, what stays, what gets archived.
Week 2: Dry run
Run a non-production import of the export into the new platform. Verify customer counts, appointment counts, invoice totals match the source. Spot-check a dozen client charts end-to-end. Document any discrepancies.
Week 3: Cutover preparation
Train front-desk staff on the new platform. Run them through 20 mock workflows: book, check in, take payment, send consent. Choose a cutover date — typically a Sunday evening so the practice goes live on a Monday morning. Send client-facing communications about the new booking page if the URL is changing.
Week 4: Cutover + parallel period
Final export from the source on cutover day. Final import into the destination. Verify the daily close-out for the first week on the new platform reconciles cleanly. Keep the source platform accessible (read-only) for 90 days in case a question about historical data comes up.
What we have learned from medspas migrating onto Lumè
Two medspas are migrating onto Lumè in 2026. We are taking on a small, deliberate number of additional customers this year so we stay close to every onboarding. From the two we have run so far, three patterns:
- The export is always lossier than the vendor claims. Plan for a half-day of manual cleanup on consent metadata and provider notes.
- The cutover is rarely the hard part. Training the front desk on the new workflows takes the most time. Schedule that ahead of the import, not after.
- The first daily close-out is the moment of truth. If the numbers tie out on day one, the migration is done. If they do not, you know within 24 hours where to fix.
Our scoping conversation during the demo includes the export-shape review and a migration timeline based on your actual data. The fee for the migration is bundled into the onboarding — there is no separate setup line on the invoice. See pricing for the broader structure.
If you are running on Mindbody, Vagaro, Boulevard, Aesthetic Record, or a spreadsheet, the migration is in scope. Most complete in two to four weeks. Request a demo; we will look at a sample export from your current platform and tell you what we see.
References: Capterra and Software Advice user reviews of Aesthetic Record, Mindbody, Vagaro, and Boulevard (2024–2026); HIPAA §164.502(e) (Business Associate requirements); state medical board export and retention guidance (CA, NY, TX, MA).