Migrate from Keitaro
Moving off Keitaro is not a one-click import — there is no automated pull from Keitaro, and your historical statistics stay there. What you do is rebuild your setup in Qubix, piece by piece, using the ready sections of the panel. The good news: it is a one-time job, most of it is quick, and the postback — the part everyone dreads — is nearly free (you change only the domain).
This page maps every Keitaro concept onto its Qubix counterpart and gives the order to rebuild them in.
What you bring across
| In Keitaro | In Qubix | How it moves |
|---|---|---|
| Affiliate network | Network | Rebuilt. Qubix ships 328 ready network templates, so the offer/postback macros are filled in for you. |
| Offer | Offer | Rebuilt — the offer URL and payout. |
| Landing page (local or external) | PWA or Website | Rebuilt in the PWA builder or uploaded as a static site. |
| Traffic source | Source | Rebuilt — the incoming parameters and macros. |
| Campaign | Campaign | Rebuilt. |
| Flow and streams (the rotation and routing inside a campaign) | Flows and distribution | Rebuilt — filters, weights and the split logic become Qubix flows. |
| Domain | Domain | Re-pointed to Qubix and given a role. |
| Postback (network → tracker) | Postback | Seamless — you change only the domain (see below). |
| Reports and historical stats | — | Not transferred. There is no import; statistics start fresh in Qubix. |
Qubix does not pull data from Keitaro's API — Keitaro is supported as a postback format, not as a sync. Plan the move as a manual rebuild, and keep Keitaro running in parallel until you have checked that conversions arrive in Qubix.
The order to rebuild
Each step links to the section that covers it in full — this page is the map, not a repeat of every screen.
- Domains. Point the domains you will use at Qubix and assign their roles — Domains.
- Networks. Recreate each affiliate network; pick its template if there is one — Connecting a network.
- Offers. Recreate your offers (URL + payout) — Creating an offer.
- Sources. Recreate your traffic sources and their parameters — Creating a source.
- Landings. Rebuild local landings as PWAs — Creating a PWA — or upload external ones as Websites.
- Campaigns and streams. Recreate the campaign, then move your Keitaro streams (filters, weights, rotation) into Qubix flows — Creating a campaign and Flows and distribution.
- Postbacks. Repoint the postback — the seamless step below.
Once traffic runs through a Qubix campaign, Qubix stamps its own visitor identifier into the offer links. That identifier is what the network echoes back on a conversion — which is what makes the postback step below just work.
Postbacks: change only the domain
In Keitaro the network sends its postback to an address with a security key in the path, then
/postback, then the parameters. Open each affiliate network's postback setting and change
only the domain:
Before: https://track.your-keitaro.com/a1b2c3d4/postback?subid={subid}&status={status}&payout={payout}¤cy={currency}
After: https://your-postback-domain/a1b2c3d4/postback?subid={subid}&status={status}&payout={payout}¤cy={currency}
Leave the a1b2c3d4/postback path and every parameter exactly as they are. Qubix reads Keitaro's
subid, status, payout and currency without any reformatting; any extra parameter, including
a security key, is ignored.
The event is taken from Keitaro's status, the same way Keitaro reads it:
| Keitaro status | Recorded in Qubix as |
|---|---|
registration, lead | registration |
sale, deposit | deposit |
rejected, trash | rejection |
Keep sending the status your networks already send per event — there is nothing to rewrite.
Check before you switch off Keitaro
Fire a test conversion and watch it appear on the Postbacks feed, then in the deposit and registration reports. Only once conversions land reliably should you stop sending traffic through Keitaro.