Migrating from Refersion
Move a Refersion affiliate roster onto Rekomi with a two-key API pull. Rekomi preserves rfsn tracking links; conversion history comes in through the Step 2 CSV flow.
This guide is for brands switching from Refersion to Rekomi. The primary path is a two-key API pull; a CSV fallback covers Refersion's own emailed export.
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)
- In Refersion, open Account, Settings, Refersion API and copy your Public Key and your Secret Key. API access requires Refersion's Growth plan or higher.
- Open
/dashboard/settings/migrate, pick Refersion, choose your target Rekomi campaign, and paste both keys. They are used once, in memory, and never stored, logged, or shown again. - Click Pull from Refersion.
What the pull imports:
- Affiliates: email, name, and status (
ACTIVEimports as Approved,Pendingas Pending,Deniedas Rejected). - Tracking link: Refersion's link carries
?rfsn={affiliateId}.{affiliateCode}, for example?rfsn=123456.abc123. Rekomi preserves the full{affiliate_id}.{code}value as the slug, not just a fragment, so links keep attributing.
Refersion's REST API does not expose conversion or order history, so the API pull does not bring across historical conversions; use the Step 2 CSV flow (below) for that.
Re-running the pull is safe: affiliates dedupe by email.
The CSV fallback
Refersion's dashboard export is emailed to you. The importer matches email, name, and status columns tolerantly.
What the CSV importer brings across
| Field | Source column | Notes |
|---|---|---|
closest match to email | Required. Lowercased + trimmed. Primary dedup key. | |
| Full name | closest match to first_name + last_name | Joined when both exist. |
| Status | closest match to a status column | See mapping table below. |
| Tracking slug | ?rfsn= extracted from a link column, when present | Falls back to a fresh slug when absent. |
Status mapping
| Refersion | Rekomi |
|---|---|
| Active / Approved | Approved |
| Pending | Pending |
| Denied | Rejected |
| anything else, blank, or missing | Pending |
Denied affiliates in Refersion cannot re-apply on their side, so they import into Rekomi as Rejected, matching their terminal state.
How slug preservation works
Refersion's tracking link carries the referral value as ?rfsn={affiliateId}.{affiliateCode}. rfsn is a built-in Rekomi attribution param, and Rekomi preserves the full value, both the numeric affiliate id and the code, rather than just the code fragment. That means existing Refersion links keep attributing on Rekomi the moment you swap the tracking snippet, as long as the row was reached during import.
Step-by-step cutover
1. Run the API pull
Create a Public Key and Secret Key under Account, Settings, Refersion API in Refersion and run the pull under /dashboard/settings/migrate.
2. Attribution params: nothing to configure
rfsn is a built-in Rekomi attribution param, so existing ?rfsn= links resolve to the right affiliate with zero configuration.
3. Check the import result
The import runs synchronously and shows a row-by-row result. Every job is listed under Import history with an Undo button.
4. Opt into auto-notify (Growth+ only)
Send imported affiliates a claim link so they can set up payouts on Rekomi. Send a sample to yourself first.
5. Swap the tracking snippet
Install Rekomi's tracking snippet, then remove Refersion's script. Existing ?rfsn= links attribute to Rekomi immediately. Keep Refersion active for a 24-48 hour shadow period, then cancel.
What is NOT imported
| Data | Status | Workaround |
|---|---|---|
| Conversion and order history | Not exposed by Refersion's REST API | Use the Step 2 CSV flow with the generic columns (affiliate email, amount, commission, currency, date). |
| Coupon assignments | Not imported | Mint fresh Rekomi coupon codes. |
Common gotchas
Both keys required. The Refersion API pull needs the Public Key and the Secret Key together; a single key is not enough.
Plan gate on the API. Refersion's API requires the Growth plan or higher. If your account does not have API access, use the emailed CSV export instead.
No history via the API. Refersion's REST API has no conversion-list endpoint, so the API pull is roster-only for history purposes. For historical conversions, prepare a Step 2 CSV from your own records.
Verifying the import landed clean
- Open
/dashboard/affiliatesand spot-check 3-5 rows against the Refersion source. - Open one affiliate's detail page and confirm the preserved
rfsnslug (the fullid.codevalue). - Click an affiliate's existing
?rfsn=link with the new snippet installed; confirm a click row appears within a few seconds. - Send a sample notification to yourself before firing the bulk send.
Importing history and earnings
Because the API pull does not include conversion history, Step 2 is the path to bring Refersion's past conversions onto Rekomi. Prepare a CSV using the generic columns (affiliate email, amount, commission, currency, date) from your own records, then upload it under Settings, Migrate, Step 2. See the migrations overview for the full reference.
Where to go next
- Tracking and attribution: the
rfsnparam, cookie window, and stickiness. - Migrating from other platforms: the broader URL-preservation matrix.
- Plans and trials: what each tier includes and how the 14-day free trial behaves.
Migrating from ReferralCandy
Move a ReferralCandy affiliate roster onto Rekomi with an API pull. ReferralCandy's API exposes no commission amounts, so the pull imports the roster only; FRIEND- coupon codes keep crediting on Shopify stores.
Migrating from BixGrow
Move a BixGrow affiliate roster onto Rekomi with a CSV export. Rekomi preserves bg_ref tracking links, and coupon codes keep crediting since they are real Shopify discounts.