Leaving Neos Meet

A tool you liked can stop fitting — the team changed, the workflow changed, you found something that suits you better. No hard feelings, and no maze. This is the honest guide to moving off Neos Meet and onto whatever comes next, including the tools we compete with. We wrote it because covenant clause §5 says we would: “if you leave, we will help you land.”

What stops working, and when

Cancelling and deleting are two different things, and it is worth being precise about the difference before you do either.

• Cancel or downgrade to Free:nothing is deleted. Your booking links keep working, your event types and history stay put, you simply move to the free plan's limits. This is the reversible move — run Neos Meet and your new tool in parallel for a while, then stop using the Neos Meet link.
• Delete your account: this is the irreversible one. Upcoming meetings are cancelled and invitees emailed, your data is erased, and your booking links stop resolving. Your handle is parked for 90 days rather than handed to anyone else, so an old link can never suddenly point at a stranger; after that it returns to the pool. Take your export first — the download is gone once the account is.
• Old links in the wild: the links in email signatures, calendar invites, and QR codes are the hardest thing to move. On deletion you can supply a forwarding linkto your new booking page; for 90 days, visitors to your parked handle see a “this host has moved — book with them here” link to it. It is a link they choose to click, never an automatic redirect, and it buys you time to swap the links you control.

The move, in the right order

The same playbook works for any destination. Run it in this order and no booking falls through a gap:

• Set up your event types and availability on the new tool, but keep Neos Meet live.
• Swap the links people actually click — email signature, bio links, proposal templates, CRM sequences — to the new page. This is where bookings really come from.
• Let the meetings already on your Neos Meet calendar play out; they are real reservations.
• When nothing new is coming through the Neos Meet link, cancel or delete. If you delete, add the forwarding link so stragglers still reach you.

Mapping your export file to your new tool

None of the tools below has an automated importer for Neos Meet, and neither did we for them — a booking page is a small enough thing to rebuild by hand in fifteen minutes, and the parts that matter (buffers, minimum notice, booking windows) rarely survive an automated import anyway. Your export JSON is the checklist. The sections you will use most:

• event_types — one entry per event type, with duration, location, buffers, minimum notice, booking window, and custom questions. Recreate each on the new tool from this.
• schedules — your weekly hours, timezone, and date overrides. Copy the hours across and double-check the timezone.
• bookings (or the CSV) — your meeting history, if you want it in the new tool or your CRM. Most tools do not import past bookings; keep the file as your record.

Moving to Calendly

Sign up, connect the same Google Calendar, and recreate each event_typesentry as a Calendly event type. Calendly's availability model is one or more schedules, so your schedulessection maps cleanly. Custom questions become Calendly's invitee questions. Round-robin and collective event types map to Calendly's team event types. Calendly cannot import your past bookings; keep the export for your records. See also our side-by-side comparison, which we keep honest in both directions.

Moving to Cal.com

Cal.com is open source, so you can self-host or use their cloud. Connect Google Calendar, then recreate each event_types entry — durations, locations, buffers before and after, and minimum notice all have direct equivalents. Your schedulesbecome Cal.com availability schedules with the same timezone. Booking questions map to Cal.com's booking fields. If you run round-robin, Cal.com's team round-robin is the equivalent, and your team section lists who to invite.

Moving to SavvyCal

Connect your calendar and rebuild each event_typesentry as a SavvyCal link. SavvyCal calls availability “schedules” too, so your schedulessection transfers directly; set the timezone at the top. Its overlay/ranked-times features are extra — you configure them fresh, there is nothing in the export to carry over. Custom questions become SavvyCal's booking questions.

Moving to TidyCal

TidyCal is the simplest destination, which makes the move quick. Connect Google Calendar and recreate each event_types entry as a TidyCal booking type — duration, and any buffer and booking-window settings TidyCal supports. Your scheduleshours copy across; TidyCal's availability is per-booking-type or global, so consolidate if you kept several schedules. Some finer controls (per-event minimum notice, granular buffers) may not have an equivalent — the export tells you what you had so nothing is a surprise.

What does not transfer anywhere

• Your calendar credential. You will connect Google again on the new tool — the token is never in the export, by design.
• Live meeting links already sent. Meetings already on calendars keep their existing Google Meet links; only new bookings use the new tool.
• Recordings and CRM links from the add-ons live in those systems, not in the scheduler; export or move them from there.

Still stuck?

Email support@neos.network with your booking link and, if there is one, the exact time an invitee tried to book. A real person reads it — there is no bot in front of us.