How to migrate from Calendly to Cal.com

Move booking pages from Calendly to self-hosted Cal.com: list event types and links, connect calendars, rebuild each page, swap every link, close Calendly last.

Start with one workloadThe steps

Written for
The engineer who will do the work
Or run by Pilae
At a fixed price, then operated

In short

  • Cal.diy, the MIT edition of Cal.com that Pilae runs, has no Calendly importer: each person connects their calendar and recreates their availability and event types.
  • Meetings already booked through Calendly stay in the host’s calendar, which Cal.com reads as busy time, so no booking needs importing to prevent double bookings.
  • Links on calendly.com cannot be redirected, so every published link is listed and replaced, and each Calendly event type points to its new page until the account closes.
  • Calendly is cancelled last, once no new bookings have arrived there for a full cycle and the last meeting booked through it has taken place.
On this page (9)

Moving from Calendly to Cal.com is a rebuild, and a small one per person. Cal.diy, the edition of Cal.com that Pilae runs, has no Calendly importer, and little needs one: an account holds event types, availability and calendar connections, and the meetings themselves are already in everyone’s calendar. What takes planning is the links. Every booking link in a signature, on the website or in an old email points at calendly.com, and none of them can be redirected. This guide covers the order we do it in.

Why teams move from Calendly to Cal.com

Three reasons come up most often.

  • Who reads the calendars. A scheduling tool reads every free and busy slot of everyone who uses it, and keeps the name, email and answers of everyone who books. With Cal.com on your own machines, that stays in a database you hold, in the location you choose.
  • Booking pages on your domain. Calendly links live on calendly.com. Cal.com runs on a hostname of yours, so a link printed today can still be pointed somewhere else later.
  • No fee per person. Calendly prices by seat and plan. Cal.diy is MIT-licensed with no fee per user, so giving a colleague a booking page means creating an account, not changing a plan.

What you give up is team scheduling and the parts of Calendly built on it. Cal.diy covers personal booking pages, event types, availability and calendar sync. Round-robin and collective events, routing forms, workflows and SAML sign-in are in the commercial Cal.com product only, and step 2 is where you find out whether that matters to you. You also take on running the service, which is the part Pilae carries.

Before anyone creates a page, find out what Calendly is doing today. Three lists cover it.

  1. People and event types. For a handful of users, read them off each person’s scheduling page. For more, use the Calendly API with a personal access token created by an organisation admin, which reaches the data of everyone in the organisation. The organisation memberships give you the users. Each event type comes with its name, slug, duration, locations, booking questions, whether it is secret, and its kind and pooling type, which is where round-robin and collective events show up. Availability schedules and routing forms come from the same API.
  2. What actually gets booked. On paid plans, Calendly’s Calendar page exports meetings as CSV: filter by date and team member, then select Export. The file holds each invitee’s name, contact details and time zone, the event type, date and location, UTM parameters and payment details. Sort it by event type. Pages nobody has booked in months are not rebuilt.
  3. Where the links are published. Email signatures, the website and any Calendly embeds on it, email and proposal templates, CRM snippets, social profiles, forms and auto-replies. Add every integration that receives Calendly data: webhook subscriptions are listed through the API, and each CRM or other connection needs someone who knows what it feeds.

The CSV holds personal data about everyone who booked. Keep it under the same retention rules as the rest of your customer records.

Step 2: check team scheduling and what has no counterpart

Go through the event type list with the people who use it. Most event types map directly. A few do not, and those decide the plan.

Calendly Cal.com (Cal.diy)
One-on-one event type Event type
Group event type Event type with seats
Round-robin or collective event type Not in Cal.diy: it needs teams
Availability schedule Availability schedule
Booking questions Booking questions, on the event type’s Advanced tab
Buffers, minimum notice, daily limits The event type’s Limits tab
Secret event type Hidden event type
Zoom, Google Meet, Teams or Webex location The same conferencing app, connected by each person
Stripe or PayPal payment The Stripe or PayPal app on the event type
Workflows (email and text reminders) Not in Cal.diy: booking webhooks to n8n
Routing forms Not in Cal.diy
Inline, pop-up widget and pop-up text embeds Inline, floating button and pop-up on click embeds
SAML single sign-on Not in Cal.diy: local accounts

Where an event type is round-robin or collective, or a routing form sends leads to a sales team, settle how those meetings will be booked before anyone moves. The answer may be a personal page for each member of the team, or the commercial Cal.com product, whose own Calendly importer also brings bookings and the questions of routing forms across, though not their routing rules. Either way it is decided now, not discovered after the switch.

Step 3: set up Cal.com, accounts and calendar connections

Cal.com has to be reachable by the people who book, so unlike most internal tools it has a public hostname for its booking pages. Pick that hostname now: it goes into every link you publish in step 5.

  • Calendar apps in your own tenant. Google Calendar connects through an OAuth client created in your own Google Cloud project, with the Calendar API enabled. Microsoft 365 and Outlook connect through an app registration in Entra ID. CalDAV covers Nextcloud and other standard servers. The registrations are yours, and you can revoke them without asking anyone.
  • Conferencing apps. Zoom needs an OAuth app of its own. Google Meet rides on the Google Calendar connection, and Microsoft Teams needs a work or school account. Daily and Webex are also available.
  • Outgoing mail. Confirmations, reschedules and cancellations go to invitees through your SMTP relay, from your own domain.
  • Accounts. Cal.diy has no single sign-on, so staff get local accounts. Create them as an administrator under Settings, Admin, Users, and turn public sign-up off. Give each person the username they had on Calendly: the new link is then the old one with the host changed.

Then each person connects their calendars under Settings, My account, Calendars: every calendar Calendly checked for conflicts, and the one new bookings are written to. Video accounts are connected under Conferencing in the same menu.

Step 4: recreate availability and event types

Start with availability, because every event type uses it. Recreate each schedule with its working hours, time zone and date overrides, then the event types, most-booked first.

  1. Keep the slug. With the same username and the same slug, the new link differs from the old one only in its host, which turns step 5 into a find-and-replace.
  2. Copy the settings from your list: title, description, duration, location, buffers, minimum notice and limits, booking questions, and seats for group events. Secret event types become hidden ones.
  3. Add payments where the Calendly event took them, through the Stripe or PayPal app.
  4. Rebuild reminders outside Cal.com. Cal.diy sends confirmations, reschedules and cancellations, but it has no workflows. Reminders and follow-ups that Calendly workflows sent are rebuilt in n8n, started by Cal.com’s booking webhooks under Settings, Developer, Webhooks. Calendly workflows keep running for the meetings booked there, which is what you want during the parallel period.
  5. Book it. From an outside address, book a slot, then reschedule and cancel it. Check that the event lands in the right calendar with its video link, that the emails come from your domain, and that a meeting booked through Calendly blocks its slot.

Help each person with their first event type. The rest usually follow the same pattern.

Work through the list from step 1, one place at a time.

  • Signatures and templates. Replace each calendly.com address with the new one. Where usernames and slugs were kept, the change is the host.
  • Website embeds. Replace each Calendly embed with a Cal.com one. The shapes match: a page inline, a pop-up opened by a click on an element of your page, and a floating button.
  • Your own redirects. Where a link on your website or a short link of yours redirected to Calendly, point it at Cal.com. From now on, publish booking links through your own domain, so the next change is one redirect rather than a search through every signature.
  • The old pages. Addresses on calendly.com cannot be redirected. Edit each Calendly event type’s description to give its new address, so anyone arriving from an old email or a printed proposal finds the way. Keep the Calendly page bookable during the parallel period: a meeting booked there is still a meeting.

Step 6: run both, then close Calendly

The two run side by side until Calendly has gone quiet. Meetings booked on either side land in the same calendars, and each tool reads those calendars for busy times, so nothing is booked twice.

The cutover, in order

  1. Both open: New links are published, and each Calendly page carries a line pointing to its replacement.
  2. Watch Calendly: Any booking that still arrives there reveals a link you missed. Find where it came from and replace it.
  3. Quiet cycle: Wait until no new bookings have arrived on Calendly for a full cycle, monthly and quarterly meetings included.
  4. Last meetings: Invitees reschedule and cancel through their Calendly emails, so the account stays until the last meeting booked through it has taken place.
  5. Close: Take a final CSV export of meetings, then cancel the subscription.

Cancelling a paid Calendly plan switches the account to the free plan at the end of the billing period, and the free plan allows one event type. Deleting the account removes all its information and cannot be undone, so take the final export first.

Running Cal.com in production

A booking service is small, but it holds credentials for everyone’s calendar.

  • PostgreSQL holds users, event types, availability, bookings and the tokens for connected calendars. It is the one thing that has to come back after a restore.
  • The encryption key protects the CalDAV and other password-based calendar credentials in the database. Keep it apart from the database and in a backup of its own: a database restored without it leaves those calendar connections unusable.
  • A public booking page, a private admin side. Booking pages answer on the internet. The machine and its database do not need to.
  • Updates. Cal.diy comes without warranty or vendor support, and upstream recommends it for personal, non-production use. Each release wants a tested path and a way back.

Pilae operates Cal.com this way: booking pages through one hardened gate on port 443, the machine and its database on your private network, daily encrypted backups in the country your contract names with the key stored separately, and on Enterprise a restore test every month recorded in the console. Upgrades go through the Pilae Agent, tested on a copy of your data and applied in your window. It runs on your premises or on dedicated machines in Pilae Cloud. If you are still comparing, see our page on Calendly alternatives.

Let Pilae run the move

Pilae runs Calendly to Cal.com migrations at a fixed price: the inventory, the check on team scheduling, the setup with calendar registrations in your own tenant, the first event types with each person, the link swap and the parallel period. Then we operate Cal.com with backups, monitoring and updates. See migration services for what the fixed price covers, or tell us how your teams book meetings and we will scope it.

Questions

Can Cal.com import our Calendly account?

Not in the edition Pilae runs. The commercial Cal.com product has a Calendly importer for availability, event types with their questions, routing form questions and bookings, but its code is not in Cal.diy, the MIT-licensed edition we deploy. Each person recreates their availability and event types, working from a list taken through the Calendly API.

What happens to meetings already booked through Calendly?

They stay where they are. Calendly wrote each one into the host's calendar, and Cal.com reads that calendar for busy times, so the slots stay blocked and nobody is double-booked. Invitees reschedule or cancel through the links in their Calendly emails, which is why Calendly stays open until the last of those meetings has taken place.

Do round-robin, collective events and routing forms work?

Not in Cal.diy. Teams, and with them round-robin and collective events, as well as routing forms, workflows and SSO, are in the commercial Cal.com product only. The inventory finds the event types that depend on them before anyone moves, and we say so before you sign if your scheduling needs something else.

Is Cal.com open source?

The Cal.com product has been closed source since April 2026. The public repository continues as Cal.diy, an MIT-licensed fork with the enterprise code removed, and that is what Pilae operates. It has no licence fee and no restriction on running it for your organisation. Upstream recommends it for personal, non-production use; we run it with pinned versions, backups, monitoring and tested upgrades.

How long does a Calendly to Cal.com migration take?

It depends on how many people book through Calendly and how many places their links are published, not on the amount of data. The inventory in step 1 settles both. Pilae quotes the setup, the rebuild of event types, the link swap and the parallel period as one fixed price once the inventory is done.

Let us run the move for you

An inventory, a parallel run and a cutover plan, at a fixed price. Then we operate the app.

Start with one workload

  • Go deeperSaaS migrationA fixed-scope migration off Google Workspace, Microsoft 365, Zapier, Airtable and ChatGPT to open-source apps, with a parallel run and a cutover plan.
  • CheckManaged operationsPatching, daily encrypted backups, monitoring and incident response for your open-source apps, under an SLA with an availability commitment of up to 99.9%.