PartnerStack is built for broader B2B partner ecosystems. Its public [platform page](https://partnerstack.com/) highlights partner recruitment, activation, tracking, commissions and optimization, while its [pricing page](https://partnerstack.com/pricing) lists paid plans by partner motion and custom enterprise paths.

That is useful context, not a reason to attack the product. If you are moving from PartnerStack to RefCampaign, the reason should be operational fit: a leaner affiliate program, Stripe-centered revenue attribution, clearer founder-led workflows, or a simpler path from partner activity to paid subscription revenue.

## Start with the current partner system

Before rebuilding anything, separate your affiliate program from the rest of your partner motion.

Write down:

- Active affiliates who drove clicks or revenue in the last 90 days.
- Referral partners, resellers and agency partners that should not move yet.
- Current commission rules, partner groups and special terms.
- Links, coupon codes, approved assets and partner resources.
- Pending commissions, payout timing and refund rules.
- Reporting views the team uses to understand partner-sourced revenue.

PartnerStack can support more than a simple affiliate program. The migration goes faster when you decide which partners belong in RefCampaign and which still need a broader partner ecosystem workflow.

If the current problem is measuring what affiliates actually contribute, review the [affiliate analytics feature](/en/features/affiliate-analytics) before you rebuild the program.

## Decide what changes in RefCampaign

A migration is not a copy-paste exercise.

Keep the parts that protect partner trust:

- Commission rates for active revenue-generating affiliates.
- Payout schedule and minimum payout threshold.
- Existing partner resources that are still accurate.
- Any promise already made to a strategic partner.

Change the parts that make the program hard to operate:

- Partner types that are mixed together in one workflow.
- Reports that do not map cleanly to Stripe subscription revenue.
- Manual reconciliation between affiliate activity and paid invoices.
- Approval steps that slow down a founder-led SaaS team.

RefCampaign is a better fit when affiliate tracking should stay close to Stripe billing and the team wants a direct view of partner revenue. For the broader strategic trade-offs, use the [RefCampaign vs PartnerStack comparison](/en/compare/refcampaign-vs-partnerstack).

## Move active affiliates before the long tail

Do not migrate every partner profile at once.

Start with the affiliates who still send traffic or revenue:

1. Create the affiliate in RefCampaign.
2. Recreate their primary tracking link or campaign.
3. Test click tracking and a paid Stripe event.
4. Send a transition note with the new link and payout continuity details.
5. Watch one full subscription or invoice-paid cycle before expanding the rollout.

This avoids spending time on inactive partners while the revenue-driving group still needs support. If you are also segmenting high-value B2B partners, the [high-ACV affiliate marketing guide](/en/blog/b2b-affiliate-marketing-high-acv) can help decide who needs a custom track.

## Reconcile commissions before closing the old workflow

Finance should be able to answer four questions before PartnerStack is retired:

- Which commissions are pending in PartnerStack?
- Which payouts have already been approved?
- Which partners moved to RefCampaign?
- Which refunds, cancellations or clawbacks still belong to the old period?

Write one cutoff rule. Example: "Clicks before July 15 stay in PartnerStack unless the affiliate updates their link earlier; clicks from July 15 onward are tracked in RefCampaign."

The rule matters more than the tool. Affiliates should never wonder where a commission went.

## Migration checklist

Use this sequence:

1. Audit partner types and isolate the affiliate program.
2. Export active affiliates, links, coupons and commission rules.
3. Document pending payouts, refunds and cutoff policy.
4. Rebuild the core affiliate program in RefCampaign.
5. Test Stripe attribution and reporting end to end.
6. Move top revenue affiliates first.
7. Notify the remaining active affiliates.
8. Keep old reporting available until finance closes the transition period.

When you are ready to compare the operating model, read [RefCampaign vs PartnerStack](/en/compare/refcampaign-vs-partnerstack), check [RefCampaign pricing](/en/pricing), or review how teams [scale an affiliate program toward 100K MRR](/en/blog/scale-affiliate-program-100k-mrr).

The migration succeeds when the partner experience feels boring. Links work, commissions remain visible, payouts stay predictable, and your SaaS team gets a clearer connection between affiliate activity and paid revenue.