Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Affiliate Marketing › Affiliate Fundamentals

Moving an Affiliate Programme to a New Platform

How to move an affiliate programme between networks or in house without losing partners or sales: inventory, terms, tracking, partner notice and the switch.
Tutorialadvanced10 min readUpdated

Why programme moves lose partners and sales

Whether to move at all is a decision the comparison of affiliate networks and in-house programmes helps make: it sets out where each model wins, and why many programmes keep a network for the long tail while running their most important partners on their own platform. It covers migration only in passing, in an FAQ and two common mistakes: leaving without a migration plan, and not exporting data from the start. This tutorial assumes the decision is made and runs the move.

Moves fail in predictable places. Partners hear about the move from someone else and assume the worst. The new terms are worse, or simply different, and partners compare clause by clause. Tracking on the new platform is switched on the day partners move and has never seen a real sale. Old links keep working on the old platform, so both platforms pay for the same orders. Pending commission on the old platform is forgotten once attention moves, and partners who were owed money tell other partners. The history needed to judge partners stays behind in a platform the business can no longer open. A programme whose best partners went quiet after a move can trace which of these it was, or whether the cause lay elsewhere, with the diagnosis of top affiliates leaving the programme.

Each of those has a step below. The general discipline of switching a tool off, finding its dependencies, reading its contract and exporting what must be kept, is the subject of the tutorial on retiring a marketing tool; this tutorial applies it to a programme where the dependencies include hundreds of independent businesses.

Before you start

  • A recorded decision to move. What is moving where, and why, signed off by whoever owns the programme's budget.
  • A named owner and a responsibility chart. A RACI matrix for the move: who owns tracking, terms, partner communication, finance and the old contract.
  • The old platform's contract. For notice, data exports, access after termination and how pending commission is settled. The business's own advisers read anything uncertain; this tutorial does not interpret contracts.
  • The current terms and every partner-specific deal. Including the reasons each special commission rate exists.
  • A list of partners in order of value. From the programme's own records: validated sales, new customers and quality, not clicks.
  • The integration record. Where the postback, pixels, product feed and any order exports connect; the tutorial on documenting marketing integrations builds one if none exists.
  • The peak calendar. A move should not land in the business's busiest period; the tutorial on planning a change freeze explains how to keep risky changes out of it.

The steps

  1. Fix the scope, the date and who decides

    Write down what moves: the whole programme, or only a group of partners while the rest stay on the old platform. Set a target date for the switch outside any freeze period, and work backwards from it to the dates for terms, tracking tests and partner invitations, as the backward planning framework describes. Agree who can delay the date, and on what evidence. A move with no owner drifts until the old contract renews by default.

  2. Read the contract and export the history

    Read the old contract for notice, for what the platform must provide when you leave, and for how long you keep access afterwards; take advice where it is unclear. Then export, while access is complete: the partner list with the contact and payment details the contract and privacy rules let you hold, rates and deals, clicks and conversions with order references and statuses, rejection reasons and payment history. This history is part of the business's first-party data about its own programme. Check each export opens and matches the platform's own totals before relying on it.

  3. Re-paper the terms on the new platform

    Write the terms partners will sign on the new platform. The aim is terms at least as good as the old ones for the partners you want to keep, and clearer where the old ones were vague. Carry over every partner-specific deal you intend to honour, and decide in advance what happens to those you do not. Make sure the new platform's settings, from the lookback window to the validation period and rates, match the document, as the commission structures guide advises for any change. The programme management hub places the terms among the rules that hold the programme together. The tutorial on writing affiliate programme terms covers drafting them clause by clause.

  4. Rebuild tracking and test it before any partner moves

    Set up the new platform's tracking as the tracking guide describes: links carrying partner and click identifiers, the identifier stored on your own domain, a server-side postback as the main record with a pixel as backup, consent respected. Then test it with real purchases on every path customers use, as the tutorial on tracing missing affiliate conversions replays them: each payment method, guest and account checkout, codes, mobile and desktop. Run the affiliate programme launch checklist, which asks to be run again when a programme moves between platforms. No partner moves until every path records.

  5. Set the deduplication rule for the parallel period

    While both platforms run, both can claim the same order. Decide one deduplication rule before the first partner moves, the same rule the business applies across other channels, as the networks comparison's section on running both and the attribution and deduplication guide explain. Write it into both sets of terms, apply it in validation, and check a sample of orders each week to confirm no order is approved on both platforms.

  6. Talk to the partners who matter first

    Before any announcement, contact the partners at the top of the value list personally. Explain why the business is moving, what changes for them, what stays the same, and when payment will arrive. Ask what would stop them moving. Give them their new links and terms first, and a date by which old links should be replaced. A partner who hears about the move from the brand, early, with answers ready, is far more likely to follow it.

  7. Announce to everyone else with notice and new links

    Then tell the rest of the partner base, with the notice your old terms and contract require. The message gives the date, the reason, the new terms, how to join the new platform, how to replace links and what happens to commission already earned. Treat joining as onboarding: the tutorial on onboarding and activating new affiliates covers the welcome pack, the first offer and the follow-up for partners who go quiet. Track who has joined and who has replaced their links.

  8. Run both platforms in parallel and watch the gap

    During the parallel period, compare each moved partner's sales on the new platform with what they produced on the old one, and the programme's total with orders in the order system. A partner whose sales fall after moving has probably left old links in place, or has a link that does not record. Check the partner's live pages, and trace any gap rather than assuming the partner stopped promoting.

  9. Settle pending commission on the old platform

    Keep validating conversions on the old platform until every one inside the lookback window and the validation period has been approved or rejected, then make sure the final payments reach partners. Reconcile what was approved with what was paid. Unpaid commission from the old platform is the single fastest way to undo the trust the move needed. The tutorial on closing the month on affiliate commissions covers the validation and invoice match to keep running on the old platform until the last conversion settles.

  10. Close the old platform and update the records

    When the parallel period ends, set the old programme to stop accepting new clicks as the contract allows, take a final export, remove users and integration credentials, and request deletion as the retiring a tool tutorial describes. Remove the old pixel and postback so they do not fire into a closed account. Update the integration record, the terms archive and the partner list, and note in the reporting history the date each partner moved, so that later comparisons do not mistake the move for a change in performance. The measurement hub covers the reporting the programme returns to afterwards.

What moves, what stays and what is closed

Not everything on the old platform moves. The table sorts the main items so that nothing is moved by default or lost by default.

ItemMovesStays until settledClosed or deletedNotes
Partner relationshipsPartners you invite and who joinPartners not yet movedPartners you decide not to invite, with noticeContact the most valuable first
TermsNew version, at least as good for key partnersOld terms govern old conversionsOld version archivedSettings must match the document
Partner-specific dealsThose you honour, written inUntil old conversions settleThose you end, with noticeRecord why each exists
Tracking linksNew links issued to each partnerOld links run during the parallel periodOld programme stops taking clicks at the endCheck partners' live pages
Postback and pixelRebuilt and tested on the new platformOld ones until the end of the parallel periodRemoved from the siteOne deduplication rule throughout
Click and conversion historyExported in fullReadable on the old platform while access lastsDeleted on request after exportCheck exports against platform totals
Pending commissionNoneValidated and paid on the old platformAccount closed after final paymentReconcile approved with paid
Product feed and creativeReconnected to the new platformOld feed until closeOld connection removedUpdate the integration record

A tool retailer moves its top partners in house (illustrative)

Illustrative example — not a real result

Vothram Tools brings its top partners in house

Vothram Tools, an invented woodworking tools retailer, has run its programme on a network for six years. It decides to move its partners to an in-house platform, keeping nothing on the network once the move is complete. It sets the switch for late February, well clear of its December peak and its spring sale.

It reads the network contract with its adviser, finds a notice period of 90 days and a right to export, and exports two years of partner, click, conversion and payment history in January, checking the totals against the network's reports. It writes new terms matching the old rates for its 40 most valuable partners and keeping their special deals, and rebuilds tracking with a server-side postback. A test on 9 payment and checkout paths finds that orders using gift cards do not record; it fixes the trigger and retests before any partner moves.

The programme manager calls the top 40 partners in the first week of February; 36 agree to move and receive new links and terms. The rest of the 410 partners get notice, new links and a welcome pack. Both platforms run for 60 days with one rule: the last affiliate click before the order is paid, on whichever platform recorded it, never both. A weekly sample of 100 orders finds 2 approved on both early in the period, which Vothram reverses before payment.

Network conversions are validated and paid until the last one settles. Vothram takes a final export, removes the network's pixel and postback, requests deletion and closes the account. Of the 410 partners, 212 moved; they had produced 94% of validated sales the year before.

Common mistakes

  • Announcing before the tracking works. Partners who move to a platform that does not record their sales do not move twice. Test every path first.
  • Exporting at the end. Access narrows once notice is given. Export early, check the files and keep a final export for the close.
  • Worse terms for the partners who matter. Key partners compare clause by clause. Match or improve their terms, or expect them to stay behind.
  • Letting key partners hear it second-hand. Call them before the general announcement.
  • Two platforms, no single rule. Without one deduplication rule, both platforms pay for the same orders.
  • Forgetting the old platform's pending commission. Validate and pay to the last conversion, and reconcile.
  • Leaving the old pixel on the site. A tag firing into a closed account is a data flow nobody manages.
  • Reading the move as a performance change. Record the date each partner moved so later reports are read correctly.

Frequently asked questions

Will every partner follow us to the new platform?

Probably not, and the plan should assume so. The networks comparison notes that partners who rely on a network for consolidated payment, or who only work through networks, may not join a direct programme, while partners with a strong relationship with the brand usually will if the move is planned, the terms are at least as good and payment is reliable. List the partners who matter most, talk to each before the announcement, and plan the move around them rather than around the whole list.

How long should both platforms run at the same time?

Long enough for the partners you want to move to switch their links, and for conversions from old links still inside the lookback window to finish; no longer. The right period comes from your own records: how long your most important partners took to update links in the past, your window, and your validation period on the old platform. Throughout, apply one deduplication rule so the same order is never paid on both platforms.

What data should we export before leaving a network?

Everything you would need to run the programme, settle disputes and judge partners later: the partner list with contact and payment details as the contract and privacy rules allow, commission rates and any partner-specific deals, click and conversion history with order references and statuses, rejection reasons, and payment history. Read the contract for what the old platform must provide and how, and export early, while you still have full access. The networks comparison advises asking for regular exports from the start for exactly this reason.

Terms used on this page

Frameworks

Where this page is used

Related