Migrating from Leadbyte or Leadprosper
How your existing setup maps onto LeadMove, and the order to rebuild it in so no lead is lost during the switch.
There's no automated import yet — you rebuild your setup in LeadMove, test it, then repoint your suppliers. The concepts map almost one-to-one, so it's mostly retyping, not rethinking.
What your terms become
| In Leadbyte / Leadprosper | In LeadMove |
|---|---|
| Campaign | Pipeline — one per lead type you sell |
| Supplier / vendor | Source — one per partner, each with its own posting URL |
| Post URL / lead capture URL | Posting URL — /api/i/{source-key}, no header or key to send |
| Field mapping | Intake mapping, plus automatic matching of field-name variants |
| Client / buyer | Buyer — reusable across pipelines |
| Delivery / integration | Delivery method — email, webhook, Google Sheets or SMS |
| Filters / criteria | Routing rule conditions |
| Priority / order | Tiers — tier 1 is tried first, then tier 2 |
| Caps / limits | Buyer quotas — daily, weekly, monthly |
| Duplicate check | Deduplication — fields plus a time window, per pipeline |
| Lead return / rejection | Dispute, resolved by credit or replacement |
The order to rebuild in
- Pipeline and fields. One pipeline per lead type you sell, using the same field names your suppliers already post — then you don't have to touch their setup later.
- Buyers and delivery methods. Copy webhook URLs, headers and body templates exactly as they are today, so the buyer's system sees the same payload.
- Routing rules, tiers and pricing. Each filter becomes a rule's conditions; the tier reflects who gets first refusal. Set the price on the buyer, or on the rule when it varies by lead.
- Test before switching. Run real payloads from your old system through the test console and compare the previewed payload against what your buyer receives today.
- Switch the supplier posting URLs, one supplier at a time, keeping your old setup live until you've seen leads land correctly.
Migrate one supplier at a time
Switching everything in one evening leaves you no way to tell whether a missing lead is a mapping problem or a supplier problem. Move your smallest supplier first, watch a day of real traffic, then move the rest.
Two things that behave differently
- Nothing is dropped. A lead that fails validation or matches your dedup rules is still stored, so you can fix it and resend instead of losing it. See Lead statuses explained.
- Every lead is scored. Leads arrive with a 0-100 quality score and an A-D grade you can use in routing conditions and pricing.
A guided migration assistant is on the roadmap. Until it ships, if you're moving a large setup, get in touch and we'll go through it with you.
Common questions
Can you import my campaigns and buyers from an export? Not automatically today. Sending us an export still helps us help you rebuild faster.
Do my suppliers have to change how they post? Usually only the URL. LeadMove accepts JSON and form-encoded bodies and matches field names case-insensitively, ignoring spaces, underscores and dashes. See the Webhook API reference.
Can I run both systems in parallel? Yes, and you should. Nothing in LeadMove touches your old platform, so keep it running until every supplier is moved.
What about my historical leads? By default they stay where they are — LeadMove's deduplication only sees the leads it has received itself. If you want your history inside LeadMove (past leads, stats, dedup against old contacts), contact support and we'll import it with you as a custom migration.