Migrating from Post Affiliate Pro

This guide is for brands switching from Post Affiliate Pro to Rekomi. Post Affiliate Pro's merchant API authenticates with your panel password, which Rekomi never asks for, so the import is CSV-only, and both of Post Affiliate Pro's export shapes work as-is.

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

Export from Post Affiliate Pro

Two export paths work, and you don't need to reformat either:

1. Tools, Import/Export (the canonical path): export Affiliates. This produces the semicolon-delimited file with !FIELDNAME headers (!USERID;!REFID;!RSTATUS;!USERNAME;!FIRSTNAME;!LASTNAME;...). Rekomi reads it directly, semicolons, ! headers, letter statuses and all.
2. Affiliates, Affiliates manager: the grid's Export to CSV button exports the columns you have visible. Rekomi matches those column titles tolerantly.

Then open /dashboard/settings/migrate, pick Post Affiliate Pro, choose your target Rekomi campaign, and upload the file.

What the CSV importer brings across

Status mapping

How slug preservation works

Post Affiliate Pro links carry the affiliate's Referral ID as a_aid, in both formats the platform generates: the query form ?a_aid=jane and the classic fragment form #a_aid=jane. The importer preserves each affiliate's Referral ID as their Rekomi slug (reading it from the !REFID column or lifting it out of a link column, fragment included), and a_aid is a built-in Rekomi attribution param, so existing Post Affiliate Pro links keep attributing the moment you swap the tracking snippet.

One nuance: Post Affiliate Pro defaults the Referral ID to the numeric user ID unless the affiliate customized it. Numeric IDs of 3+ digits are preserved as-is; shorter ones get a fresh slug.

Step-by-step cutover

1. Export and upload

Export affiliates from Tools, Import/Export (or the Affiliates manager grid) and upload the file under /dashboard/settings/migrate.

2. Attribution params: nothing to configure

a_aid is a built-in Rekomi attribution param, so existing ?a_aid= and #a_aid= 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. Import transaction history (Step 2)

Export transactions the same way (Tools, Import/Export, or the Transactions grid's export) and upload the file under Settings, Migrate, Step 2. Post Affiliate Pro gets a dedicated transaction parser; see Importing history and earnings below.

5. 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.

6. Swap the tracking snippet

Install Rekomi's tracking snippet, then remove Post Affiliate Pro's integration code. Existing a_aid links attribute to Rekomi immediately. Keep Post Affiliate Pro active for a 24-48 hour shadow period, then cancel.

Importing history and earnings

Post Affiliate Pro's transaction export has a dedicated parser (not the generic-column path), so both transaction file shapes work directly:

• Approved, unpaid commissions (payout status U with an approval date) import as owed, payable only after you explicitly confirm during the import.
• Paid commissions (payout status P) import as settled history, never paid again.
• Declined transactions and refund/chargeback rows (D status, R/H types) never import.
• Recurring commissions (type U) import as recurring; sales, actions, and bonuses import as one-time.
• Amounts are read in your Post Affiliate Pro account currency. The canonical export carries no currency column, so rows fall back to your Rekomi home currency; make sure they match, or add a currency column.

One identity caveat: the canonical Tools, Import/Export transaction file identifies affiliates by user ID only. Because Post Affiliate Pro defaults each affiliate's Referral ID to their user ID, most rows resolve automatically against the imported roster. Affiliates who customized their Referral ID need an email or affiliate-name column in the file (the Transactions grid export can include one); rows that can't be resolved are listed in the preview, never guessed.

What is NOT imported

Common gotchas

Semicolons and ! headers are fine. The canonical Tools, Import/Export file is semicolon-delimited with !FIELDNAME headers. Upload it exactly as exported; Rekomi detects both.

Non-email usernames. Installs where affiliates log in with plain usernames need an email column in the export; rows without any email are skipped and reported.

Letter codes. A/P/D statuses, S/A/U/R/H transaction types, and P/U payout statuses are all understood; you never need to translate them to words.

Verifying the import landed clean

1. Open /dashboard/affiliates and spot-check 3-5 rows against the Post Affiliate Pro source.
2. Open one affiliate's detail page and confirm the preserved Referral ID slug.
3. Click an affiliate's existing ?a_aid= link with the new snippet installed; confirm a click row appears within a few seconds.
4. Run the Step 2 preview and compare its totals against your Post Affiliate Pro transactions grid before confirming.
5. Send a sample notification to yourself before firing the bulk send.

Where to go next

• Tracking and attribution: the a_aid param, cookie window, and stickiness.
• Sub-affiliate recruiting: the Rekomi answer to multi-tier programs.
• Plans and trials: what each tier includes and how the 14-day free trial behaves.