Migrating from Cal.com
Switching from Cal.com?
We made the wire short.
Cal.com went closed-source in 2026 and taxes every paid booking — Slotsy is pay-once, your own Stripe key with zero platform fee, and we operate it so you're not the SRE on your own scheduler.
Side by side · Cal.com vs Slotsy
The diff, line by line.
| Cal.com · subscription | Slotsy · $49 once | |
|---|---|---|
| Pricing model | Monthly subscription, per seat | Lifetime deal on AppSumo |
| Payment fee | Stripe Connect + 0.5% + $0.10 / booking | Your own key · zero platform fee |
| Open source | No longer — went closed-source Apr 2026 | Closed, but data export is one click |
| Self-hosting | Managed is cloud-only; the public fork is stripped | We operate it for you |
| Custom domain | Organizations tier ($28/user) | Available on Agency |
| Custom email sender | Organizations tier only | Your own domain, all paid tiers |
The migrate · three steps · ~15 minutes
No double-booking. No DNS panic.
- Step 1
Recreate your event types in Slotsy
Set up your event types, durations, and availability fresh. There's no auto-importer at v1 — most setups port over in a few minutes. Your Cal.com instance can stay running the whole time.
- Step 2
Connect your calendar
Link Google Calendar (bookings appear in it, and its busy times block your slots) or paste an iCal feed URL so Slotsy reads your existing busy times and you won't double-book during the switch.
- Step 3
Switch your link
Point your booking link and any embeds at your Slotsy page. On Agency, CNAME book.your-brand.com and Cloudflare auto-provisions the TLS cert. Flip over when you're ready.
Ready to migrate?