The new affiliate dashboard looks great. The partners have their replacement links. Then someone asks a perfectly reasonable question: what happens to the customer who clicked an old link yesterday and buys tomorrow? If the room goes quiet, the migration isn't ready.
I'd judge a platform move by whether the team can explain a partner's credit and payment after the switch. Start there, rather than with the launch announcement. A clean-looking dashboard won't help much when a publisher is asking where a commission went.
Start with the money that is still in motion
Consider a fictional program preparing a November 1 cutover. The old platform shows $12,000 in approved commissions, $800 pending review and a $300 disputed adjustment. The tempting move is to put everything in one opening-balance cell and get on with the migration. That creates a number nobody can explain.
Keep three separate records. Finance checks which of the approved $12,000 is already paid, scheduled for payment or still unpaid. The program manager owns the pending $800 until its review is finished. The $300 adjustment stays separate until its direction and treatment are settled. An adjustment might increase or reduce what is owed; its size alone doesn't tell you which.
This distinction changes the next action. If $5,000 of those approved commissions has already been paid, copying all $12,000 into a new payable list creates an obvious problem. Preserve the payment references and have finance confirm the unpaid amount. You need a traceable balance, not a fresh label for an old total.
Keep the transaction reference, partner identifier, currency, relevant dates, commission status and payment evidence together in the approved working files. The project summary can point to those files without sharing a complete partner payment export with everyone in the launch meeting.
Provider labels deserve a close look, too. For Awin Classic, Awin's invoice guide describes reconciling the invoice period against Validation Date and Approved transaction status. Check the fields your own platform uses before comparing totals. Two reports called 'November commissions' may answer different questions.
Follow one customer across the switch
Now follow the customer who clicked the old link on October 31 and purchased on November 2. Before testing, agree which referral is eligible, which record supports credit, which system calculates the commission and which process pays it. Check the applicable terms with the platform and responsible agreement reviewers. A replacement link doesn't answer those questions on its own.
For this example, the test sheet starts with: 'Old referral, purchase after cutover. Expected crediting treatment: awaiting confirmation. Duplicate check: compare the merchant order reference across both systems.' The path stays open until the expected result is agreed and the authorized test matches it. Seeing an order appear somewhere is not a passing result.
Test a normal new-link purchase as well as the exceptions that matter to the program: a cancellation, a refund, an earlier referral and any relevant discount-code or recurring-order path. Use the platform's authorized test method and keep test transactions distinguishable from real partner balances.
If the same order appears in both systems, investigate what each record does. Two records do not necessarily mean two payments. The concern is whether both can enter a payable commission process. Record the order reference, expected treatment, observed result and the person resolving the difference.
Ask partners about placements, not just links
An email delivered to a partner is a start. Their placements may sit in a review controlled by another editor, a newsletter already locked for production or an old comparison page nobody has visited in months. Ask where the active links actually live and who can update them.
Map the old partner identifier to the new one, then list the placements, agreed commission arrangement and unresolved questions. Start with partners whose active promotions would be most disruptive to lose. A long contact spreadsheet can make a migration look organized while the important placements remain untouched.
Once the details are confirmed, a useful notice could read: 'Hi Alex, we're preparing a platform change for November 1. Please review the replacement links and your placement list in the brief. Which placements can you update, and which need another editor? Please keep the current links in place until we confirm the cutover after testing. Maya is your contact for link questions; payment-status questions remain with our finance team.'
That message gives Alex something specific to do and keeps the date conditional until the team is ready. Confirm reporting access, payment handling and any commercial changes separately. Don't bury a change to commission terms inside a routine link-update email.
Make the launch meeting settle three questions
The program manager should be able to show which priority partners are ready and who owns each exception. Finance should be able to explain the opening payable balance and unresolved amounts. The technical owner should be able to show that the agreed transaction paths and duplicate checks passed.
In our example, the approved $12,000 has been reconciled with paid and unpaid amounts identified. The $800 still has a validation owner. The $300 adjustment remains unresolved and outside the confirmed payable total. Normal purchases and refunds pass, but the earlier-referral path doesn't yet have an agreed treatment. My decision would be to hold the cutover until that path is settled.
If the team proposes moving only a smaller part of the program, write down the affected partners, the paths they use and the control that makes the narrower move workable. Give that proposal a real review. A failed full-program test shouldn't quietly become permission for a partial launch.
Know what you will pause if a live check fails
Suppose the first live review finds an earlier referral missing from the expected report. Pause additional partner link changes while the technical owner traces that order reference. Keep genuine payable balances separate from test records, and give affected partners a specific time for the next update.
Don't restore the old tracking configuration on instinct. Check whether doing so would lose new referrals, create duplicates or change the agreed crediting treatment. Save the approved before-change configuration and destinations, with secrets protected, and name who can apply and verify a recovery change.
The restart decision should be equally concrete: the expected treatment is confirmed, the test produces the matching record, duplicate checks pass and the responsible reviewers accept the evidence. 'The dashboard looks normal again' leaves too much room for another surprise.
Close the old system when the records are ready
Put access, export and termination dates in the migration plan. Before access ends, check that the required reports, invoices, agreements and unresolved cases remain retrievable in approved storage. Retention and termination requirements depend on the program's agreements and circumstances, so have the appropriate reviewers confirm them.
After the first agreed reporting and payment cycle, reconcile the same transaction references again. Follow up on partner questions and keep corrections traceable. Don't replace the opening record with a cleaner-looking total that hides what changed.
If you're still choosing the operating model, the network versus in-house comparison covers fees and management responsibilities. Experience Advertising can help organize program work, and AffiliateFinders supports potential-partner discovery and contact research. Evan Weber founded both businesses. Those services don't replace the platform, finance and agreement checks a migration needs.
Before booking the cutover, bring one mapped partner, one reconciled balance and one tested exception to the meeting. If the team can walk through all three without guessing, the launch date becomes a decision you can defend.
Have both teams sign off on the final unresolved balance list. If the move follows a partnership announcement, use the Rakuten and impact.com transition questions.
