Leaving Acuity Scheduling? Check payments, rescheduling

Acuity Scheduling takes bookings, takes payment, and handles time zones, and plenty of teams still look for something else. The search splits on one question: do you need to qualify the person before they take a slot? We run Fillout on client accounts and can price it from its own pricing page, read on 19 October 2026; the other head-to-heads live on their own pages, linked below.

Pick by what happens before the slot, not by feature list

The scheduling tools that end up in these comparisons all do the same core work: show availability, send reminders, connect a calendar. Once you accept that about them, feature grids stop helping, because they tick the same boxes. What actually separates the tools is what happens before the slot opens. In one case the booking is a bare slot: name, email, pick a time, done. In another case the booking needs a form first, because whoever takes the call has to know whether the person is worth the call. And in a third case you just want the simplest possible link to send around, nothing attached.

If you are in the second case, the form and the booking should be one object, not two pages. That is the whole case for Fillout, and it is the case this article prices. If you are in the first or third case, the choice is simpler and cheaper than most comparison posts make it look. We keep everything we run in the forms and booking category, so you can see the full set in one place.

Check payment and rescheduling rules before leaving Acuity

Before you move, be clear about what you would be giving up. Acuity's core job is taking a slot, taking the payment for that slot, and keeping the calendar straight across time zones. If paid sessions and client self-rescheduling are the backbone of your business, those two behaviours are the ones to audit in any replacement, because they are the ones clients notice when they break.

Payment first. If clients pay at booking, the replacement has to charge at booking, on the same link, without a second checkout. Test it with a real card before you migrate anything, not with the vendor's demo. Rescheduling second. Acuity lets clients move their own sessions within rules you set. Some alternatives hide that behind an email exchange, which quietly turns your assistant into a calendar clerk. Ask the vendor specifically: can the client move the slot themselves, and can I limit how late they do it?

The prices in this piece are Fillout's, read on a stated date from its own pricing page, and they sit below. The sister comparisons carry their own dated numbers, read the same way, on their own pages. If your decision is purely on price, start there.

Use Fillout when the booking needs a form first

Leaving Acuity over this means accepting that the slot itself was never the problem. The problem is that a slot books anyone. Fillout's booking page puts the qualifying questions in front of the calendar, so the meeting only gets created after the answers are in, and those answers travel with it. Nobody has to open a second tab or match a form submission to a calendar entry; the caller reads the context on the meeting itself.

The money side, read on fillout.com/pricing on 19 October 2026: the free tier is genuinely free at $0 per month, unlimited seats, unlimited forms, 1,000 responses a month. Starter lifts that cap to 2,000 for $15 per month billed annually ($180 a year), or $19 billed monthly. Pro takes you to 5,000 responses at $40 per month billed annually ($480 a year), or $49 billed monthly, and Business is $75 per month billed annually ($900 a year), or $89 billed monthly. Two details matter for a booking link: a busy month doesn't cut you off, forms keep collecting and the count resets on the 1st, and subscriptions can be cancelled at any time.

On our own accounts, Fillout is one of three integrations writing into our CRM through the API, alongside n8n and Praiz, and it creates the record when the form is submitted. That is the usage we can vouch for. When a before-and-after on our own accounts produces a usable figure on how qualifying questions change who shows up, this section will carry it with its date.

The limits cut both ways. A booking that needs nothing but a name and an email gains nothing from a form-first tool; a plain builder does it free. And a large sales org running territory rules on its calendar needs a dedicated scheduling product, because Fillout's round-robin, which assigns who takes the call without anybody arbitrating by hand, stops short of that. Qualify and book on one page goes deeper.

Compare the alternatives where the numbers are dated

A comparison table is only worth publishing when every row carries a price read on a dated page, and this piece puts its dated numbers on one tool: Fillout, free forever at $0 with 1,000 responses per month, Starter at $15 per month, Pro at $40, Business at $75, all billed annually. The other head-to-heads live on their own pages, each priced the same way from dated readings: start with Calendly alternatives for bookings that need a form first, which covers the same decision from the Calendly side.

Whichever side you are on, the question that settles the plan tier is monthly response volume. On our accounts, Fillout writes into the CRM through the API on every response, so the responses a form collects are records your team then works. If the slot is enough without the form, the Calendly-side comparison settles it on price instead.

Migrate your booking links without losing paid sessions

The migration itself lives or dies on exports. The one that bites hardest is upcoming paid sessions: export them with the payment status attached, or you will be reconciling who paid by hand during the switchover. Rescheduling rules migrate badly too, because they rarely carry over automatically and clients notice immediately, so copy them across by hand rather than assume. Alphabetically last in nobody's checklist but first in cost when forgotten: every booking link embedded in a website, a email signature, or a social profile needs redirecting, and the ones you forget are the ones generating bookings.

If you land on Fillout, the move is simpler than most migrations because the form travels with the booking: you rebuild the qualifying questions once, connect the calendar, and the submissions start writing wherever you point them. On our accounts, Fillout writes into the CRM through the API on every response, which is the pattern we would reproduce on a new account from day one rather than retrofitting. Run both booking pages in parallel for a couple of weeks, keep the old link live until the new one has taken real bookings, then retire it.

One last check before you commit: whatever you choose, confirm on the vendor's own pricing page, on the day you decide, what the free plan stops at and whether the displayed price is billed annually. That single check is the difference between a comparison you can act on and one you will redo in a month.