Know why teams really migrate, and when we tell you not to
After this lesson you can
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.
Know why teams really migrate, and when we tell you not to

Ask a team why they want to move their affiliate program and you get the reason they have rehearsed: the price, the cost against what they use, wanting everything in one tool, or simply "we want a marketplace". Those reasons are real. They are rarely the one that made someone open the conversation.
The reason underneath
Across the migration conversations we have had, the same shape keeps appearing. The program went from zero to one. The founder invited their own users, a few consultants, maybe an agency or two. Some revenue came in. Then it stopped growing, because the people they could reach by hand were all reached, and finding the next batch of affiliates one cold email at a time turned out to be slower than anyone budgeted for. Sometimes nobody owns the program any more. Sometimes the admin around payouts has become the thing people dread each month. Sometimes engineering wants the custom referral code out of the product.
That plateau is the real reason, and it matters because it tells you what a move can and cannot fix. A move to a network changes one thing above all: you go from a silo, where you only ever get the affiliates you personally recruit, to a marketplace where affiliates who already promote B2B SaaS can find you and apply. Add campaigns, where you pay affiliates for a specific piece of work, and you have a way to restart activity rather than wait for it.
When we tell you not to move
Two cases, and we say them out loud on calls.
- You are happy where you are. You only ever want your own affiliates, your current tool talks to your payment processor natively, and the admin does not hurt. A move gives you a network you have said you do not want. Stay.
- The program never grew at all. A few affiliates signed up, nobody published, no revenue came. Migrating does not fix a program that has not worked, because the platform was never the constraint. The constraint was that your own users were not recommending you yet.
Why should our network start recommending their SaaS if even their own users are not recommending them?
That is the question we ask ourselves before taking a migration on. If the honest answer is "they would not", the right move is to grow first. The Growth plan exists for exactly that: set the program up, invite your own network, see whether people recommend you, keep the cost low, and move into the network once they do.
What to expect
Any migration is free and done with you: we get access to your current tool, export the data, prepare it, review it with you on a call, and import it. The data work is about a day. The part that takes calendar time is the cookie overlap in lesson 4, which is 30 days for most programs and sometimes 60. Nothing about your affiliates' links changes on their side. If you are coming from one of the platforms we migrate from most often, there is a step-by-step guide for each: FirstPromoter, Rewardful, PartnerStack and Tolt.
What to expect
Ballpark figures for this stage. Not promises: your trial length and how you recruit move them in both directions.
Want the band for your own program? Run the timeline calculator. Two minutes, no signup.
Key takeaways
- The stated reason for moving is usually price or consolidation. The real one is a plateau: the own network ran dry and recruiting by hand is slow.
- A move changes one thing above all: from a silo you fill yourself to a marketplace that produces inbound applications.
- Do not move a program that never grew, or one you are happy with. Migration fixes the ceiling, not the foundation.
- The data migration is about a day and it is free. The calendar time is the cookie overlap.
The detail lives in the help centre
This lesson tells you the order and the judgement. The clicks are in the articles below. Open one, do the step, and you will find a way back to this lesson at the top of the article.
Reference: read if you need the detail
Background you can skip on a first pass.
Do this before the next lesson
Each step says how much counts as done. Doing a third of it and moving on is how programs stall.
Logged in? These open the right screen in your Reditus account. Not a customer yet? They take you to signup first.
Questions we hear at this point
Can we leave our existing affiliates on the old tool and add new ones on Reditus, so nobody has to change links?
We do not recommend it as a permanent setup. Two trackers on one funnel means the same customer can be attributed twice, affiliates complain, and you have handed anyone who wants to game the system a way to do it. Nobody has to change links in a migration anyway: existing links keep working. Some companies do run both platforms for a while to compare, which works, but it costs focus. If you do it, set the end date before you start. Lesson 4 covers the cutover.
Is the migration really free?
Yes. We get access to your current tool, export the data, prepare the import, review it with you, and import it. The only thing we ask you to do first is the technical installation, so tracking is verified before anything moves.
How long does a migration take?
The data work is about one day. The real duration is the overlap period, during which both trackers run so that clicks made before the move still get attributed: 30 days for most programs, sometimes 60, matched to the cookie window of the platform you are leaving.
Finished this lesson?
Saved in this browser only. No account, no certificate, nothing sent anywhere.
