How long does migrating from Boberdoo take?

Most operators switch the routing itself in a weekend once the mapping review is done. The full timeline is set by how many buyer integrations need test-ping verification and how long you run in parallel: typically mapping review in week one, a 2 to 4 week parallel run, then cutover with Boberdoo kept warm for a week.

Does Datahubb migrate my Boberdoo setup for me?

Yes, free. The team rebuilds your buyers, campaigns, filters, and payout rules from your exports, and you review every mapping before anything goes live. Contract-end pricing applies if you are still under a Boberdoo contract.

What Boberdoo features do not carry over to Datahubb?

Non-exclusive multi-sell is the main one: Datahubb picks a single winner per distribution run, with reposting and tiered remnant monetization as the alternatives. Consumer SMS and email nurture also stays with whatever tool runs it now.

How do Boberdoo lead types map to Datahubb?

A lead type or vertical becomes a campaign, partners become buyers with a delivery method and type, price-based routing becomes Highest Bidder, weighted routing becomes Weighted, tiered routing becomes Advanced distribution with per-tier payout floors, and filters become lead filters at four levels.

How do I switch without dropping leads?

Mirror a copy of live traffic through Datahubb alongside Boberdoo for 2 to 4 weeks and compare sold rate, margin, and rejection reasons against a baseline you wrote down first. Cut over on a quiet morning and keep Boberdoo live but de-prioritized for a week as the fallback.

Switching from Boberdoo to Datahubb: What Maps, What Breaks, How Long It Takes

The question every Boberdoo operator asks about switching is never about features. It is about risk: what breaks, who takes the blame if a buyer integration drops leads mid-cutover, and how many weekends this really costs. This guide answers that honestly, including the parts of a Boberdoo setup that do not port one to one.

Three facts up front. Migration to Datahubb is done for you: the team rebuilds your buyers, campaigns, filters, and payout rules from your exports, free, and you review every mapping before anything goes live. You do not cut over blind: mirror a copy of live traffic through Datahubb alongside Boberdoo for 2 to 4 weeks and compare sold rate, margin, and rejection reasons on your own leads first. And if you are still inside a Boberdoo contract, Datahubb discounts your subscription until it ends.

The concept map

Boberdoo's model translates cleanly. This is the mapping the migration team works from:

Boberdoo	Datahubb
Lead Type / vertical	Campaign (the container for fields, buyers, suppliers, filters, distribution)
Partner / buyer	Buyer, with a delivery method (direct post, ping post, one-to-one, email, store) and a type (CPL, CPA, PPC, CPC)
Ping/Post	Ping post on a dedicated concurrent ping service, multi-step pings supported
Price-based routing	Highest Bidder
Weighted routing	Weighted, a smooth-toward-target engine that converges buyers to their target share and self-corrects on rejection
Tiered routing	Advanced distribution: ordered tiers, each with its own sub-strategy and its own minimum payout floor
Filters	Lead filters at four levels: global, supplier, buyer, traffic source, with 14 condition types
Source / affiliate	Suppliers and Traffic Sources, each with their own API key
Return processing	Returns module with ledger reversal and payout corrections
Min or floor price	Campaign minimum bid price, or per-tier minimum payout in Advanced

What breaks, honestly

Not every concept has a twin, and it is better to know before cutover than in week two.

Non-exclusive selling. Datahubb picks a single winner per distribution run. If you sell the same lead to several buyers simultaneously on Boberdoo today, that needs planning: reposting and tiered remnant monetization are the equivalents, and they suit exclusive and semi-exclusive models, not true multi-sell.
Zero-payout buyers. A RevShare-style buyer bidding zero gets filtered out by price floors unless its Advanced tier has a minimum payout of exactly zero. The migration team sets this up front; it is the single most common gotcha.
CPA partners that pay on downstream conversion. On Datahubb these should use the CPA flow: the sale holds as pending, with no revenue booked, until the buyer's postback confirms, with a configurable confirmation window and automatic expiry. If you booked that revenue at delivery on Boberdoo, your reporting timing changes, deliberately.
Consumer nurture. Datahubb delivers leads to buyers. Any consumer SMS or email follow-up stays with whatever tool runs it now.

What you gain on the other side

The reason to endure any migration: capabilities the old platform does not have. Boberdoo's own documentation states its unmatched-reasons tool is real-time only and does not log the reason per lead for later reference. On Datahubb, every rejection permanently records the exact rule that fired, next to the lead's actual value, and rolls up into groups ranked by estimated missed revenue with an action plan. Leads skipped only on caps or schedule can be redistributed to those same buyers later. Routing rules let one campaign run different strategies for different traffic slices. And your bill stops scaling with volume: from a published $499/month, unmetered, against Boberdoo's calculator tiers that reach $1,075/month at 25 leads per day and climb from there.

The first-week sequence

The standard rebuild, whether the migration team drives or you do:

Create the campaign for your highest-volume lead type and define its fields once in the guided builder.
Add suppliers and traffic sources. Each gets its own API key; payload defaults can normalize inconsistent senders.
Add buyers with the right delivery method and buyer type, porting endpoints, headers, and credentials.
Choose distribution. Price-based becomes Highest Bidder; tiered becomes Advanced with per-tier floors. Set the zero-payout tiers now.
Port filters and integrations. State and ZIP lists import from CSV; fraud, DNC, and validation providers attach with per-campaign rules.
Wire postbacks. Sources and buyers get their own Postbacks v2 configs with event subscriptions; the in-app guide generates ready-to-paste URLs for partners.
Test before traffic. Buyer test pings and posts bypass schedules, and ingest logs show exactly what happened to each lead, so you prove the routing matches before real volume moves.
Start the parallel run. Mirror a slice of live traffic and compare sold rate, margin, and rejection reasons against Boberdoo for 2 to 4 weeks.

How long it actually takes

Most operators switch the routing itself in a weekend once the mapping review is done. The full timeline is set by two things: how many buyer integrations come with you (each one needs its endpoint verified with test pings) and how long you choose to run in parallel. A typical shape: mapping review in week one, parallel run through weeks two to four, cutover on a quiet morning with Boberdoo kept warm for a week as the fallback.

The cutover checklist

Every buyer has passed a test ping and post, with the response mapped to accept, reject, and price.
Zero-payout and CPA buyers sit in tiers with the right floors and confirmation windows.
Parallel-run numbers meet or beat the Boberdoo baseline you wrote down before starting.
Suppliers have the new ingest URLs and keys; postback URLs are swapped on both sides.
Boberdoo stays live but de-prioritized for one week; nothing is cancelled until the first full reconciled week closes.

Start with the Boberdoo comparison for the side-by-side, or open a 14-day self-serve trial and run the first-week sequence against test traffic before you commit to anything.