Client Scheduling Without Acuity: A Complete Switch

Client scheduling without Acuity can work through a coaching platform, another dedicated scheduler or a managed manual process. The useful question is whether the replacement supports your actual appointments, calendars, client access and purchase terms.

For an ongoing coaching relationship, moving booking beside preparation and client work can simplify the route. A move still needs a clear owner for every existing appointment and remaining entitlement. A spreadsheet export is not a completed migration.

This guide compares the practical choices and follows a complete fictional transition. The case preserves two existing bookings, closes the old booking route and grants only the four genuinely unbooked sessions remaining.

Choose against the service you deliver

Coachful is our #1 recommendation for coaches who want client scheduling connected with preparation, session credits and the wider coaching relationship. That is our recommendation for this use case, not a claim that it replaces every appointment configuration or is the cheapest option.

Acuity’s current official documentation describes packages, subscriptions, intake data, calendar connections and exports. Its existing capabilities should be compared honestly. The reason to move is a better fit for your work, not an invented absence of those features.

Price the whole transition: the actual plan, required capabilities, setup work, overlap and ongoing administration. Included booking inside a paid platform is not a zero-cost business system. Use current quotes and your own work estimates rather than a universal savings claim.

Separate appointment ownership from calendar visibility

A calendar can show an event without owning the appointment. The appointment system may control its confirmation, cancellation, reminders and package use, while an external calendar displays a copy or supplies busy-time information.

Acuity’s official calendar guidance says to change an Acuity appointment in Acuity. Editing its external-calendar copy does not reliably update the source booking. It also distinguishes publishing appointments from enabling external events to block availability.

The same ownership question matters during replacement. Write down which system owns each existing booking and which system handles new ones after cutover. Do not recreate all visible events in the new scheduler and assume the old confirmations disappear.

Check the host’s actual calendar selection and sync direction. Connecting a Google account is not the same as selecting every calendar that should block time. Shared calendars, read-only calendars and events marked free can behave differently according to the product’s configuration.

Reconcile a package before granting anything

Start with the commercial entitlement and match each unit to its state. A package of ten can include four held sessions, two future reservations and four unbooked sessions. Six are not yet delivered, but only four are free for a new reservation.

Different systems can call a unit used when it is booked, held or affected by a cancellation rule. Preserve those definitions. A platform’s remaining balance and the number of sessions not yet delivered answer different questions.

Check late cancellations, no-shows, reschedules, expiry and agreed exceptions against the actual purchase. A cancellation can restore booking value without refunding money. A session moved to another date should not become an additional delivered session.

The migration record needs the original purchase reference, relevant appointment identifiers, confirmed balance and chosen cutover treatment. Do not grant six unrestricted new credits on top of two live reservations. Equally, do not remove two sessions merely because their reservations appear in an export.

Export useful records without treating them as an import promise

Acuity’s current export guidance describes appointment CSV files containing dates, times, timezones, appointment identifiers and other fields. Selecting an intake form filters the export to appointments with that form attached and includes its answers. That matters when you need a complete appointment inventory.

Choose the date range and cancellation inclusion deliberately. Check the resulting coverage against the calendar and package record. A client-list export is different from an appointment export and does not itself establish package entitlement.

Export only what the transition needs. A scheduling reconciliation rarely needs every sensitive intake answer. Where UK GDPR applies, the ICO’s data-minimisation guidance provides relevant context; the page is under review following legislative changes, so confirm current requirements for your circumstances.

Keep the records in an appropriately controlled location. A CSV does not automatically become native Coachful appointments, a historical payment ledger or consent for a different staff audience. This guide’s case uses a manual reconciliation and a new nonbilling credit grant.

Configure the replacement before opening its route

In Coachful, define the actual session type, duration, host and meeting arrangement. A public discovery appointment and an ongoing client session can need different access and payment rules. Use a neutral event title that does not expose the coaching topic on a shared calendar.

Sessions > Availability contains Available times, Calendar Sync and Client Booking. Connect and select the relevant calendars, then check the host’s usable availability.

Timezone, duration, interval, buffer and advance-notice controls are under the Sessions settings gear > Scheduling settings, with an explicit Save. Do not invent independent before-and-after buffer controls or a daily session cap if those are not the available settings.

Check the client’s eligible route and compatible entitlement. If payment happened elsewhere, access can require a deliberately reconciled nonbilling grant. Creating that grant is not evidence of a new receipt or authority to charge the original card again.

For a fuller discussion of slot-fitting and buffers, see scheduling and buffer settings. Here the focus is a migration with existing commitments.

Begin the fictional transition with ten purchased sessions

Coach Tess supports Owen through ten fifty-minute individual sessions, already paid in one purchase. The original package has no expiry. Owen already has a Coachful client account for preparation, while Acuity currently owns booking and package-code use.

At the 26 October review, four sessions have been held. Two future Acuity appointments are confirmed for 2 and 9 November, both at 14:00 Europe/London, which is 09:00 America/New_York on those dates. Four sessions remain unbooked.

Tess’s Acuity subscription is managed through Squarespace, with a billing period ending on 15 November. She chooses a staged transition: keep existing appointments in Acuity until delivered, then open new booking in Coachful on 16 November after the old subscription has ended.

This is also a whole-account decision. Tess checks every client balance and future appointment before planning subscription closure. Owen is the last client with an unserved Acuity entitlement; no other future bookings, unused package obligations or recurring client payments depend on the account. Historical records still need appropriate retention. Without that wider check, finishing Owen’s two appointments would not justify closing the practice’s scheduler.

All people, dates, records, checks and outcomes below are fictional. This is a worked illustration, not a migration or runtime test performed on a real account.

Rehearse the new booking while preserving old commitments

Tess configures the fifty-minute client session and checks the host’s timezone. She selects the external calendars that should block her time. The old Acuity bookings remain visible through their existing calendar connection, and she confirms their busy periods are unavailable to the new route.

In an authorized test account, she checks an available slot, a known external busy period and the correct fifty-minute confirmation. She also rehearses a reschedule and cancellation, comparing the source appointment with the external calendar afterward.

The rehearsal checks the chosen configuration, not every future calendar failure. Tess records the selected host, calendars and observed states. She does not infer that a connection prevents all double bookings.

Owen’s two actual reservations stay in Acuity with their original meeting instructions. Tess neither creates duplicate Coachful appointments nor grants credits for those two reserved sessions. Owen receives an explanation through their private Coachful conversation and confirms that the existing dates remain suitable.

If either appointment needed changing before cutover, Tess would handle it in its source system and update the reconciliation. The move does not remove Owen’s existing cancellation or rescheduling rights.

Complete the legacy appointments before freezing the remainder

The 2 and 9 November sessions are held at the confirmed times. Tess checks their attendance and package use once in the Acuity record. The original ten are now six delivered and four unbooked, with no future reservations remaining.

She retains the appointment identifiers and original purchase evidence in the controlled migration register. She does not manufacture four new sales in Coachful or import old paid markers as cash receipts.

On 10 November, Tess requests cancellation of the Squarespace-managed Acuity subscription at the end of its billing period, not immediate termination. The confirmation shows 15 November as the end date. She keeps the service active until then rather than assuming a cancellation request already closed booking.

Before the end of 15 November, she checks for any additional bookings, cancellations or balance changes. None occurred in this fictional record. If one had, the four-unit figure would need reconciling again before a new grant.

The old code’s balance is evidence for the check; it is not treated as a second independent entitlement that can be redeemed in both systems after transfer.

Close the old booking route and grant four units once

After the subscription ends, Tess checks the old scheduler. It no longer accepts a new appointment. She also verifies that no future Acuity booking needs reminders or editing.

Acuity’s current Squarespace-managed cancellation guidance says existing appointments are not canceled when the subscription ends, but reminders and follow-ups stop and editing is unavailable. That is why this case completes its legacy appointments first. Other billing arrangements need their own checked cancellation behavior.

On 16 November, Tess grants Owen four compatible standalone fifty-minute credits in Coachful through Clients > Owen > Purchases & Credits > Grant session credits. She has checked that this session type has no credit-expiry period configured, preserving the original no-expiry terms. The grant itself is not a place to invent different expiry terms. She checks the resulting credits and records the original purchase reference in the operational reconciliation.

The grant creates access without a charge, invoice or new captured payment. The six delivered legacy sessions remain in the retained Acuity history; Tess does not claim they have automatically become native Coachful events.

She opens the new booking route only after confirming the old route is closed and the four-unit balance is correct. The commercial package remains ten sessions, rather than becoming six historical sessions plus six new unrestricted credits.

Send one complete cutover message and check the next booking

Tess replaces the website booking button and current reusable instructions. Old emails cannot change retroactively, so she sends Owen this explicit message through their private Coachful conversation:

“Your ten-session package is already paid. Six sessions have been held, including 2 and 9 November, and four remain unbooked. From 16 November, use your eligible fifty-minute client booking route in Coachful. The four credits preserve your original no-expiry terms; there is no new payment.

Your old Acuity route no longer accepts bookings. You do not need to recreate the sessions already held. Please check the displayed date, time and timezone before confirming. Send any booking or balance question in this private Coachful conversation; I will reply here within two working days, Monday to Friday, in Europe/London.”

The help arrangement was already agreed for the transition. Owen opens the new route and books 23 November at 14:00 Europe/London, displayed as 09:00 America/New_York. Tess checks the actual confirmation, meeting link and host.

One of the four credits funds that appointment. Three remain available for a future booking, while the reserved unit belongs to the 23 November session. It is not another cash transaction.

Owen says the new location is clear but that he initially opened an old email first. Tess retains that feedback and adds a prominent cutover note to the current instructions. She does not report that every legacy message was removed.

Review actual delivery and the final balance

The 23 November session is held once in Coachful. Tess checks the actual appointment record and the linked credit use. Seven of the original ten sessions have now been delivered: six in the legacy record and one in Coachful. Three remain unbooked.

The closing balance satisfies ten equals six legacy deliveries plus one new delivery plus three remaining. There are no future Acuity appointments and no second active old booking route. Historical payment evidence still belongs to the original purchase.

Tess keeps a small mapping record rather than combining counts from two dashboards without their definitions. The scheduling transition is complete for this package, but the three remaining sessions are still owed. No coaching-outcome or universal administration-saving claim follows from the migration.

Resolve exceptions against the same ten-session obligation

Consider an alternative to the actual case: Owen cancels the 9 November appointment within a policy that restores its booking value. The correct closing figures would then be five sessions held, none reserved and five unbooked. A five-credit replacement grant could preserve ten total; Tess’s actual four-credit grant would be one short. This is a different scenario, not an extra event added to the completed record above.

If Owen instead reschedules that appointment beyond 15 November, it remains a future commitment. Tess must reconsider the shutdown date or agree a deliberate appointment transfer, including its meeting instructions, reminders and credit treatment. She cannot call the appointment delivered to make the original cutover plan balance. Keep the changed booking identifier beside the revised count so another staff member can trace the decision.

If the new client route fails after closure, do not ask Owen to buy again or issue another four credits as a workaround. Tess’s agreed private conversation is the first help channel. She checks his existing credits and the failed step, then replies there with the next action. An appointment is not described as confirmed until its authoritative booking exists and both parties have its details. Until then, the specific booking remains pending; the original entitlement remains owed.

This approach separates a technical inconvenience from a commercial correction. A repeated button click, stale email or failed notification is a reason to investigate the record, not evidence that the client has gained or lost another session.

Handle timezones, changes and reminders as separate checks

Store the date and a named city-based zone, not only an offset. The relationship between London and New York changes during parts of the year when daylight-saving transitions differ. Moving a display zone during travel should not unintentionally move the underlying appointment.

For a change, begin in the system that owns the actual appointment. Check the old event, new event, client notification and entitlement consequence. Editing an external calendar copy alone can leave the source booking unchanged.

Review reminder delivery separately from booking success. In Coachful, workspace reminder timing is controlled in Communications > Notification settings, with the supported choices. A session’s channel settings remain subject to the workspace’s connections, master switches and recipient consent.

Cancellation policy, restored credit and money are also separate. A configured cancellation deadline is not an automatic card charge, and returning a credit is not a cash refund. Do not promise a refund without the actual financial result.

A contrasting practice: recurring payment keeps the move pending

Another fictional coach, Leila, has clients whose monthly Acuity subscriptions fund recurring bookings. She has not agreed the replacement payment route with them. Their saved payment method and renewal terms are not a portable consent to a new charge.

Leila decides not to cancel the source subscription or issue duplicate recurring access yet. She inventories the actual mandates, paid-through periods, future appointments and cancellation behavior, then seeks the appropriate payment and client agreements.

The scheduling configuration can be prepared, but the client transition remains pending. That is the completed decision in this contrasting case. It would be inaccurate to call the migration finished merely because a new booking page exists.

A billing transition requires its own record of approved terms, actual old-billing stop, new client approval, collection and access. Do not copy Owen’s one-time prepaid approach into a recurring service without that work.

Use a release checklist with observable conditions

1. Service fit: the actual session types, hosts, meeting arrangements and client access work in the selected configuration.
2. Entitlement: purchased, held, reserved and unbooked units reconcile, with cancellation and expiry exceptions preserved.
3. Calendar behavior: selected busy calendars, event publishing and source-owned changes have been checked.
4. Legacy commitments: existing appointments retain an owner, instructions and required reminders until delivered or deliberately migrated.
5. Old route: website buttons, current instructions and any still-bookable old route have an explicit cutover treatment.
6. Client evidence: the person can use the correct route and knows where to get help; a sent message alone is insufficient.
7. Financial separation: no duplicate sale, invoice, subscription or cash record is inferred from a migration grant.

A failed condition pauses the relevant part of the transition. A staged overlap can be a reasonable cost of preserving commitments; keep it in the plan rather than hiding it inside a promised instant saving.

Keep preparation connected without expanding the service

Use a short optional preparation resource if it serves the actual coaching. Tess can deliberately deliver a worksheet asking Owen which situation he wants to discuss and what changed since their last session. The intended audience is Owen and Tess, the sole authorized coaching staff member.

The client’s private Coachful conversation supplies the named booking-help route. A submitted worksheet is not automatically attached to every appointment or turned into a task. Discuss it, then explicitly select any action that belongs in the coaching plan.

Keep sensitive details out of public calendar titles and shared event descriptions. A neutral session name and the correct meeting link can identify the appointment without exposing the personal topic.

For a wider client-work comparison, see managing coaching clients without Paperbell. Explore Coachful’s features for the integrated workflow beyond booking.

Frequently asked questions

Does Acuity support packages and calendar connections?

Yes. Its current documentation describes both, along with subscriptions and exports. Compare the actual configurations instead of assuming a missing capability.

Does exporting a CSV import appointments into Coachful?

No automatic import is claimed here. The case retains legacy history, reconciles the balance and deliberately grants the remaining access through a supported workflow.

Should clients recreate existing appointments?

Avoid unnecessary duplication. Preserve the existing source booking or agree a deliberate migration with notifications and entitlement checked. The case leaves two appointments in Acuity until they are held.

Does granting session credits mean a payment was collected?

No. A nonbilling grant supplies access. Historical purchase evidence and any actual new payment need their own records.

When can I cancel the old scheduler?

After checking the actual billing arrangement, future appointments, reminders, editing needs, client balances and remaining dependencies. The case’s end-of-period Squarespace-managed route is not a universal instruction for every account.