Keep the original export
Save an unchanged Meetings CSV so every migration decision can be checked against the source.
Calendly migration guide
Move from Calendly to StudioDock without rebuilding your history blindly
A practical CSV-first path for podcast, photo, video, and recording studios moving from meeting scheduling to a booking operation: export the Meetings data, map event labels to spaces, validate a sample, and cut over future bookings on purpose.
The guide is public. Importing is an authenticated admin workflow; Calendly is handled as a generic CSV source rather than a dedicated importer.
Before you export
Treat Calendly event types as source labels, not destination rooms
Calendly is organized around event types, hosts, and availability. StudioDock is organized around spaces, booking rules, add-ons, payments, and customer flows. Write the destination space list first so a convenient event name never silently sends a booking to the wrong room.
Confirm the studio timezone
Review combined start and end datetimes against the timezone used by the studio before validating future bookings.
Separate setup from history
Recreate availability, buffers, routing, workflows, links, and integrations as a new operating setup rather than forcing them into booking rows.
Exact Calendly-to-CSV mapping
What to map in StudioDock’s generic importer
Calendly’s Meetings export can include invitee, event, status, tracking, and payment context. The generic importer does not require every optional column, but it does require a source space label and usable start time for each row.
Swipe horizontally to review each mapping detail.
| Calendly export field | StudioDock field | How to use it |
|---|---|---|
| Invitee name / First name / Last name | Guest name | Map a combined name when the export has one, or map first and last name separately in the generic importer. |
| Invitee email / Email | Guest email | Keep the contact address attached when the Calendly export includes it. |
| Invitee phone / Phone | Guest phone | Optional; only map a phone column when it is present in the export. |
| Event start time / Start date and time | Source start datetime | Use the combined datetime field so the importer can normalize it in the studio timezone. |
| Event end time / End date and time | Source end datetime | Prefer the source end datetime; otherwise map a date, start time, and duration. |
| Event type / Event name | Source type and space name | Use the event type as a source label, then map every label to an existing StudioDock space. |
| Event UUID / Invitee UUID (if present) | External booking ID | Keep one stable source ID when the export provides it so duplicates can be investigated before reruns. |
| Status / No-show status | Booking status | Review cancelled and no-show rows before import; use the importer’s status mapping rather than treating every row as confirmed. |
| Location / Notes / Custom answers | Notes or client notes | Keep useful operating context in notes; do not force routing, workflow, or calendar data into a booking field. |
| Payment details / Amount (if present) | Total price, paid amount, or payment details | Preserve source amounts for review only. Reconcile provider settlement separately instead of recreating a payment. |
Header names vary by export and account configuration. Use the generic field selectors and preview rather than assuming a Calendly-specific preset is available.
The migration workflow
Six checks between Calendly and a clean StudioDock start
1. Export the right Meetings slice
In Calendly, filter the Meetings view to the team members, dates, and statuses that need to move, then export the CSV. Keep the original file unchanged.
2. Separate meetings from the new operating model
List event types, hosts, locations, availability rules, buffers, and active links. These are setup decisions to recreate in StudioDock, not promises of a one-click import.
3. Create destination spaces first
Create the real podcast, photo, video, or recording spaces in StudioDock, then decide which Calendly event type or location should map to each space.
4. Use a generic CSV import
In the authenticated Import & Export area, choose the generic CSV source, upload a small sample, and map the columns above. StudioDock does not currently detect Calendly as a dedicated preset.
5. Review rows before importing
Confirm names, contact details, source start and end datetimes, status, price context, and every source label-to-space mapping. Fix errors before importing the full file.
6. Cut over future bookings deliberately
Validate a future booking in the public StudioDock flow, then replace Calendly links or embeds. Keep the source export for reconciliation during the handoff.
What the product proves
The import flow is explicit about what still needs a human decision
In the authenticated Import & Export area, StudioDock shows the raw CSV, detected source status, field selectors, required mapping warnings, source-space matching, local validation errors, and normalized preview before the import runs. That makes a generic Calendly handoff reviewable without exposing customer data on this public page.
Validate before switching traffic
- Every source event label resolves to the correct StudioDock space.
- A sample has expected names, contact details, times, statuses, and price context.
- Cancelled and no-show history is intentional, not accidental.
- The StudioDock public booking flow works before Calendly links or embeds are replaced.
Related migration resources
Choose the right next step
Migration overview
See the structured, source-aware switch process.
StudioDock vs Calendly
Compare a meeting scheduler with a studio booking platform.
Studio booking buyer checklist
Use a practical decision checklist before changing systems.
Podcast studio workflow
See how a recording business can sell spaces, sessions, and add-ons.
Frequently asked questions
Calendly migration questions
Does StudioDock offer a one-click Calendly migration?+
No. StudioDock currently handles Calendly exports through the generic CSV import workflow. You choose the source columns, map event labels to existing spaces, review the normalized preview, and decide which records should move.
Which Calendly fields should I prepare?+
Prepare invitee name and email, event start and end datetimes, event type or another source label that can map to a StudioDock space, and status. Phone, notes, custom answers, source IDs, and payment details are useful when the export includes them.
Can a Calendly event type become a StudioDock space automatically?+
No. Generic CSV imports require every source space name to map to an existing StudioDock space. Treat an event type or location as a mapping input, review each label, and do not rely on a name match for rooms with similar names.
What does not migrate from Calendly meeting history?+
Do not expect availability schedules, buffers, routing forms, workflows, calendar connections, embeds, subscriptions, or provider settlement history to become StudioDock configuration automatically. Recreate the customer-facing and operational setup separately, then reconcile any money outside the booking-row import.
Should I import cancelled or no-show meetings?+
Only if they are useful for your operational history. Include the status column, review the normalized preview, and start with a small sample. Future bookings and active customer continuity should take priority over importing every old meeting.
Ready to outgrow meeting scheduling?
Start with the workflow your studio actually needs.
Open a trial to set up your spaces, or send the team your Calendly migration question through the asynchronous demo form.