Switch from Calendly

Calendly does not offer a one-click "move to Zitli" button—and that is fine. What you need is a checklist of event types, durations, buffers, locations, and team routing rules. Screenshot or note your Calendly setup; you will recreate it in Zitli in under an hour for most solo practices.

Keep Calendly active until your Zitli link is tested. Existing Calendly bookings stay on your calendar. New bookings should flow through Zitli once you update public links.

In Zitli, connect the same Google Workspace or Microsoft 365 accounts you used with Calendly. Authorise two-way sync so busy times from existing appointments block availability immediately.

If you had multiple Calendly users, each person connects their own calendar. Team admins can verify connections before publishing shared booking pages.

Create event types matching your Calendly offerings: duration, buffer before/after, location (video, phone, in-person), and intake questions. This is the moment to enable canton holiday blocking and set the booking page language to DE, FR, IT, or EN.

Team round-robin or collective events map cleanly—assign hosts, set fairness or load rules, and test with an internal booking before going live.

Replace your Calendly URL on your website, email signature, proposal templates, LinkedIn, and Google Business Profile. Use a short redirect from the old link if you control that domain.

Send a one-line note to active clients: "We moved booking to Zitli—same service, Swiss hosting, new link." Most do not notice the backend change if the UX is smooth.

Book a test appointment yourself in each language you offer. Confirm reminders, calendar holds, and video links work.

Compare Zitli vs Calendly on data and pricing if procurement asks. Turn off or downgrade Calendly once two weeks of overlap pass without issues.

Need team routing? Read the round-robin guide next, or see pricing for Team plans in CHF.