Imports

Moving an affiliate program is mostly moving its history. Import brings partners, customers and transactions in from a spreadsheet or straight from the platform you are leaving, with a dry run before anything is written and a rollback if you change your mind. Your partners' published links keep working through the move: each imported partner keeps their old referral token, and the tracking script captures the link parameters other platforms use, so a link in a partner's yearly review keeps converting.

Sources

• CSV file: any spreadsheet, up to 5 MB per file. You map the columns yourself, with the obvious matches pre-filled from your headers.
• Direct from your previous platform: the picker names the four affiliate platforms we import from directly. You paste your own API key from that platform; it is used read-only, encrypted for the run, and removed when the run finishes. Nothing is changed on the other side, so the platforms can run in parallel while you switch over.

What comes across

Three kinds of record, each its own file or fetched for you:

• Partners: one row per partner. Email is required; their referral token keeps their old links working.
• Customers: one row per referred customer, with the partner who referred them, so recurring commissions keep accruing to the right person.
• Transactions: one row per payment, with the customer, the partner, the amount and the date. A row with no amount imports as a lead.

Statuses are translated to ours on the way in, and money arrives as proper amounts with a currency.

Dry run, run, rollback

Every import dry-runs first: the full pass, counting what would be created, updated, skipped and failed, without writing anything. Read the numbers, fix the mapping if something looks off, and run it for real only when the dry run reads right.

The history table keeps every run with its counts. If an import turns out wrong, rollback undoes it in one click: everything that run created is removed, and everything it updated is restored.