Migrating an existing program
After this track you can
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.
If you already run an affiliate program on another platform, or on something your own developers built, this is where you start. The move itself is short: the data migration is about a day of work, and we do it with you. What takes judgement is everything around it: knowing why you are really moving, deciding what has to survive, telling your affiliates in the right order, and cutting over without paying anyone twice.
Five lessons, in the order the move happens. Most teams who move come from PartnerStack or Impact, so lesson 2 is written for them: what changes, what stays, and how to time the switch around your renewal. When you are done, rejoin the timeline at Track 3, because a migrated program arrives with affiliates who need activating, not recruiting.
Syllabus
Lessons in this track
- 1Know why teams really migrate, and when we tell you not toSeparate 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. 7 min read Video coming soon
- 2Coming from PartnerStack or Impact: what changes, what stays, and when to switchUnderstand, 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. 7 min read Video coming soon
- 3Protect what must survive: links, historical commitments and payoutsKeep 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. 7 min read Video coming soon
- 4Tell your affiliates in the right order, with the templatesAnnounce 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. 6 min read Video coming soon
- 5Run the cookie overlap, then cut over to one platformRun 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. 6 min read Video coming soon
What "in trouble" looks like at this stage
Every academy teaches the happy path. These are the signals we see in programs that are going quietly wrong at this exact point, and the lesson that deals with each one.
Your program never grew on the old platform and you expect the move to fix it
Migrating does not fix a program that has not worked. Grow it first, then move.
Fix it: Know why teams really migrate, and when we tell you not toYou plan to announce the move from inside the tool you are leaving
Your brand should say it first. The old tool's email is the last thing affiliates should hear.
Fix it: Tell your affiliates in the right order, with the templatesOpen payouts are still sitting in the old tool on cutover day
Payouts are where migrations break. Clear them, or migrate them, before the switch.
Fix it: Protect what must survive: links, historical commitments and payoutsBoth platforms have been live for four months
The overlap is for the cookie window, not for avoiding a decision.
Fix it: Run the cookie overlap, then cut over to one platformYour annual renewal is weeks away and the migration has not started
The overlap alone takes 30 to 60 days. Plan the Stripe date backwards from the renewal, or accept one more term and plan properly.
Fix it: Coming from PartnerStack or Impact: what changes, what stays, and when to switch