Event types
Each Calendly event type re-creates as a YionStack booking offering with its duration, buffer time, location, description and meeting questions intact.
Move from Calendly
Your event types and bookings — connected to the deal, the invoice and the calendar.
Export your Calendly invitees and event types, upload them to YionStack, and the booking module re-creates the event types alongside the CRM contact, the deal and the calendar they belong to. See every supported source →
File-based — you upload an export from your old system, we map it. No connection to your old account.
At a glance
scheduling- From
- Calendly
- How
- Upload an export
- Records
- 7 types come across
- Steps
- 3-step migration
- Stays put
- 5 items intentionally
- Residency
- UK (europe-west2)
What lands in your business
The records you depend on, in their right places.
Past bookings
Historical Calendly meetings come across as booking records attached to the right contact. Booking date, duration, host and answers to meeting questions are all preserved.
Invitees
Every Calendly invitee becomes a YionStack contact with source set to "scheduling" and a link back to the booking they made. Existing CRM contacts match on email so duplicates collapse correctly.
Booking links and slugs
Calendly slugs (the public URLs your customers bookmarked) re-create as YionStack booking-page slugs so the existing links continue to work after you add a single redirect rule on your domain.
Availability and working hours
Per-event-type availability windows, working-hours rules and date-specific overrides come across so existing customers see the same slots they were used to.
Payment-collected bookings
For event types that collected a payment through Calendly’s Stripe integration, the historical payment records carry across as booking deposits attached to the booking and the contact.
Webhook subscriptions (as reference)
Your Calendly webhook subscriptions are archived as a reference list. New webhooks are subscribed inside the YionStack booking module, where they can fire on the deal, invoice and calendar events too.
How it works
Three steps. Reversible at any point.
- 1
Export from Calendly
From Calendly, use Account → Data Export to download invitee CSVs and event-type JSON. Both files drop into the YionStack Import surface in one upload.
- 2
Review the mapping
YionStack reads the column headers and the event-type JSON, suggests where each one lands, and proposes a booking-offering definition per event type. You approve or adjust before anything goes live.
- 3
Run the import
The job runs in the migration dashboard. Event types appear in the booking module ready to publish; historical bookings attach to the right CRM contacts; the public slugs are reserved so the redirect rule is the only DNS-side change.
What stays where it is
We are honest about scope.
A migration is not the same as a clone. The records below are intentionally out of scope — either because they belong with the system that produced them, or because their meaning changes once they live inside an operating system instead of a point-tool. You can still reference the originals while you run YionStack alongside.
- —Live Google Calendar and Microsoft 365 connections — re-authorised in YionStack’s calendar module under your own OAuth so the new bookings continue to write to your real working calendar.
- —Stripe payment connection — re-authorised in YionStack’s payments module under your own Stripe account; new booking deposits flow through it directly into the YionStack invoicing module.
- —Calendly workflows (confirmation emails, reminders, follow-ups) — re-author inside the YionStack booking module so they share templates with the marketing module and the CRM.
- —Round-robin pools — re-create as YionStack team-bookings with the same routing rules and the same hosts.
- —Salesforce/HubSpot/etc. routing — re-authorised inside YionStack, where the booking already lives in the unified CRM and the routing rule is simpler than the third-party hop.
Common questions
Straight answers.
Will my existing Calendly URL keep working?
Yes, with a single redirect rule on your domain. The slugs re-create inside YionStack so the existing URLs (calendly.com/yourname/30min) can redirect to your YionStack booking page (yourbusiness.yionstack.co.uk/book/30min) without breaking any bookmarked link.
What about round-robin or collective event types?
Round-robin pools re-create as YionStack team-bookings with the same routing rules and host pool. Collective (multi-host) event types re-create with the same host assignment, and the YionStack calendar module handles the multi-calendar availability check.
Will my Stripe-collected payments come across?
The payment records come across as booking deposits attached to the booking and the contact. The Stripe customer record stays with Stripe — re-authorising the Stripe connection in YionStack lets new bookings continue to take payment, and the deposits flow into the YionStack invoicing module.
Can I run Calendly and YionStack side by side during the cutover?
Yes. The migration is a one-time copy. Keep Calendly live, run YionStack bookings on a second slug for a week, agree the cutover date, then add the redirect rule on the day of the switch.
What about my Calendly webhook integrations (Zapier, custom code)?
Existing webhook subscriptions are documented in the import summary. The YionStack booking module emits the same lifecycle events (booking.created, booking.rescheduled, booking.cancelled) so the same downstream consumers can re-subscribe and the rest of your stack continues to work.
Ready to run your business smarter?
Join thousands of UK businesses already running on YionStack.
- No credit card
- 14-day free trial
- Cancel anytime