Move from Calendly to Tapmy bookings

What do I need to note down from Calendly?

| Calendly piece | What to record for Tapmy | |---|---| | Event types | Length, price, capacity, location, description and intake questions | | Availability | Working hours, date overrides, buffers, minimum notice, time zone | | Calendar connection | Which calendar, sync direction, permissions, conflict behavior | | Payments | Whether the booking is free, a deposit, or fully paid | | Notifications | The confirmations and reminders buyers get today | | Public links | Website, profiles, email, QR codes and campaigns that use your Calendly link |

How do I replace my Calendly links with Tapmy bookings?

1. List your active event types. Mark which ones move and which stay in Calendly, for example team scheduling.
2. Create one Tapmy booking with the right length, price, description, availability and buyer questions.
3. Connect your calendar and confirm you own it and have granted the right permissions.
4. Book it yourself from a signed-out browser set to a different time zone. Check payment, the calendar event, the confirmation, the join details and the cancel path.
5. Run a test for double booking and buffers. Tapmy may not cover team or round-robin scheduling, so do not promise it.
6. Swap one low-risk public link first and watch it.
7. Leave Calendly running until every future appointment and reschedule is accounted for.

What does a good result look like?

A buyer picks a time, sees it in their own time zone, pays if needed, gets a confirmation with join details, and nobody gets double booked.

What should I watch out for?

• Calendar sync, buffers, rescheduling and conflict rules deserve a hands-on test.
• Do not cancel Calendly while future events or old reschedule links still depend on it.
• Test around travel dates and daylight-saving changes.
• Team scheduling may have no Tapmy equivalent.

What comes next?

Move booking types one by one. Keep a link back to Calendly until your first real sessions have gone well.