Migrating from Acuity Scheduling: services, clients and appointments
Read-only at Acuity, a three-step import that is checked as it goes, and each step can be undone.
With your Acuity user ID and API key, Pilotiko reads your appointment types, clients and booking history without changing anything at Acuity, then imports them in order: services, clients, appointments. Status: Being commissioned: the connector is written and tested against a test server; it has not yet been verified with a real account.
In short
- Read-only: Pilotiko never writes to Acuity.
- Three-step import: services, then clients, then appointments.
- Each step is verified by re-reading the database and can be undone on its own.
- Undone records are archived, never deleted.
What does the Acuity Scheduling connection do?
It has one job: moving your data out of Acuity and into Pilotiko, so your services, clients and history are in place from day one.
Acuity Scheduling's API uses HTTP Basic authentication: your numeric user ID is the username and your API key the password. Acuity says these calls must come from a server where the credentials stay protected [1]. That is how Pilotiko works; once saved, the key never travels through your browser again.
The connector reads three things: your account (/me), your appointment types and your appointments over a period bounded by minDate and maxDate. Acuity returns at most 100 appointments per request by default [2], so Pilotiko chains requests to cover the whole history. Each appointment from Acuity carries, among other things, the client, contact details, date, duration, price and type [2].
The data then runs through the same pipeline as any imported file: discover, map, import, normalize, de-duplicate, reconcile and verify. Email addresses and phone numbers are normalized so the same client written two ways is recognized.
- Credentials requested: Acuity user ID (digits only) and API key (at least 8 characters).
- Read: appointment types (name, price, duration, description), clients (name, email, phone) and appointments (client, service, date, duration, price, status, staff member, notes).
- Written to Acuity: nothing, ever.
- Written to Pilotiko: services, client records and appointments, after you click Import everything.
How do you migrate from Acuity Scheduling to Pilotiko?
- 1
Find your credentials
In Acuity, under Integrations, locate your user ID and API key.
- 2
Click Connect in Pilotiko
Paste both values. Pilotiko checks access, then reads everything without changing it.
- 3
Match the calendars
Each Acuity calendar is linked to a Pilotiko staff member, existing or newly created.
- 4
Review the preparation
Pilotiko shows what is ready, the duplicates it found and anything that needs your decision.
- 5
Click Import everything
Services, then clients, then appointments: an appointment needs its client and its service. A summary appears for each step.
What is available, being commissioned or coming soon?
| Feature | Status | Detail |
|---|---|---|
| File import (CSV, Excel, .ics, .vcf) | Available | Universal migration, no Acuity connection needed |
| Reading services, clients and appointments through the API | Being commissioned | Tested against a fake server faithful to API v1 |
| Ordered import verified by re-reading | Being commissioned | Summary per step |
| Undoing a step | Being commissioned | Records archived, never deleted |
| Ongoing sync with Acuity | Coming soon | Not built: the connection is for migration |
| Writing to Acuity | Coming soon | Not planned in this connector |
How much retyping does a migration save?
How is client data handled, and how do you close access?
A migration moves personal information: names, email addresses, phone numbers and appointment notes. Quebec's private-sector privacy act makes the business responsible for what it holds (s. 3.1) and requires telling people the purposes and their right to withdraw consent (s. 8) [3]. Consent only lasts as long as needed for the purposes it was sought for (s. 14), and computerized information collected from a person must, on request, be released in a structured, commonly used format (s. 27) [3].
The API key is encrypted (AES-256-GCM) and stays on Pilotiko's server. Once the migration is done, choose Disconnect: the key is erased and the action goes to the audit log. At Acuity, go back to the Integrations section where the key lives to replace it. To exercise your rights with Pilotiko: your rights.
What are the limits of the Acuity migration?
After the move, your availability can come from your calendar: see Google Calendar or Outlook and Microsoft 365. For video meetings, see Zoom. Your old site's content is read by WordPress. Full list: integrations.
- The connector has never been tried against a real Acuity account; the first real run is the validation step.
- Acuity intake forms and labels are not carried over in this version.
- Payments recorded in Acuity are not transferred; only the appointment price is.
- Undoing a step archives the records it created; they stay viewable and are not destroyed.
Frequently asked questions
Does Pilotiko change my Acuity account?
No. The connector is read-only and never writes to Acuity, so you can keep Acuity running during the switch.
Where do I find my Acuity API key?
Acuity says it is in the Integrations section of your account, along with your user ID. Both values are required.
What if a client already exists in Pilotiko?
Pilotiko normalizes email addresses and phone numbers to spot duplicates. Duplicates are merged rather than created twice, and the summary counts them.
Can I undo the import?
Yes, step by step. Records created are archived, never deleted, so you can still check what had been imported.
Will my full history come over?
Pilotiko reads appointments period by period and chains requests of 100, covering the whole history the API exposes. The exact count appears in the summary.
What if I can't use Acuity's API?
Export your data as a CSV or .ics file and bring it in through Pilotiko's universal migration. The same mapping and de-duplication pipeline applies.
Sources
- Acuity Scheduling Developers, Quick Start (Acuity Scheduling API) (accessed on October 15, 2026).
- Acuity Scheduling Developers, GET /appointments (accessed on October 15, 2026).
- LégisQuébec, Act respecting the protection of personal information in the private sector (CQLR, c. P-39.1) (accessed on October 15, 2026).
Read next
Pilotiko integrations
Google Calendar, Outlook, Zoom, Stripe, LinkedIn, Cloudflare, Twilio and more: what each Pilotiko connection does today, with its status read from the code.
Connecting Google Calendar to Pilotiko
What the Google Calendar connection really does in Pilotiko: the calendar.events scope, busy times, invitations, its current status and how to revoke access.
WordPress integration: Pilotiko reads your existing site
Pilotiko reads the pages, posts and Yoast tags of your WordPress site through its public REST API, with no password, to start your new site from real content.