Migrate from Binom

Binom is a self-hosted, redirect-first tracker, and its two habits shape the move: traffic is routed through paths and rotations, and many teams host their landers inside Binom itself. Both are rebuilt in Qubix — the routing as flows, the local landers as PWAs or websites. There is no import from Binom, and its statistics stay on your server. The postback, as always, is the easy part.

What you bring across

In Binom	In Qubix	How it moves
Affiliate Network	Network	Rebuilt. Qubix ships 328 network templates with the macros pre-filled.
Offer	Offer	Rebuilt — URL and payout.
Landing Page / Lander	PWA or Website	Rebuilt. External landers become websites; local landers stored inside Binom must be re-hosted (see below).
Traffic Source	Source	Rebuilt — parameters and tokens.
Campaign	Campaign	Rebuilt.
Paths, Rotations, Rules	Flows and distribution	Rebuilt — the path tree, weights and filters become Qubix flows.
Domain / Tracking URL	Domain	Re-pointed to Qubix and given a role.
Postback	Postback	Seamless — change only the domain (see below).
Reports and history	—	Not transferred.

Local landers must be re-hosted

If your landers are integrated (uploaded and served inside Binom), they do not carry over — there is nothing to point at once Binom is gone. Rebuild them as PWAs or upload them as Websites. Only landers hosted on your own external server can stay where they are.

Term differences to keep in mind

• A Binom Path (a routing branch with its landers and offers) and Binom Rules (filters that send matching clicks down a path) both become part of a Qubix flow.
• Rotation in Binom means two things — the split mode (Normal / Smart) and a reusable shared config attached to many campaigns. In Qubix the split is configured per flow; there is no shared-rotation object, so re-apply the same split settings to each campaign that used it.

The order to rebuild

1. Domains. Point your tracking domains at Qubix and assign roles — Domains.
2. Networks. Recreate each affiliate network — Connecting a network.
3. Offers. Recreate offers with URL and payout — Creating an offer.
4. Sources. Recreate traffic sources and their tokens — Creating a source.
5. Landers. Rebuild local landers as PWAs; register external ones as Websites.
6. Campaigns, paths and rotations. Recreate the campaign, then move your paths, weights and rules into flows.
7. Postbacks. Repoint the postback — below.

Postbacks: change only the domain

Binom's postback goes to click (Binom v2; older v1 installs use click.php) with cnv_id, cnv_status and payout. Open each affiliate network's postback setting and change only the domain:

Before:  https://track.your-binom.com/click?cnv_id={clickid}&cnv_status={status}&payout={payout}
After:   https://your-postback-domain/click?cnv_id={clickid}&cnv_status={status}&payout={payout}

Leave the path (Binom v2 uses /click, v1 /click.php) and every parameter as they are. Qubix reads Binom's cnv_id, cnv_status and payout without reformatting.

The event is taken from cnv_status:

Binom cnv_status	Recorded in Qubix as
lead	registration
sale, deposit	deposit
reject, trash	rejection
hold	registration (pending)

Keep the status scheme your networks already send — nothing to rewrite.

Check before you switch off Binom

Fire a test conversion and watch it land on the Postbacks feed, then in the deposit and registration reports. Cut traffic over only once conversions arrive reliably.

What's next

Migrate to Qubix

The overall move and what transfers.

Flows and distribution

Where Binom paths and rotations go.

Parameter passing and postback

The postback in depth.