> 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/chili-piper.md).

# Migrate from Chili Piper

Rebuild Chili Piper routing, scheduling, and handoff journeys in Distro.

Start with one journey: a demo form, a CRM assignment flow, or an SDR-to-AE handoff. Rebuild it in Distro, verify the result, then switch its source.

Chili Piper also uses the name **Distro** for its record-routing product. In this guide, **Distro** means the product you are moving to; **Chili Piper Distro** means the product you are replacing.

## Find the Distro equivalent

These are starting points for rebuilding your setup. Review the settings behind each one before switching.

| In Chili Piper                    | Set up in Distro                                                       |
| --------------------------------- | ---------------------------------------------------------------------- |
| Concierge web-form scheduling     | New form submission workflow, a form connection, and Show Scheduler.   |
| Chili Piper Distro record routing | CRM-triggered workflow, assignment, and explicit CRM owner updates.    |
| Handoff                           | Browser extension workflow or a booking link for the intended host.    |
| ChiliCal scheduling links         | Event types and personal or shared booking links.                      |
| Teams and Distributions           | Queue membership and a routing profile for Records, Meetings, or both. |
| Ownership rules                   | CRM matching followed by an owner rule or CRM record owner scheduling. |
| Rules without ownership           | Ordered rulebook conditions or workflow Branch paths.                  |
| Meeting types                     | Event types, including hosts, questions, timing, and messages.         |

See Chili Piper's [product catalog](https://help.chilipiper.com/hc/en-us/categories/29182155306259-Chili-Piper) and [distribution settings](https://help.chilipiper.com/hc/en-us/articles/29260564275603-Setting-up-your-Distributions) when recording the setup you want to keep.

## Rebuild a Concierge journey

{% stepper %}
{% step %}

### Prepare hosts and distribution

Follow [Admin setup](/get-started/admin-setup.md). Reconnect calendars, conferencing, and the CRM. Check each member's CRM identity.

Create a [routing profile](/routing/profiles.md), then a [queue](/routing/queues.md). Record the old distribution's weights, availability exclusions, and credit behavior; configure the intended Distro settings explicitly.
{% endstep %}

{% step %}

### Keep your website form

Create a **New form submission** workflow and [connect the existing form](/forms/existing-forms.md). Map the actual website fields and approve the staging and production origins separately.

Use the original form provider's confirmed-success callback. A click on Submit should not start scheduling when the original form fails.
{% endstep %}

{% step %}

### Route and book

Match the CRM record before using its owner. Put ownership rules above new-lead distribution in a [rulebook](/routing/rulebooks.md).

Use **Earlier assignee** in Show Scheduler after Apply Rulebook has selected a member. For a flexible pool journey, use a queue directly with **Any available member** so the host is chosen for the booked time.

Connect **Booked** to confirmed-meeting actions and **Not booked** to the intended follow-up. Add a deliberate path for unqualified leads and unusable owners.
{% endstep %}
{% endstepper %}

## Move record routing and handoffs

For Chili Piper Distro flows, recreate the CRM object and trigger conditions first. Assign the member, then write the appropriate CRM owner field using the provider's owner identity. Showing a scheduler is a separate, visitor-facing journey.

For Handoff, use a [browser extension workflow](/workflows/extension.md) when sellers need qualification and routing. A personal booking link is suitable when the receiving host is already known. Map the prospect as the guest; the seller starting the flow is not automatically the attendee.

## Review before switching

Check caps, SLA reassignment, custom-object matching, and any chat journey separately. A similarly named routing setting does not establish the same behavior.

Test an existing owner, a new qualified lead, an unavailable host, an unqualified lead, a failed form submission, and a successful booking. Verify the CRM activity and messages as well as the calendar event.

Finish with the [source switch checklist](/migrate-to-distro.md#switch-one-source-at-a-time). Old Chili Piper links, credits, and booking-management credentials need their own transition plan.


---

# 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/chili-piper.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.