FirstPromoter is built for SaaS and subscription businesses. Its public pricing page lists Starter at $49/month up to $5,000/month revenue from affiliates, Business at $99/month up to $15,000/month, and Enterprise starting at $149/month above that.

That makes FirstPromoter a serious option. A migration to RefCampaign should be based on fit, not criticism. For some teams, the reason is EU hosting. For others, it is pricing, French support, or a desire to keep the affiliate program tightly aligned with Stripe-native workflows.

Use this checklist when you already have a FirstPromoter program and want to move without breaking partner trust.

## Confirm the migration trigger

Review [FirstPromoter pricing](https://firstpromoter.com/pricing) and your own usage before deciding.

Migration is worth considering when:

- Your affiliate revenue is growing and pricing thresholds matter.
- Your buyers ask more questions about GDPR, hosting and data processing.
- You want a lighter founder-led program before hiring partner operations.
- You want Stripe subscription tracking, commission approvals and payout workflows in one SaaS-focused setup.

If the current program is profitable and operationally calm, do not rush. Start with an audit: affiliate count, active revenue, unpaid balances, manual work per month and partner satisfaction.

## Export the working parts

Capture the current program before rebuilding it.

Export or document:

- Active promoters and their emails.
- Referral links, coupons and landing pages.
- Campaigns and commission structures.
- Cookie duration and attribution model.
- Pending, approved and paid commissions.
- Any custom terms for strategic partners.

FirstPromoter's feature table references webhooks, API, Stripe coupons, PayPal/Wise payouts, refunds and chargebacks. If you use any of those features, list exactly how they affect your program before recreating rules elsewhere.

## Recreate policies, not clutter

Migration is a good time to simplify.

Keep:

- Commission rates affiliates actually use.
- Approval windows tied to refunds or chargebacks.
- The payout schedule affiliates expect.
- Active links from partners who still produce traffic.

Drop:

- Old campaigns with no traffic.
- Special rates without an owner.
- Landing pages affiliates stopped using.
- Automation rules nobody can explain.

For strategy, pair this with [how to pay affiliates in SaaS](/en/blog/how-to-pay-affiliates-saas) and the [affiliate program metrics guide](/en/blog/affiliate-program-metrics-kpis).

## Cut over tracking carefully

The default migration pattern:

1. Create the RefCampaign program.
2. Recreate active affiliates.
3. Generate new links.
4. Test click capture, signup attribution and paid Stripe conversion.
5. Move two or three active affiliates first.
6. Reconcile commissions in both systems.
7. Move the rest of the affiliate base.
8. Freeze FirstPromoter approvals after the cutoff date.

Do not approve the same conversion in both tools. Define the cutoff rule before the first affiliate updates a link.

## What to tell affiliates

Your message should answer:

- Why the link changed.
- Whether old links still work temporarily.
- How pending commissions will be paid.
- When the new dashboard becomes the source of truth.

Avoid a long vendor comparison. Affiliates want continuity.

If you are still choosing between tools, read [RefCampaign vs FirstPromoter](/en/compare/refcampaign-vs-firstpromoter), review [RefCampaign pricing](/en/pricing), or [contact us](/en/contact) with the commission rules you want to preserve.

The best migration feels uneventful. Affiliates keep promoting, finance can reconcile commissions, and the founder gets a simpler program tied to real SaaS revenue.