Migrating from FirstPromoter

This guide is for brands switching from FirstPromoter to Rekomi. The primary path is a one-key API pull: paste your FirstPromoter API key and Account ID and Rekomi imports your promoter roster (with each promoter's referral token and lifetime click count), your leads, and your commission history in one run. A CSV upload remains as a secondary path for Promoters exports you already have.

Existing brand.com/?fpr=alex links are preserved automatically. Migration is on Starter or higher; auto-notify is on Growth or higher.

Import via API (recommended)

FirstPromoter's Promoters CSV export has undocumented columns, and its Referrals list (your leads) has no export at all, so the API pull is both the easiest and the most complete path.

1. In FirstPromoter, open Settings → Integrations and copy your API key and Account ID (both are shown there).
2. Open /dashboard/settings/migrate, pick FirstPromoter, choose your target Rekomi campaign, and paste both values. They are used once, in memory, and never stored, logged, or shown again.
3. Leave the Import leads and Import commission history toggles on (or switch either off) and click Pull from FirstPromoter.

What the pull imports:

• Promoters: email, name, per-campaign status (API mapping: accepted imports as Approved, pending/not_set as Pending, rejected and blocked as Banned, inactive as Paused), PayPal email when exposed, and the referral token (ref_token) preserved as the Rekomi link slug. Promoters enrolled in several FirstPromoter campaigns import once, with their first campaign's token and status; the import summary reports how many that affected.
• Click counts: each promoter's lifetime unique-click aggregate (clicks_count) carries over into their Rekomi click counter, so leaderboards and EPC math don't reset to zero.
• Leads: referrals who never became paying customers import as zero-money lead records attributed to their promoter, so your funnel and lead counts are populated from day one.
• Commission history: each commission's amount and sale amount (FirstPromoter reports integer cents; they import 1:1), date, and paid state (is_paid). Everything imports as settled, locked history: nothing becomes payable from the API pull. Denied commissions are skipped. Zero-decimal currency amounts (for example JPY, which has no cents) import exactly as FirstPromoter reports them, with no rescaling.

What the pull cannot import: payable balances (use the Step 2 CSV flow with its preview if you want unpaid commissions made payable), promo codes, campaign structure, custom fields, and click-level logs (FirstPromoter only exposes aggregates). Each list is fetched up to 5,000 rows; the result tells you if a fetch was cut off.

Re-running the pull is safe: affiliates dedupe by email and history rows dedupe on FirstPromoter's own ids.

The CSV fallback

If you prefer a file, the CSV importer still works with the Promoters-tab export. Leads and history cannot come from that file (only from the API pull or the Step 2 referrals CSV).

What the CSV importer brings across

The importer fuzzy-matches header names case-insensitively and accepts either v1 or v2 columns interchangeably. Other columns from FirstPromoter's export (id, default_ref_id, promo_code, created_at, country) are silently ignored.

Status mapping

FirstPromoter's v2 rollout renamed several states. The importer unifies both vocabularies:

The match is case-insensitive. If your CSV has both columns (transitional accounts during the v2 rollout), the first one the parser sees wins.

How slug preservation works

FirstPromoter's tracking URL is brand.com/?fpr={cust_ref}. Rekomi recognizes fpr as one of the 16 default attribution params, so no additional config is required - every existing FirstPromoter link works on Rekomi out of the box once you swap the snippet.

The importer reads cust_ref (v1) or ref_id (v2) from every row and tries to register that exact value as the affiliate's new Rekomi slug. Preservation succeeds when:

1. The value is a valid alias: 3-64 characters, alphanumeric plus hyphen, no leading or trailing hyphen.
2. The slug is not already taken globally.

FirstPromoter's slugs are usually short, lowercase, and well-formed, so collision rates are low. The job detail panel lists any rows that fell back to fresh random slugs.

Step-by-step cutover

1. Run the API pull

Copy your API key + Account ID from Settings → Integrations in FirstPromoter and run the pull under /dashboard/settings/migrate (see Import via API above). One run brings your roster, leads, and history.

If you use the CSV fallback instead: export from the Promoters tab (NOT Reports; the Reports export excludes promoters who haven't yet made a referral) and upload the file. The importer detects v1 vs v2 automatically based on which columns are present.

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

Check Notify affiliates after import and compose a personal note. Click Send a sample to myself to fire a preview, then let the bulk dispatch run at 1 email/sec.

3. Swap the tracking snippet

Install Rekomi's tracking snippet, remove FirstPromoter's snippet. fpr is already in Rekomi's default attribution params, so every existing brand.com/?fpr=alex link starts attributing to Rekomi from the moment the swap is live.

4. Cancel FirstPromoter

Keep FirstPromoter active for a 24-48 hour shadow period if you want to compare numbers, then cancel.

v1 vs v2: which one am I on?

FirstPromoter was acquired by SpringWater Capital in September 2025. The v2 UI redesign started rolling out late 2025 and continued through early 2026. You can tell which export format you have by opening the CSV:

• v1 format has a status column (approved / pending / denied / blocked) and a cust_ref column.
• v2 format has a state column (accepted / not_set / rejected / inactive) and a ref_id column.

You don't need to do anything different in the Rekomi importer - it auto-detects. The reason this matters is for verifying the import landed correctly after the fact: if your CSV is v2, expect rejected affiliates to show "rejected" in the source column and not "denied".

What is NOT imported

Common gotchas

My export from Reports has fewer rows than I expected. You exported from Reports instead of Promoters. The Reports tab excludes promoters without referrals. Re-export from Promoters → Export.

Some rows have status and others have state. This happens during the v2 rollout if FirstPromoter migrated only part of your account. The importer handles it - both columns get parsed correctly.

Promo codes in promo_code aren't carrying over. Correct - the importer doesn't currently bring across promo codes. Recreate them in Rekomi's coupons UI; Rekomi auto-attributes coupon redemptions to the affiliate they were minted for.

My PayPal emails are different from the affiliate emails. That's fine. paypal_email is preserved separately from email. Payouts use the PayPal address; the account login uses the regular email.

Verifying the import landed clean

After the job completes:

1. Open /dashboard/affiliates and spot-check 3-5 rows.
2. Confirm one affiliate's tracking link is brand.com/?fpr={cust_ref} matching the source.
3. Send a sample notification to yourself.
4. Click your own test link with the new snippet live; confirm a click row appears.

Then fire the bulk auto-notify and cancel FirstPromoter.

Importing history and earnings

The API pull already imports your commission history (and leads) as locked, settled records. Use the Step 2 CSV flow instead when you have a referrals/commissions export file, or when you want unpaid commissions made payable on Rekomi: only the CSV flow previews the exact unpaid balance and asks you to authorize it.

• Past conversions and commissions are matched to the affiliate by email (or preserved slug) and recorded with the amount and date from your export.
• Commissions FirstPromoter already paid import as locked history (shown in lifetime totals, never paid again). Commissions still owed are queued for a Rekomi payout only if you authorize it on the preview screen.
• If your export includes a customer's Stripe customer/subscription id and your Stripe is connected, existing subscriptions keep paying the same affiliate on renewals.
• A dry-run preview shows what will import (and exactly how much, if anything, Rekomi would pay) before you commit. Re-running is safe. Denied and refunded rows are skipped.

See the migrations overview for the full reference.

Where to go next

• Tracking and attribution: fpr and the other 15 default params.
• Coupons: recreate FirstPromoter promo codes with per-affiliate Stripe coupon minting.
• Migrating from other platforms: URL-preservation matrix.
• vs FirstPromoter: side-by-side comparison if you are still evaluating.