> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/migrate-to-distro.md).

# Migrate to Distro

Move your routing and scheduling journeys from Chili Piper, RevenueHero, Default, or Cal.com to Distro.

Keep the journeys your team relies on: qualify a lead, find the right owner, offer a meeting, and follow up. Start with one journey, rebuild it in Distro, and test it before switching traffic.

## Choose your current product

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><strong>Chili Piper</strong></td><td>Rebuild form scheduling, record routing, and seller handoffs.</td><td><a href="/migrate-to-distro/chili-piper.md">Migrate from Chili Piper</a></td><td><a href="https://1584026818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV2wz5iuVqF38uyorXQp5%2Fuploads%2FEQvWVFslhl70isnK7yCH%2Fdistro3-form.webp?alt=media">distro3-form.webp</a></td></tr><tr><td><strong>RevenueHero</strong></td><td>Move inbound routers, campaign journeys, and Relays.</td><td><a href="/migrate-to-distro/revenuehero.md">Migrate from RevenueHero</a></td><td><a href="https://1584026818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV2wz5iuVqF38uyorXQp5%2Fuploads%2Fy3mbFOBJigsejsOhz7Nb%2Fdistro3-queue.webp?alt=media">distro3-queue.webp</a></td></tr><tr><td><strong>Default</strong></td><td>Recreate queues, routing policies, forms, and workflows.</td><td><a href="/migrate-to-distro/default.md">Migrate from Default</a></td><td><a href="https://1584026818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV2wz5iuVqF38uyorXQp5%2Fuploads%2F7kcPURcldgL3DldTwRGY%2Fdistro3-workflow.webp?alt=media">distro3-workflow.webp</a></td></tr><tr><td><strong>Cal.com</strong></td><td>Move booking events, team scheduling, and routing forms.</td><td><a href="/migrate-to-distro/cal-com.md">Migrate from Cal.com</a></td><td><a href="https://1584026818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV2wz5iuVqF38uyorXQp5%2Fuploads%2FEXoO5bJigqAN1OiIcMR7%2Fdistro3-calendar.webp?alt=media">distro3-calendar.webp</a></td></tr></tbody></table>

Already using Distro's older routers? Follow [Move from the old routers](/migrate.md) for the Form Router, Outbound Router, and Click Router guides.

## Before you rebuild

Record the current form fields, entry URLs, rule order, owner matching, receiving teams, weights, availability, event settings, and follow-up actions. Include what happens when nobody matches or the visitor does not book.

Use [Admin setup](/get-started/admin-setup.md) to connect your CRM, calendar hosts, and providers. Review [Feature availability](/get-started/availability.md) in the workspace you will use for live traffic.

These guides describe how to rebuild configuration. They do not provide a one-click import of another platform's workflows, credentials, distribution history, bookings, or URLs. Record any requirement to preserve those items before deciding how to switch.

## Test the whole journey

Validate and simulate the workflow's paths, then run a controlled test through the actual source once live execution is available.

| Case                                 | What to check                                                                 |
| ------------------------------------ | ----------------------------------------------------------------------------- |
| Existing customer                    | Correct CRM record, mapped owner, and fallback when the owner cannot be used. |
| New qualified lead                   | Intended queue, event, and host selection timing.                             |
| Missing data or unqualified lead     | Deliberate fallback, follow-up, or redirect.                                  |
| Busy or paused host                  | Intended availability exclusions and fallback.                                |
| Successful booking                   | Calendar event, conferencing, guests, CRM activity, and messages.             |
| Visitor leaves without booking       | Intended Not booked action.                                                   |
| Form provider rejects the submission | No workflow start from an unconfirmed success.                                |
| Personalized campaign                | Correct recipient identity and a separate session for each prospect.          |

Simulation checks your configuration using samples. A real test checks the website integration, calendar, CRM writes, and provider requests. See [Test, publish, and versions](/workflows/test-and-publish.md).

## Switch one source at a time

* [ ] Save the old settings, embed snippets, and destinations so you can restore the source if needed.
* [ ] Publish the Distro workflow and confirm it is On and live execution is available.
* [ ] Activate the correct published version on the form or trigger connection.
* [ ] Replace the old capture handler, embed, API caller, or campaign destination for this journey.
* [ ] Confirm only one integration owns the form submission and its scheduling response.
* [ ] Complete a controlled acceptance test after the source switch.
* [ ] Review workflow Logs, queue usage, bookings, and CRM activity for duplicates or unexpected results.
* [ ] Tell sellers which links and meeting-management controls to use.

Keep access to the previous platform for existing bookings, old management links, and in-flight journeys until their transition is resolved. Moving new traffic does not transfer those items automatically.

A rollback switches the source back deliberately. It does not undo CRM changes, messages, or bookings already completed in Distro.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/migrate-to-distro.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.