Migrate from LeadDyno to RefCampaign: a Stripe SaaS checklist

LeadDyno's pricing page publishes affiliate software plans starting at $49/month with a 30-day trial, unlimited clicks and conversions on every plan, and plan limits based on active affiliates, reward structures and commission plans. Its Stripe support page also explains that users can view affiliate sales, commissions, traffic and affiliate counts inside Stripe through the LeadDyno app.

That is useful context, not a reason to attack the product. If you are moving from LeadDyno to RefCampaign, the reason should be operational fit: Stripe subscription attribution, simpler SaaS reporting, EU hosting, or a program that does not need a broader e-commerce-style setup.

Start with the current affiliate setup

Before rebuilding, list the parts that affect affiliate trust.

Document:

• Active affiliates and their current links.
• Promo codes or product-specific code rules.
• Reward structures, commission plans and affiliate groups.
• Historic data exports you still need for finance.
• Pending commissions, approved payouts and refund handling.
• Any Stripe reporting your team uses from the LeadDyno integration.

The goal is not to copy every setting. The goal is to preserve what affiliates depend on while simplifying the parts your SaaS team actually operates.

If the reason for the move is Stripe depth, start with the Stripe affiliate software page and the Stripe affiliate tracking feature.

Decide what changes in RefCampaign

Keep the pieces that would create confusion if they changed overnight:

• Active affiliate links or redirect strategy.
• Commission rate and payout cadence for current affiliates.
• Rules for refunds, cancellations and pending commissions.
• Messaging around when the new system becomes official.

Change the parts that are too broad for a SaaS affiliate program:

• Reward structures that no longer map to subscription revenue.
• Affiliate groups that exist only because of old tool limits.
• Reports that need manual reconciliation against Stripe invoices.
• Workflows that mix customer referrals, e-commerce codes and SaaS affiliates.

RefCampaign should become the cleaner source of truth for Stripe-paid affiliate revenue. For tool-specific differences, read RefCampaign vs LeadDyno.

Move revenue affiliates first

Start with the affiliates who can prove the migration is working.

For each active affiliate:

1. Create the affiliate in RefCampaign.
2. Recreate or redirect their primary link.
3. Test a click, signup and invoice-paid event.
4. Confirm the commission appears with the expected status.
5. Send the affiliate a concise note with the new link and cutoff date.

If your program is still being designed around Stripe, the guide to Stripe affiliate software for SaaS can help decide which events should count before you migrate everyone.

Reconcile payouts and refunds

Do not close LeadDyno until the old accounting window is clean.

Finance should confirm:

• Which commissions are pending in LeadDyno.
• Which commissions are approved but unpaid.
• Which commissions moved to RefCampaign.
• Which refunds or cancellations still affect the old period.
• Which data export should be archived for audit purposes.

Use one cutoff rule. Example: "Conversions before July 15 are paid from LeadDyno; invoice-paid events from July 15 onward are tracked in RefCampaign."

Migration checklist

1. Export affiliates, links, codes, groups and commission plans.
2. Document Stripe reporting and finance exports.
3. Decide the cutoff date and refund policy.
4. Rebuild the core affiliate program in RefCampaign.
5. Test click-to-paid attribution through Stripe.
6. Move active revenue affiliates first.
7. Notify the remaining affiliates with their new links.
8. Keep LeadDyno accessible until final payouts are reconciled.

When you are ready to compare the fit, read RefCampaign vs LeadDyno, review RefCampaign pricing, or map the setup against the affiliate program with Stripe guide.

The migration succeeds when affiliates do not feel the tool change. Their links work, their commissions remain explainable, and your team gets cleaner Stripe-based reporting.