If your assignment rules already live on a webhook or on your CSV import routing, you don't have to recreate them to start using Lead Routing Policies. Bonzo reads the routing you built, translates it into a policy, and shows you the result before anything is saved. Your original routing is left exactly as it was.
Before you start
- You need the Updated Lead Routing Policies and Convert LRP permissions, since converting creates a policy.
- Only webhook routing and CSV import routing can be converted.
- The routing has to be saved. On the CSV routing page, the "Convert to lead routing policy" button is disabled while you have unsaved changes.
- The button doesn't appear on a webhook that is already using a policy.
Converting a webhook's routing
Step 1: Open the webhook
From your dashboard, navigate to Settings → Webhooks and click the webhook you want to convert.
Step 2: Click "Convert to lead routing policy"
The button sits in the top right of the webhook page, next to the delete button.
Step 3: Review the translated policy
Bonzo reads your routing and fills in a full policy form: each routing group becomes a condition group, every assignee is added to the policy's pool, and campaign and pipeline stage outcomes carry across. The policy is named after your webhook, such as "Zillow Leads - Converted Routing."
Nothing has been saved yet. Edit any part of the form the same way you would when building a policy from scratch.
Step 5: Click "Create policy"
The policy is created and is active right away. A confirmation tells you it's saved under Settings → Lead Routing Policies, and reminds you the original routing was left unchanged.
Converting CSV import routing
Step 1: Open your CSV routing
From your dashboard, navigate to the People tab → Import → Routing, and open the routing you want to convert.
Step 2: Save any pending changes
If the "Convert to lead routing policy" button is greyed out, you have unsaved edits. Hovering it shows why. Save the routing first.
Step 3: Convert and review
Click "Convert to lead routing policy," review the translated policy and any notes, then click "Create policy." The policy takes the routing's own name.
There is no apply step here — CSV routing isn't switched over automatically. Instead, choose "Use a lead routing policy" on the first step of your next import and pick the policy you just created.
What may not carry over
A policy and native routing don't express everything the same way. Anything that can't be translated exactly is listed in the modal before you save, never dropped silently.
| Situation | What happens |
|---|---|
| Groups with identical conditions split by percentage | Their assignees are merged into one branch and distributed round-robin. Set per-assignee distribution on the policy if you need the weighting back. |
| Per-group daily quotas | Become per-assignee limits, and the policy gets a daily quota reset at midnight. Someone in two groups with different limits gets the lower one. |
| A branch pointing at more than one campaign or pipeline stage | The first is kept; the rest are left off. |
| The routing's default assignee | Not translated. Set a fallback user under the policy's Overflow rules if you need one. |
| A condition using an operator or field a policy can't evaluate | That single condition is skipped and noted. |
| A campaign outcome whose sequence is no longer attached to a campaign | Skipped and noted. |
| A routing with no assignees | The policy is created empty. Add assignees before using it. |
FAQs
Does converting change my webhook or CSV routing? No. Conversion only reads your routing. It stays active and untouched unless you choose "Apply to webhook."
Can I convert the same routing more than once? Yes. Each conversion creates a separate policy. Repeat names get a number appended, such as "Zillow Leads - Converted Routing (2)."
Can I edit the policy before it's created? Yes. The preview is the full policy builder. Rename it, adjust assignees, change the distribution method, add exclusion tags or overflow rules — then create it.
What if I apply the policy and want my old routing back? Remove the policy from the webhook's Routing section. Your native routing, campaign, and pipeline stage are restored exactly as they were.
I'm a Super User converting a child team's routing — why won't the policy apply? Policies are created on your own team, and a webhook only accepts a policy belonging to its team. Create the policy from within the child team instead.
The convert button isn't showing on my webhook. Either the webhook is already using a policy, or it has no native routing to convert.
Converting gets you onto Lead Routing Policies with the rules you already trust, and the preview means you see exactly what changed before anything is saved.