Moving salon software: how to keep client history meaningful after the import
Review appointment history, colour notes, photos, forms and balances before moving salon software, with clear limits around what an import proves.
On this page
A successful salon-software import needs to preserve the meaning of the records, not just copy a list of names. Historical appointments, free-text colour notes, photos, signed forms and financial balances each need their own mapping and review.
OpenChair offers assisted import work using AI-assisted mapping and human review. The scope, any charges, repeat-run handling and cutover arrangements need to be agreed for the particular salon. It is not a universal automatic importer or a guarantee that every field from every system can be transferred.
The useful starting point is an export your team can explain.
Agree what the move is meant to include#
“Bring our clients across” can mean very different things.
It may mean contact details only. It may also mean future bookings, previous visits, colour notes, client images, consultation responses, gift-card balances, deposits or memberships.
Those should not be treated as one undifferentiated request. List them separately and agree which are included, which need further investigation and which will remain available through another agreed record.
For a colour salon, losing the meaning of a previous formula may be more disruptive than a missing marketing label. For a lash and brow studio, consultation and image history may need close review. A barbershop may prioritise regular-client history and future appointments.
These are examples of what to inspect, not promises that every export contains the necessary data.
Inspect representative records before the full import#
Start with a small sample that includes ordinary clients and the cases most likely to expose a problem.
Choose a long-standing client, someone with future bookings and someone whose history contains the specialist notes your team relies on. Add a record with a relevant financial balance where that is in scope.
An illustrative sample might look like this:
| Source item | What to establish before mapping |
|---|---|
| An old first appointment | Whether it is a dated historical visit or merely a date written in a note |
| A free-text colour formula | What the text actually contains, and which measurements are absent |
| A client photo | Which client or visit it belongs to and whether its use is understood |
| A completed form | Whether the response, date and associated record can be preserved meaningfully |
| A gift-card or deposit balance | What the balance represents and how it will be reconciled separately from funds |
The purpose is to find ambiguity before the whole venue starts working from it.
Do not make “Client since” mean “Imported today”#
OpenChair's August client-history improvement uses the earliest known appointment for the client's starting point when that history is available. If there is no known appointment, the profile creation date remains the fallback.
Consider an illustrative client whose supplied first visit predates the move by several years. A historical appointment can preserve that context; a newly created contact record alone cannot.
The distinction is useful when staff review the relationship after migration. It also sets the right expectation: OpenChair cannot recover a missing history simply because the client has been imported.
Check both cases during review. A client with supplied appointment history should be understood differently from one whose export contains only contact information.
Keep imported notes separate from measured evidence#
A free-text formula may be worth preserving exactly because it contains information the colourist recognises.
It should not be silently converted into a complete measured bowl if the export does not contain the product quantities, date or mixing events needed to support that record.
For example, a note may identify a previous product combination without recording an actual amount. Preserving that note is useful. Inventing a quantity to make the destination look complete is not.
The same principle applies to a nail technician's old shade or shape notes. The presence of those words in a text field does not prove the previous system, or the imported record, had dedicated structured nail fields.
Map what is known. Keep the source's limitations visible. Ask the operator to resolve ambiguity where it genuinely needs their knowledge.
Check images and forms as records, not just attachments#
A folder full of images is not necessarily a usable client history. The team needs to understand who the images belong to and, where the source supports it, which visit they relate to.
A completed form also needs more than a filename. Review the actual response and the available date and association before treating it as part of a client's working history.
For a tattoo studio or beauty venue, these general checks may be important when reviewing an export. They do not establish that OpenChair supports every specialist record format or regulatory requirement.
Keep private client records separate from public portfolio use. Importing an image should not be treated as permission to publish it.
Reconcile balances without assuming money has moved#
A financial record and the funds behind it are different things.
Preserving a gift-card balance or deposit record does not transfer money between payment providers. Importing membership information does not automatically transfer the client's saved payment credentials or recurring payment mandate.
Agree the treatment of each financial category with the relevant people before cutover. Compare the source totals with the agreed destination records and investigate differences.
Do not turn an apparently matching total into a claim that every underlying payment arrangement has transferred correctly. Representative record checks and overall reconciliation answer different questions.
Use assisted mapping with a human review point#
OpenChair's assisted service can use AI to help with mapping and consistency checks, with results reviewed with the salon and corrected within the agreed scope before cutover.
That is different from uploading any file and assuming the system has completed a full migration automatically.
The salon's knowledge remains important. Staff can recognise a duplicated client, an implausible first-visit date or a formula note that has lost its meaning in a way that a column name alone may not reveal.
Do not rely on a general turnaround promise for a complete migration. A service-menu import request is a narrower task than moving all bookings, historical records and financial arrangements.
Agree the final handover#
Before changing the team's working system, agree which data has passed review, what remains unresolved, how later changes in the old system will be handled and when the team will begin using the new records.
The right outcome is an agreed and inspectable result, not simply a message saying an import has finished.
Start with OpenChair's switching guide and request an export review. A useful move preserves the history your team can actually rely on, while leaving missing or uncertain information visible.
