Guide · Updated 23 October 2026
How to switch lead distribution software without losing leads
Short answer
You can switch lead distribution software without losing a lead if you never switch all at once. Write down your buyers, caps and routing, rebuild them in the new platform, test each buyer with a test lead, send a small share of live traffic through it, and compare acceptance and revenue per lead. Move publishers and postbacks only when the numbers match, and cancel the old plan after one full billing cycle.
What to write down before you touch anything
| Item | Why it matters | Where it usually hides |
|---|---|---|
| Buyer endpoints and auth | A wrong header or field name means every lead is rejected | Each buyer's delivery settings, often with a key you did not write down |
| Prices, floors and caps | These decide who sees a lead first and when they stop | Buyer settings, sometimes also in spreadsheets |
| Routing order and weights | Your revenue depends on it | The cascade or distribution rules |
| Filters and fraud rules | Without them, junk reaches buyers and comes back as returns | Rules, blocklists, a developer's script |
| Publishers and their payout rates | You owe them money and they track against your links | The affiliate or supplier list, plus side agreements |
| Tracking links and postback URLs | Publishers already have these in their own systems | Links you issued, and the postback settings publishers pasted in |
| Contract dates, notice periods, prepaid fees | You can pay for two systems longer than you planned | Order forms and billing emails |
The publisher problem
Your buyers are easy to move because you control the integration. Your publishers are harder: they have your tracking links in their campaigns and a postback URL in their tracker. If those change on cutover day, conversions stop matching and payout arguments start.
Two ways to handle it. Keep the old links live and move publishers to new ones in groups, telling each group a week ahead. Or, if your tracking runs on your own domain, point that domain at the new platform on cutover so links keep working. Test the link parameters first, because a different parameter name quietly breaks attribution.
A cutover plan that keeps leads flowing
- Inventory everything in the table above.
- Rebuild your buyers in the new platform and send a test lead to each one.
- Rebuild routing and filters. Run new rules in watch-only mode first so you see what they would reject.
- Send a small share of live traffic, about a fifth, through the new platform for a week or two.
- Compare the two side by side (see below). Fix differences before moving more.
- Move publishers and their postbacks in groups, then the rest of the traffic.
- Keep the old plan for one full billing cycle, then cancel in writing.
What to compare during the parallel run
- Acceptance rate per buyer: how many leads each one took.
- Rejections and returns, and why.
- Revenue per lead after returns, not the headline price.
- Response times, because a slow buyer costs bids.
- Totals: your platform's sales against what buyers say they received.
- Publisher numbers against their own tracking.
Leaving a specific platform
| Platform | Worth checking before you leave |
|---|---|
| LeadExec | Export your buyer list, delivery settings and caps before you start. If you pay annually, time the move with your renewal date. Run a share of traffic through pingtype first and compare sales before moving the rest. |
| LeadsPedia | Export your offers, buyers and publisher list before you start. Ask for your plan's end date so you do not pay twice. Move one vertical first, then the rest. |
| boberdoo | Ask boberdoo for an export of your buyers, filters and pricing rules. Confirm your contract end date and any setup fee you have already paid. Run a test lead through your most complex buyer first. |
| Lead Prosper | List every buyer integration you rely on, so each is rebuilt and tested with a test lead. Keep Lead Prosper live on a share of traffic until pingtype matches your acceptance rates. |
| Phonexa | List which Phonexa modules you actually use; you may only need to replace the lead distribution and tracking. Check contract and setup terms before you give notice. |
| LeadByte | Export your suppliers, buyers and routing rules. Run both in parallel on a share of traffic. |
| Vertikl | Export your routing rules, buyers and prices. Use the free-trial or monthly nature of your plan to run both side by side before you cancel. |
| LeadRouter | List your routing rules and fallbacks, then rebuild them as a cascade in pingtype. Keep your tracker; point your sales postbacks at pingtype's tracking domain if you want pingtype to handle publisher tracking too. |
| iRev | Ask iRev for an export of partners, offers and payout history. Check your commitment and any onboarding terms before moving. |
| PalDock | Export your partners, offers and conversions, and note any custom integrations PalDock built for you. Compare what you pay PalDock on your last three months of approved payouts with $900 a month. |
| Pingtree | Check whether your current set-up relies on its funnel builder; pingtype includes a form builder with a drag-and-drop editor. |
| Standard Information | Ask for an export of your buyers and appointment rules. Confirm support terms and contract before you give notice. |
| LeadConduit | Map each LeadConduit flow to a pingtype cascade and rules. If you use ActiveProspect validation or consent tools, check which you will keep alongside pingtype. |
Where each part lands in pingtype
| Your current set-up | In pingtype |
|---|---|
| Buyers and delivery settings | Buyers with field mapping, JSON delivery, an X-Api-Key header, reply parsing and test leads |
| Routing order and weights | Cascades, waterfall or percentage split, and ping/post bidding |
| Caps and schedules | Caps on leads, clicks, sales or spend, with time windows and warm-up |
| Duplicate, fake and fraud rules | Rules with a watch-only mode, phone, email and IP checks, and a risk score |
| Publishers | Publishers with tracking links, their own sign-up portal and payouts |
| Tracking links and postbacks | The built-in click tracker, on your own tracking domain, with S2S postbacks |
| History | Conversions can be imported by CSV |
Questions
How long does it take to switch lead distribution software?
Rebuilding buyers and rules is quick compared with the parallel run. Plan for one to two weeks of side-by-side traffic and one billing cycle before you cancel the old plan.
Will my publishers need new links?
Only if you change your tracking domain. If your links run on your own domain, you can point it at the new platform. Test the link parameters before you do.
Can I bring my history across?
Ask your current vendor for an export of buyers, offers and history. pingtype can import conversions by CSV.
Do I need a developer to switch?
Not for pingtype: buyers, rules, cascades and tracking are set up on screens.