I’m mapping the practical work involved in Acuity-to-Wix Bookings migrations and would value experience from people who have handled one. Which part caused the most manual work or risk: recreating services and prices, rebuilding staff availability, moving upcoming appointments, retaining client history, or carrying over memberships and packages? I’m looking for lessons from real handovers, not client files or confidential details.
![]()
I have only briefly helped with these type of migration with Acuity.
Unless there is now a specific migration tool, then I would assume there would be issues with
- Remaining sessions, expiry dates, grandfathered pricing and recurring subscriptions as these rarely map correctly.
- Acuity can export appointments, but Wix does not provide a straightforward dashboard CSV import for bookings yet. But they can be recreated manually or through a custom API process.
Probaly more you need to consider.
Thanks, Dan — this is really useful. It sounds as though importing appointments can hide a much bigger problem with packages and subscriptions. In the migrations you helped with, did businesses usually sort out remaining sessions, expiry dates and subscriptions by hand, or was that enough to stop the move?
it wasnt a quick move. They basically had to run both systems for a while and block new appointments on the older platform.
I only helped another developer, so not sure how much other work they completed and how much the staff completed themselves.
I just coded some things to map cetain information correctly.