Migrating from Everflow

This guide is for brands switching from Everflow to Rekomi. Everflow is a network-shaped platform: your partners are company records whose people (and emails) live on nested partner users, and conversions belong to offers. The primary path is a one-key API pull with a Network API key; Rekomi flattens the network shape into a normal affiliate roster for you.

Most teams complete the cutover in a single afternoon. Migration is on Starter or higher; auto-notify is on Growth or higher.

Import via API (recommended)

1. In Everflow, open Control Center → Security and generate a Network API key. The key is shown once at creation. It must be a Network key: affiliate-portal, advertiser, and marketplace keys work against different API realms and will be rejected.
2. Open /dashboard/settings/migrate, pick Everflow, choose your target Rekomi campaign, and paste the key. It is used once, in memory, and never stored, logged, or shown again.
3. Pick your region. Most networks live on Everflow's US infrastructure (api.eflow.team); EU-hosted accounts use api-eu.eflow.team. If the pull cannot reach your account, try the other region.
4. Leave Import conversion history on (or switch it off) and click Pull from Everflow.

What the pull imports:

• Partners: Everflow partner records are companies; the email comes from each partner's users (the people who log into the partner portal). Partners with no portal users have no email anywhere in Everflow's API and are skipped; the import summary tells you how many, so you can invite them manually.
• Statuses, mapped per the table below.
• PayPal emails, best effort: where a partner's billing is set to PayPal with an email as the reception method, the pull copies it so payout onboarding starts pre-filled. Any other payment type (wire, check, Tipalti, crypto, and so on) does not carry over; those partners set up payouts fresh on Rekomi.
• Click totals from the last 12 months, from Everflow's aggregated reporting on a best-effort basis (their reporting window reaches back 367 days at most, so that is the depth the totals cover). If the reporting call is unavailable the import proceeds without them and tells you; live clicks count normally from day one either way.
• Conversion history: up to 365 days of conversions (Everflow's raw conversion data is retained for the prior 365 days at most, so older rows are not reachable by any export or API and cannot import). Amounts and per-row currency import verbatim, deduped on Everflow's unique conversion id, so re-running is safe and recurring or upsell events are never collapsed into one row. Everything imports as settled, locked history: nothing becomes payable from the API pull.

No slug preservation (and what carries the identity instead)

Everflow tracking links look like https://tracking-domain/9W598/2CTPL/?sub1=...: two machine-generated path tokens identifying the partner and the offer, minted per partner per offer, on the network's tracking domain. There is nothing user-chosen in them, so there is no slug to preserve: imported partners get fresh Rekomi links, and old Everflow links stop attributing at cutover.

The preservable identity asset in an Everflow program is coupon codes. Everflow supports per-partner codes for clickless attribution, and those codes are yours to re-create: mint the same codes as Rekomi campaign coupons (or Shopify discount codes with coupon attribution) and coupon-driven attribution keeps working with zero partner outreach.

The CSV fallback

Everflow's UI exports partners under Partners → the three-dot menu → Export (CSV or JSON). The export dialog lets you pick which partner, user, and sign-up fields to include, which means the column set varies per export; the importer sniffs headers tolerantly and matches partner name, user email and names, and status. Include the user email fields, or every row will be skipped for missing emails. Click totals and conversion history only come from the API pull (conversion report exports go through Everflow's Requested Reports queue and also have user-selected columns; use the Step 2 generic-column flow if you have one).

What the CSV importer brings across

Status mapping

Everflow uses inactive both for retired partners and soft-archived ones, so those rows import as Paused for your review rather than Approved. Reclassify any row with the bulk-status action in /dashboard/affiliates after import.

Step-by-step cutover

1. Run the API pull

Generate a Network key under Control Center → Security and run the pull under /dashboard/settings/migrate, with the right region selected.

2. Re-create coupon codes

If your program used Everflow coupon codes for clickless attribution, re-create them as Rekomi campaign coupons before announcing the move, so coupon-driven sales keep crediting the same partners without a gap.

3. Check the import result

The import shows a row-by-row result, including how many zero-user partners were skipped for missing emails. Every job is listed under Import history with an Undo button.

4. Opt into auto-notify (Growth+ only)

Everflow partners get fresh Rekomi links (no slug carries over) and most re-onboard payouts, so the notify email is worth sending: it hands each partner their claim link, where their new link and payout onboarding live. Send a sample to yourself first.

5. Swap the tracking

Install Rekomi's tracking snippet and hand partners their new Rekomi links. Old Everflow tracking links route through Everflow's domain and cannot be re-pointed. Keep Everflow active for a short shadow period to catch stragglers; then cancel.

What is NOT imported

Common gotchas

The 365-day history ceiling. Everflow's raw conversion endpoint reaches back one year at most. If your program is older, lifetime totals on Rekomi will start lower than Everflow's dashboards show. That is a retention limit on Everflow's side, not an import error.

Wrong key realm. A key from the affiliate portal or an advertiser account returns an out-of-realm error. Only a Network key (Control Center → Security) can read your partners and conversions.

Zero-user partners. Partners created via API or by an admin without portal access have no users, so no email exists to import. The summary counts them; invite those partners manually.

Dashboard totals can disagree. Everflow's Adjustments tool changes top-level reporting without touching conversion rows, so imported sums can legitimately differ from an adjusted dashboard. The conversion rows are the ground truth the import uses.

Formatted money strings. Amounts are parsed as machine decimals first; formatted strings like $7.32 are handled defensively.

Verifying the import landed clean

1. Open /dashboard/affiliates and spot-check 3-5 rows against the Everflow source.
2. Confirm a skipped-row count that matches your zero-user partners.
3. Spot-check one partner's conversion history against Everflow's conversion report for the same window.
4. Send a sample notification to yourself before firing the bulk send.

Importing history and earnings

The API pull already imports up to 365 days of conversions as locked, settled records. Use the Step 2 CSV flow when you want balances made payable on Rekomi: only the CSV flow previews the exact unpaid balance and asks you to authorize it. A Step 2 file for Everflow uses the generic columns (affiliate email, amount, commission, currency, date). See the migrations overview for the full reference.

Where to go next

• Coupon codes: re-creating Everflow codes so clickless attribution keeps working.
• Migrating from other platforms: the broader URL-preservation matrix.
• Plans and trials: what each tier includes and how the 14-day free trial behaves.