Migration guide
Calendly → Cal.com
Calendly's per-seat pricing escalates with team headcount; Teams at $16/seat/mo billed yearly means a 10-person revenue team pays $1,920/yr just to schedule meetings. Cal.com is open-source and runs the same Teams plan at $12/seat/mo (or self-host for free), with SOC 2 + HIPAA on Organizations without the $15k/yr Calendly Enterprise floor.
Published · By the TierGauge editorial team
When this migration makes sense
- You're a 5+ seat revenue or success team paying Calendly Teams or Standard and the per-seat math has started to sting.
- You want SOC 2 + HIPAA + SAML SSO without paying Calendly Enterprise's $15k/yr starting price.
- You're philosophically aligned with self-hostable / open-source tooling and might want the option to self-host later.
When it doesn't
- You're a solo professional and Calendly's Free tier covers you (no per-seat cost to escape).
- You depend heavily on Calendly's brand recognition for booking-page trust (recipients have seen the Calendly UI thousands of times; Cal.com's UI is similar but less immediately familiar).
- Your team is deeply integrated with Calendly's Salesforce lookup routing on Enterprise; Cal.com's Salesforce sync is two-way but less depth at the lookup-routing level.
What you lose by leaving Calendly
- Calendly's brand familiarity on the booking page.
- Salesforce lookup routing depth (Enterprise feature on Calendly).
- Some specialty integrations Calendly's larger ecosystem covers but Cal.com's 100+ apps don't.
- Calendly's mature 24/7 chat support tier on Standard+; Cal.com's support model is leaner.
What you gain with Cal.com
- Lower per-seat pricing ($12 vs $16 at the Teams equivalent).
- Open-source codebase: optional self-hosting and full auditability that Calendly cannot offer.
- SOC 2 + HIPAA + ISO 27001 + SAML SSO on Organizations ($28/seat) without contacting sales.
- More transparent feature progression; fewer 'contact us for pricing' walls in the upgrade path.
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.
| Limit | Calendly (Standard) | Cal.com (Teams) |
|---|---|---|
| Team seats | 1 seat (per-seat pricing) | 1 seat (per-seat pricing) |
Step-by-step migration
- 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.
- 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.
- 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.
- 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.
- 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.
- 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 my data transfer cleanly?
- Most scheduling data transfers, but rarely 1:1. The "Pair-specific gotchas" section above is hand-curated for this exact migration: it covers what exports from Calendly, how it imports into Cal.com, and which structural pieces (workflows, integrations, custom domains) require rebuild rather than direct port. The constraint usually isn't the data export; it's the rebuild work for anything Cal.com models differently.
- How long does the migration take?
- A clean migration for this pair is typically 1-2 weeks of focused work: data export, integration reconnection (CRMs, webhooks, payment processors), feature rebuild for whatever doesn't port directly, test run, cutover. The constraint is rarely the export itself; it's the integration reconnection and the rebuild work for any feature that Cal.com models differently from Calendly.
- Are Calendly and Cal.com direct competitors?
- Yes. Both are primarily scheduling tools, which is why this is a defensible head-to-head migration rather than a cross-category consolidation.
- Where can I see Calendly vs Cal.com side-by-side?
- The /compare/cal-vs-calendly page on TierGauge shows side-by-side plans, headline pricing, included features, and limit comparison at the entry paid tier. This migration guide is the long-form decision narrative; the compare page is the data-only dashboard.
Sources
- Calendly: https://calendly.com/pricing
- Cal.com: https://cal.com/pricing
Pricing verified . Migration mechanics are based on the public pricing pages and standard ESP migration patterns; verify destructive steps (DNS cutover, paid subscription transfer) against the vendor's current docs before executing.