Importing From Another Platform

OpenChair's standard web workflow sends your current booking page to support for a service-menu import. A wider migration is assessed separately against the records and formats your current provider can export.

Submitting a booking URL does not automatically import clients, appointments, financial balances or historical records. Confirm the scope before switching off your existing system.

Request a service-menu import

1. On web, open the import option in Services, or choose managed import while reviewing services during onboarding.
2. Enter your public HTTPS booking link in Current booking page URL.
3. Select Send import request.
4. Continue setting up with the starter menu or manual services while support handles the request.

OpenChair records the request and alerts support. The current confirmation says support will import your services within two business days. This commitment is for the service-menu request, not a complete transfer of salon records.

An active request for the same URL is recognised rather than submitted twice. For request statuses and troubleshooting, see Service Import Requests.

Recognising a provider's booking URL does not establish support for all of that provider's data exports. Use a public booking link, not an administrator login or a link containing private client information.

Agree any wider migration before committing

If you can supply your salon data, we will work on importing the fields that reasonably match OpenChair. Our team uses AI to help with mapping and consistency checks, then reviews the results with you. We correct issues and re-run the import where needed until both parties are satisfied with the agreed outcome and ready to cut over. For the full process, see Switching to OpenChair.

Before sending an export, agree the records in scope, secure transfer method and any sensitive-data handling with OpenChair. AI providers used for the work must appear in OpenChair's Subprocessor List. Do not include full payment-card details, passwords, authentication secrets or unrelated records. Source exports and working files remain subject to OpenChair's privacy and deletion terms.

Ask OpenChair to review an available export and confirm each required item. The following are assessment questions, not a list of guaranteed transfers.

Records	What to confirm
Services and team	Prices, durations, processing time, staff assignments and which settings need manual setup
Future appointments	Dates, time zones, staff, service mappings, statuses and whether existing client links or reminders remain valid
Client details and visit history	Supported fields, duplicate handling, original visit dates and source labels
Colour formulas	Whether notes remain free text or become structured recipes; do not assume historical notes can be reused as measured mixes
Photos	Available files, client and visit matching, permissions and transfer method
Forms	Whether signed records, signatures and dates can be retained, and which templates must be recreated
Gift cards	Supported identifiers, remaining balances, expiry dates and redemption history
Deposits and credits	How records link to appointments and reconcile with funds held or paid out by the previous processor
Memberships	Active entitlements, remaining visits and whether recurring billing needs a separate setup

A transferred balance record does not by itself move money or transfer saved cards and payment mandates. Agree the handling of these separately.

Check the transfer before changing booking systems

Agree the fields, exclusions, charges, responsibilities, transfer method and timing in writing. Keep the original exports and arrange continued access to records that will not move.

Before accepting live bookings in OpenChair:

1. Compare the agreed imported records with the original export, including future appointments and any financial balances in scope.
2. Review service prices, durations, staff assignments and booking rules.
3. Confirm which system will send reminders and accept new bookings during the changeover, so clients do not receive duplicate messages or book twice.
4. Resolve discrepancies with support before relying on the migrated records.

There is no universal migration duration or completeness guarantee. The source data and the agreed scope determine the work.

Related articles

• Service Import Requests
• Onboarding
• Managing Services