# Import partners and review migration liability

Preview imported membership/referral evidence before applying it.

## What you need

The correct program/group, a prepared CSV and permission to review any historical financial liability. Imported paid history is evidence, not a verified receipt.

## Steps

1. Open affiliate **Imports** and choose the target program and history policy.
2. Map supported columns: `email`, `first_name`, `last_name`, `group_id`, `group_invite_link`, `shop_domain`, `referred_at`, `external_paid_amount`, `currency` and `payment_reference` as applicable.
3. Preview. Review row errors, duplicates, group/program conflicts, merchant identity and historical reward/payment evidence before applying.
4. Apply only the reviewed preview. Have imported partners claim their account through their own emailed claim path.
5. Review migration-payment evidence separately. Check the liability decision and keep administrative treatment distinct from a partner receipt confirmation.

## Expected result

Applied membership/referral data with explicit import decisions. Historical payment evidence does not silently mark a new payout as received.

## Merchant contact imports

Merchant contacts use a separate **Developers → Import contacts** workflow and CSV shape. They do not create affiliate attribution or payment evidence. See [Contact import](/docs/developers/contact-import).

## Troubleshooting

Correct mapping, invalid domains/dates/currency, duplicate identities and conflicting program/group references in the source CSV, then create a fresh preview. Resolve migration liability before using historical paid amounts in a live balance.