Migration guide
Cal.com → Calendly
Inverse of iteration 121's calendly-to-cal path, and uncommon in the wild: most cost-conscious teams move the other direction. Cal.com Teams is $12/seat (with ~25% annual discount); Calendly Teams is $16/seat (no published annual discount). Cal.com is open-source AGPL-3.0; Calendly is proprietary. The migration only pencils for solo users who fit Calendly Standard at $10/seat (cheapest paid tier in the spine), or for teams where Calendly's larger integration ecosystem and brand-recognition outweigh Cal.com's cost and developer-friendliness. The bad-fit section is intentionally substantive because most readers should stay on Cal.com.
Published · By the TierGauge editorial team
When this migration makes sense
- You're a solo user (1 seat) and Calendly Standard at $10/seat is genuinely cheaper than Cal.com Teams at $12/seat. Calendly Standard remains the cheapest paid scheduling tier in the spine; if you don't need team features, it's the lowest-cost path.
- Your customers and prospects already say 'send me a Calendly link.' The brand-recognition gap is real: 'send me a Cal link' often gets followed by 'wait, like Cal.com? What's that?' If reducing friction in your scheduling links matters, Calendly's vocabulary win is real.
- You depend on Calendly-shaped integrations: Salesforce, HubSpot, Stripe, Zapier connectors that exist on both platforms but feel more polished on Calendly. The integration ecosystem maturity gap is meaningful for sales-team scheduling.
- Your team is non-technical and Cal.com's flexibility-as-feature-surface is friction rather than value. Calendly's setup is more opinionated and gets non-technical users to a working scheduling page faster.
- You want polished workflow templates out of the box (interview-scheduling, sales-call-scheduling, customer-success-cadence). Calendly ships these as templates; Cal.com's equivalent requires more configuration.
When it doesn't
- Cost is a real constraint. Cal.com Teams at $12/seat with ~25% annual discount = $9/seat/mo equivalent; Calendly Teams at $16/seat with no published annual discount. At 10 seats annual that's a ~$840/yr difference. Don't migrate just for brand recognition if cost matters.
- You value the open-source AGPL-3.0 self-host escape hatch even if you'd never use it. Cal.com is the only OSS scheduling tool in the spine; the option to migrate-to-self-hosted-or-fork-the-codebase if vendor terms change is structurally different from Calendly's proprietary lock-in.
- Your team has any developer capacity. Cal.com's API is more developer-shaped (cleaner REST + GraphQL + webhooks); Calendly's API is workflow-shaped and more limiting if you want to embed scheduling deeply into your own product.
- You depend on Cal.com's Routes and Workflows for complex routing logic (round-robin with weighted distribution, custom routing per traffic source, multi-step booking flows with conditional logic). Calendly Routing Forms cover similar ground but with less depth.
- You want booking-engine flexibility for product use cases (embed Cal.com in your app, customize the entire booking flow with React, run multiple booking pages on subdomains). Calendly's embed is more rigid.
- Your team is technical and the cost-plus-OSS combination justifies any vocabulary friction. Most teams that picked Cal.com originally did so for these reasons; the reasons typically don't go away.
What you lose by leaving Cal.com
- Cost advantage at team scale. Cal.com Teams $12/seat (or $9/seat annual-equivalent) vs Calendly Teams $16/seat with no published annual discount. The cost gap compounds at higher seat counts.
- Open-source AGPL-3.0 self-host escape hatch. Cal.com is the only OSS scheduling tool in the spine; the option to fork the codebase or self-host on your infrastructure if vendor terms change is gone after migration.
- Developer-first API surface. Cal.com's REST + GraphQL + webhook combination is meaningfully more flexible than Calendly's API.
- Cal.com Routes and Workflows depth (round-robin with weighted distribution, multi-step booking flows with conditional branches).
- AGPL philosophical alignment for teams that pick OSS-first by principle.
- Active product iteration via the Cal.com open-source community (Cal.com ships fast and accepts community PRs; Calendly's roadmap is closed).
What you gain with Calendly
- Larger integration ecosystem. Salesforce / HubSpot / Stripe / Zapier integrations exist on both, but feel more polished on Calendly for sales-team workflows.
- Brand recognition. 'Send me a Calendly link' needs no explanation; 'Send me a Cal link' usually does.
- More-polished SaaS UX for non-technical users. Calendly's setup flow is more opinionated and gets to a working scheduling page faster.
- Built-in Calendly Analytics: engagement metrics, reschedule rates, no-show tracking, conversion-funnel reporting on the booking flow itself.
- Mature workflow templates: interview-scheduling, sales-call-scheduling, customer-success-cadence ship as starter templates rather than DIY-from-scratch.
- Calendar Connections feature on Teams+ that polls multiple calendars per user without conflicts. Cal.com has equivalent but the UX is less polished.
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 Cal.com, what's the equivalent on Calendly?" gut check.
| Limit | Cal.com (Teams) | Calendly (Standard) |
|---|---|---|
| Team seats | 1 seat (per-seat pricing) | 1 seat (per-seat pricing) |
Step-by-step migration
- 01
Export your list from Cal.com
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 Cal.com provides them.
- 02
Provision Calendly
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. Cal.com-style organization rarely maps 1:1, so plan the split before the upload, not after.
- 04
Rebuild automations and templates
Calendly's automation builder is structurally similar but won't import Cal.com'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 Cal.com announcing the new sender domain and what to expect. Cut over DNS and sending from Calendly on the same day, not staggered. A dual-send week creates more confusion than it prevents.
Cal.com-to-Calendly specific gotchas
Universal steps cover most of the work. These are the failure modes unique to this exact pair.
-
#1
Booking-page URL change: customers have `cal.com/your-handle` bookmarked, in email signatures, and in CRM contact records. Calendly URLs are `calendly.com/your-handle`. Plan a 30-90 day overlap where both URLs resolve; configure Cal.com-side redirect to the new Calendly URL when you decommission the old. Don't hard-cut the booking link.
-
#2
Workflow + Routes rebuild: Cal.com workflows (event-triggered actions, custom routing per traffic source, conditional logic across multiple events) don't 1:1 transfer. Calendly Routing Forms cover the routing case but workflow-execution depth differs. Audit which workflows are actually load-bearing before migration; rebuild only those, not the entire library.
-
#3
Embed-on-website swap: Cal.com's embed script (`embed.cal.com/embed.js`) and Calendly's embed (`assets.calendly.com/external/widget.js`) have different signatures. Update every site embed; verify each renders correctly in production preview before flipping the canonical link in your email signatures and CRM.
-
#4
Calendar-integration reauth: Cal.com OAuth tokens for Google Calendar / Outlook / iCal don't transfer to Calendly. Re-authorize each calendar individually on Calendly. Plan a low-volume booking window for the cutover so any in-flight bookings don't double-book or miss notifications.
-
#5
Custom-domain handoff: Cal.com supports custom-domain on Teams ($12/seat); Calendly supports custom-domain on Teams ($16/seat) but the DNS configuration differs. If you've routed `meet.yourdomain.com` to Cal.com via CNAME, the equivalent Calendly setup uses different target hosts. Stagger DNS cutover with a 30-day overlap.
-
#6
Routing form rebuild: if you use Cal.com Routing Forms for question-based lead routing (different sales-rep based on company size, geo, intent), Calendly Routing Forms are the equivalent feature on Teams+ but the field types and routing-rule UX differ. Rebuild from documentation; don't expect import.
Compare on price across the category
This guide is Cal.com to Calendly specifically. To see both side by side with every other scheduling tool we track on a single price-only table, see the scheduling pricing comparison . Useful before committing to the migration, in case a third option fits the cost-and-feature combination better than either side of this guide.
Common questions
- Is Calendly cheaper than Cal.com?
- 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 Cal.com, how it imports into Calendly, 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 Calendly 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 Calendly models differently from Cal.com.
- Are Cal.com and Calendly 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 Cal.com vs Calendly 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
- Cal.com: https://cal.com/pricing
- Calendly: https://calendly.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.