Keep the original export
Save an unchanged CSV so every migration decision can be checked against the source.
Acuity migration guide
Move from Acuity to StudioDock without guessing at the data
A practical, CSV-first handoff for studios moving beyond appointment scheduling into rentable spaces, add-ons, and booking operations. Start small, validate future appointments, then cut over on purpose.
CSV first. Small sample first.
The Acuity preset recognizes appointment headers, but your team confirms each calendar-to-space mapping and preview before import.
- Acuity header detection and preset mapping
- Appointment ID duplicate protection
- Paid-amount and source-context checks
- Staged future-booking cutover
Before you export
Treat calendar labels as a space-mapping decision
Acuity calendars and StudioDock spaces are not interchangeable names. Build the destination space list first, then deliberately map each Acuity Calendar label to an existing StudioDock space instead of forcing uncertain labels through.
Confirm timezone context
Review exported start and end datetimes against the studio timezone before validating future bookings.
Choose a sample
Use a small, representative sample before importing the full history or switching links.
Exact Acuity preset fields
What the Acuity CSV preset can suggest
StudioDock detects an Acuity export from appointment headers and suggests these mappings. Exports vary, so inspect the preview and adjust it when your headers differ.
| Acuity CSV header | StudioDock field | How to use it |
|---|---|---|
| Appointment ID, Booking ID, or ID | External booking ID | Keeps the Acuity appointment reference. Repeated imports use it to skip an already-imported appointment. |
| First Name + Last Name | Customer name | The preset combines Acuity’s split name columns; confirm the preview before importing. |
| Email / Phone | Customer contact details | Preserves direct customer identity when those columns are present. |
| Start Time + End Time | Booking start and end | Use the exported datetimes and check their timezone context against your studio setup. |
| Calendar / Calendar Name / Space Name | StudioDock space | Map every Acuity calendar label to an existing StudioDock space before importing. |
| Appointment Price | Booking total | Carries the source appointment price for review rather than reconstructing it. |
| Amount Paid Online | Paid amount | Keeps the paid-online amount for future-booking and reconciliation checks. |
| Paid? / Paid / Payment Status | Payment information | Preserves the source payment-state context for the imported record. |
| Notes / Appointment Notes | Booking notes | Keeps source notes where they are useful to the operating team. |
| Type, Certificate Code, Label, Scheduled By, Date Scheduled | Migration notes and source context | Retains service, discount, label, scheduler, and scheduling-date context for traceability. |
The migration workflow
Six checks between Acuity and a clean StudioDock start
1. Export and save the original
Export the Acuity appointment CSV and retain an unchanged copy for reconciliation.
2. Create destination spaces
Set up StudioDock spaces first, then decide exactly which Acuity Calendar label maps to each one.
3. Start with a small sample
In the authenticated Import & Export area, choose Acuity, upload a small CSV sample, and inspect the detected preset.
4. Review the mapping
Check combined names, start and end times, space mapping, price, paid amount, payment information, and source notes.
5. Validate future bookings
Confirm active future appointments resolve to the correct space and retain the expected customer and payment context.
6. Cut over deliberately
Replace old booking links only after the StudioDock public flow is checked; keep the original export for handoff checks.
Plan and domain clarity
Keep public booking parity separate from admin migration
This public guide and its conversion paths are identical for owners evaluating Pro and Scale. Import & Export is an authenticated admin workflow, not a public booking URL. After setup, Scale tenants retain their verified custom-domain booking experience while migration operators work in StudioDock admin.
What to validate before switching traffic
- Each Acuity Calendar resolves to the correct StudioDock space.
- A sample has expected names, timing, price, paid amount, payment information, and source notes.
- Appointment IDs skip duplicates when an import is repeated.
- Future Acuity links are replaced only after the StudioDock public flow has been checked.
Continue evaluating
Relevant next steps for studio owners
Frequently asked questions
Acuity migration questions
Does StudioDock offer a one-click Acuity migration?+
No. StudioDock recognizes Acuity appointment CSV headers and suggests a preset mapping, but a safe move still requires the studio to confirm spaces, timing, payment context, and the records that should move.
Which Acuity fields does the preset recognize?+
The preset recognizes appointment ID, split customer names, contact details, start and end times, Calendar, appointment price, amount paid online, payment status, notes, scheduled date, Type, certificate code, Label, and Scheduled By when those headers are present.
Will imported Acuity customers receive new booking emails?+
No. Acuity imports preserve available direct customer details while suppressing fresh automated customer emails during the migration.
Can I rerun an Acuity import?+
Yes, provided the export includes Appointment ID or another supported booking ID. The importer uses that source ID to skip duplicate imported appointments; still review the preview before each run.
Ready to outgrow appointment scheduling?
Start with the workflow your studio actually needs.
Open a trial to set up your spaces, or send your Acuity migration question through the asynchronous demo form.