Back to Migration track

Reditus Academy · Migration track · If you already run a program somewhere else

Reditus

Migrating an existing program: the checklist

Move an existing program without losing affiliates: know why you are really moving, what must survive, how to tell your partners, and how to cut over cleanly.

Print it, or save it as a PDF, and work down it. Each step says how much counts as done. Full lessons at getreditus.com/academy/migrating-an-existing-program

By the end of this track you have

  • The real reason you are moving, written in one sentence, and a check against the two cases where we tell you not toA program that never grew on the old platform does not grow because it moved.
  • Your renewal date, notice deadline and cookie window written down, with the Stripe date planned backwards from themThe overlap alone takes 30 to 60 days. Nothing renews by accident.
  • Every affiliate link still working after the move, and legacy terms rebuilt as a private legacy tierLinks and historical commitments are what affiliates check first.
  • Open payouts cleared or migrated before cutover dayPayouts are where migrations break.
  • Your own announcement sent before anything from the old toolAffiliates should hear it from your brand, not from the platform you are leaving.
  • One platform, after the cookie-window overlapThe overlap is for the cookie window, not for avoiding a decision.

Lesson 1

Know why teams really migrate, and when we tell you not to

Separate the stated reason from the real one (a program that went zero to one and plateaued because the own network dried up), and recognise the two cases where migrating fixes nothing.

  • Write the real reason you are moving in one sentence, and check it against the two cases where a move fixes nothingTarget: One sentence, one checkMost teams say tracking or price. The real reason is usually a plateau after the own network ran dry, and a move only helps if a network is what you are moving to.

Lesson 2

Coming from PartnerStack or Impact: what changes, what stays, and when to switch

Understand, in plain words, what moving from PartnerStack or Impact to Reditus changes for you and for your affiliates, what you give up, and how to time the switch backwards from your renewal date so you never pay for two platforms.

  • Write down three dates: your renewal date, your notice deadline, and your current cookie windowTarget: Three dates on one lineThe cutover is planned backwards from the renewal, and the tracking overlap alone takes 30 to 60 days.
  • Decide in one word whether what you run is affiliate-shaped or partner-shapedTarget: Affiliate, or partnerPartners who co-sell and need your CRM need the PRM you are on. People who recommend you for a commission do not.
  • Export your current commission terms and book the migration call with them in handTarget: Every term mapped before the data movesBounties, one-time and lifetime terms each need a decision on the review call, not a surprise afterwards.

Step-by-step in the help centre

  • Migrate Your SaaS Affiliate Program to Reditus in 5 Steps · getreditus.com/help/migrate-your-affiliate-program-to-reditusThe five steps of the migration, in order.
  • How to notify affiliates after migrating to Reditus (with email templates) · getreditus.com/help/migrate-affiliate-program-reditus-email-templatesThe emails to send your affiliates about the move.

Lesson 3

Protect what must survive: links, historical commitments and payouts

Keep every affiliate link working, rebuild legacy lifetime and multi-year terms as a private legacy tier, clear open payouts in the old tool, and treat payouts as the one area that breaks.

  • List every legacy term that must survive: lifetime deals, multi-year rates, special partnersTarget: The list, before the data moveThese become a private legacy tier with end dates per referral. Nothing is rebuilt from memory afterwards.
  • Clear or export every open payout in the old toolTarget: Zero open payouts on cutover dayPayouts are where migrations break, and the first question every affiliate asks.

Step-by-step in the help centre

  • Migrate Your SaaS Affiliate Program to Reditus in 5 Steps · getreditus.com/help/migrate-your-affiliate-program-to-reditusThe migration steps.
  • Manually uploading referrals (SaaS) · getreditus.com/help/uploading-referrals-as-a-saasImport referrals by hand where needed.

Lesson 4

Tell your affiliates in the right order, with the templates

Announce from your own brand first, then trigger the password reset, expect activity to rise rather than fall, and answer the one question they will all ask: payouts.

  • Send your own announcement, from your brand, before any email from either platformTarget: Your email firstWould you use the tool you are leaving to announce you are leaving it.
  • Put the payout answer in that email: what happens to open commissions, and when the first payout from the new platform landsTarget: The payout paragraph, in email oneIt is the one question every affiliate will ask. Answer it before they do.

Step-by-step in the help centre

  • How to notify affiliates after migrating to Reditus (with email templates) · getreditus.com/help/migrate-affiliate-program-reditus-email-templatesThe notification sequence with the email templates. Adapt, do not rewrite.

Lesson 5

Run the cookie overlap, then cut over to one platform

Run both trackers for the old cookie window (30 to 60 days), connect Stripe on the first of a month so nothing is double paid, and decide deliberately whether a longer parallel test is worth the focus it costs.

  • Connect Stripe on the first of a month and mark that month's commissions as paid in the old toolTarget: Cutover on the 1stThat is how nothing gets paid twice.
  • Put the date both trackers come off in the calendarTarget: Old cookie window plus a few daysSome companies run both for a while to compare. It works, and it costs focus. Decide the end date now.

Step-by-step in the help centre

  • Connecting Stripe · getreditus.com/help/connecting-stripeConnect on the first of a month.