Calendly → Cal.com

Plan mapping at the entry paid tier

The lowest non-free, non-custom tier on each side. Use this for the "if I'm on $X with Calendly, what's the equivalent on Cal.com?" gut check.

Step-by-step migration

1. 01

   Export your list from Calendly

   Pull a fresh CSV of every active subscriber. Capture the fields you actually use downstream: email is required, name is standard, signup date and tier (free/paid) are useful when Calendly provides them.

2. 02

   Provision Cal.com

   Sign up, set sender identity, and verify your sending domain (DKIM, SPF, DMARC). Do this before importing the list; sending from an unverified domain is the single fastest way to land in spam at the moment of cutover.

3. 03

   Import the list and map fields

   Upload the CSV. Map email + name + any custom fields. Decide whether to import as one list or split into segments/tags. Calendly-style organization rarely maps 1:1, so plan the split before the upload, not after.

4. 04

   Rebuild automations and templates

   Cal.com's automation builder is structurally similar but won't import Calendly's flows directly. Rebuild only what you actively use; the move is a chance to delete the unused ones rather than lift-and-shift dead infrastructure.

5. 05

   Send a test broadcast

   Pick a small segment and send a real broadcast (not just a preview). Verify deliverability, link clicks, and unsubscribe flow. If anything's off, you find it before the announcement, not after.

6. 06

   Announce the move and cut over

   Send your last broadcast from Calendly announcing the new sender domain and what to expect. Cut over DNS and sending from Cal.com on the same day, not staggered. A dual-send week creates more confusion than it prevents.

Calendly-to-Cal.com specific gotchas

Universal steps cover most of the work. These are the failure modes unique to this exact pair.

• #1

  Cal.com supports importing Calendly event types directly via its Calendly URL importer. Use this rather than recreating event types by hand. Recurring events and round-robin assignments need a manual review post-import.

• #2

  Existing Calendly booking links (calendly.com/yourname/30min) won't redirect; either set up forwarding from your old domain or send your audience an updated link before retiring the Calendly account.

• #3

  Stripe and PayPal integrations need to be reconnected on the Cal.com side. Test a paid booking in sandbox mode before switching live workloads.

• #4

  Self-hosted vs hosted: the SaaS Cal.com (cal.com) is the easier migration. Self-hosting buys the open-source dividend but requires real infra; don't conflate the two decisions.

Common questions

Is Cal.com cheaper than Calendly?

Both start at the same headline price (Free). The reason to migrate is the pricing model and feature scope, not the entry-tier number.

Will I lose subscribers in the move?

Email lists transfer as raw addresses; subscriber relationships transfer with you because the addresses haven't changed. What you can lose: re-engagement (some readers won't notice the new sender domain immediately), paid subscriptions if Calendly handles billing differently from Cal.com (the gotchas above call out the specific cases), and any "engagement" or warmth signals that Calendly's deliverability inferred from your sending history. Plan a clear announcement and a deliverability warm-up week.

How long does the migration take?

For a list under 10,000 subscribers, a clean migration is one focused week: domain setup and verification, list import, automation rebuild, test broadcast, announcement, cutover. Larger lists or complex automations can stretch to 2 or 3 weeks. The constraint is rarely the import itself; it's the deliverability warm-up and the time to rebuild flows you actually depend on.