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

# Migrate from RevenueHero

Move RevenueHero inbound routing, campaign scheduling, and Relays to Distro.

Rebuild one Inbound Router first. Once its owner matching, distribution, and booking work as intended, use the same approach for your campaign and seller-led journeys.

## Find the Distro equivalent

| In RevenueHero                   | Set up in Distro                                                               |
| -------------------------------- | ------------------------------------------------------------------------------ |
| Inbound Router                   | New form submission workflow with qualification and Show Scheduler.            |
| Matching Rules                   | CRM matching plus rulebook owner rules or CRM record owner scheduling.         |
| Distribution Rules               | Rulebook conditions, queues, and routing profiles.                             |
| Meeting Types                    | Event types with duration, hosts, availability, questions, and messages.       |
| Relays                           | Browser extension workflow for routed handoffs; booking links for known hosts. |
| Campaign Router                  | Hosted lead form or a custom personalized entry journey.                       |
| Personal and Group Meeting Links | Personal or shared booking links with the intended attendees.                  |
| Notification workflows           | Workflow notifications and meeting lifecycle triggers.                         |

RevenueHero's [documentation index](https://help.revenuehero.io/llms.txt) can help you inventory the routers, rules, meeting types, and integrations in your current setup.

## Preserve your round-robin behavior

RevenueHero distinguishes [Strict, Flexible, and Balanced](https://help.revenuehero.io/rules/distribution/round-robin-methods). Record your current method before creating a Distro profile.

* **Strict:** start with **Pre-picked member**, which selects a host before offering their times.
* **Flexible:** start with **Any available member** and **Even rotation**, which offers eligible pooled times and selects the host for the booked slot.
* **Balanced:** review the workload and calibration behavior separately. Even rotation uses Distro's counted assignments and weights; it does not import RevenueHero's workload history or guarantee its balancing algorithm.

Distro attaches the profile to queues. Decide which queues should share a profile and which journeys should share the same queue's rotation history.

## Rebuild an inbound journey

{% stepper %}
{% step %}

### Connect people and systems

Complete [Admin setup](/get-started/admin-setup.md). Reconnect the CRM, calendars, and conferencing; map CRM owners to Distro members.

Create the receiving [queues](/routing/queues.md) and [routing profiles](/routing/profiles.md). Copy the intended roster and weights, then review exclusions and turn refunds.
{% endstep %}

{% step %}

### Recreate the rules

Connect your existing website form to **New form submission** and map its fields. Add enrichment only where the routing decision needs it.

Match the CRM record before reading ownership. Use a [rulebook](/routing/rulebooks.md) with existing-owner rules first, followed by qualified-lead distribution and a deliberate fallback. Check what happens when the owner is absent, unmapped, or unavailable.
{% endstep %}

{% step %}

### Recreate scheduling and follow-up

Choose the event in [Show Scheduler](/workflows/show-scheduler.md). Use **Earlier assignee** after a rulebook has selected a member. For flexible queue scheduling, avoid assigning the member before the prospect chooses a time.

Put confirmed-meeting actions on **Booked**. Configure reminders on the event and check that workflow notifications do not send a second copy.
{% endstep %}
{% endstepper %}

## Move campaigns and Relays

Use a published lead form as the campaign destination when visitors can enter their details. For personalized links, your website or server must validate and map recipient identity into the supported SDK or API journey. Old RevenueHero URL parameters do not automatically become Distro inputs.

See the [campaign entry options](/migrate/click-router.md) and [outbound booking guide](/guides/outbound-booking.md). Confirm reusable-link behavior and expiry before replacing campaign templates.

## Review before switching

Check meeting categories, prospect/company limits, group distribution, scheduler languages, and each CRM integration separately. Recreate only the behavior confirmed in your Distro workspace.

Test matched ownership, no CRM match, paused members, both booking outcomes, and two distinct campaign recipients. Verify owner write-back and meeting activity without duplicate logging.

Use the [source switch checklist](/migrate-to-distro.md#switch-one-source-at-a-time). Keep the previous platform available for existing bookings that still use its management links.


---

# 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/revenuehero.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.