How can you preserve affiliate attribution during a Paddle Classic migration?
Short answer: preserve a durable, merchant-owned mapping between Classic subscriptions, referred customers, partner attribution and historical commission payments before moving subscriptions to Paddle Billing. Then connect the imported Billing subscription to that original record and test future renewals and refunds. Never assume an imported subscription represents a new referred customer.
Paddle's migration plan confirms Classic and Billing data stay separate when Billing is activated. Its subscription migration guide documents a dashboard port process, but clearly labels the migration screens early access. Check availability with Paddle; do not tell merchants that every account can immediately migrate through the dashboard.
Export your affiliate and subscription inventory
Before attempting to port any customer, record the Classic subscription identifier, customer reference, agreed referring partner, partner referral identifier, initial paid transaction, commission duration and percentage, any unpaid pending commissions, issued payouts, refund liabilities and the next renewal date. Retain the original attribution agreement or policy version.
Keep the customer data in a restricted finance ledger with stable merchant-side IDs and access logging. This prevents referral ownership from disappearing when Paddle generates new Billing customer and subscription records.
| Old or merchant-side field | Billing-era mapping | Purpose |
|---|---|---|
| Classic customer identifier | customer.import_meta.external_id | Reconcile original customer |
| Classic subscription identifier | subscription.import_meta.external_id | Connect old subscription to imported one |
| Approved affiliate referral owner | Merchant attribution ledger | Prevent partner ownership loss |
| Paid and pending commissions | Historical ledger entries | Prevent duplicate acquisition payouts |
Practical migration and attribution checklist
- Build your Billing integration first. Paddle Billing uses a new API, Paddle.js v2 and different webhooks. Keep existing Classic billing working during a controlled transition.
- Verify Billing transactions and renewals. Paddle's migration documentation specifies at least one completed Billing transaction and at least one subscription renewal before starting the supported port process.
- Map the product catalog. Check plans, prices, billing intervals, override prices and tax configuration. Use a staging mapping sheet, not email or price alone.
- Freeze the affiliate ledger snapshot. Record partner ownership, earned periods, last paid Classic invoices and pending refunds.
- Subscribe to imported events. Handle
customer.imported,subscription.importedand other relevant imported events rather than assuming thatcreatedevents fire for ported subscriptions. - Start with a small pilot. Verify customer identity, product mapping, next renewal, commission owner and the correct billing state.
- Reconcile Classic and Billing. Check that a final Classic renewal is not accidentally also treated as a new Billing sale for the same service period.
- Retire Classic only after sign-off. Keep historical reports and integration logic until all remaining adjustments are accounted for.
Why subscription.imported must not trigger a new customer bounty
During Paddle's documented port process, a new Billing subscription record is created and the Classic subscription is silently canceled. The relevant imported event describes data migration, not a new buyer acquisition. Therefore, an affiliate integration should link subscription.imported to the original referral owner instead of paying another new-customer commission.
Paddle documents subscription.import_meta.external_id as a route back to the Classic reference. Store a mapping with the old and new subscription IDs, merchant customer ID and original partner, then use the actual paid Billing transaction for recurring-commission eligibility. A legitimate Classic cancellation as part of migration must not automatically trigger a churn-related clawback.
For a detailed list of object changes, review Paddle's Classic-to-Billing technical mapping. When the affiliate provider advertises generic Paddle support, ask whether it handles Billing API IDs, imported events and recurring transactions specifically.
Risks during parallel operation
- Migration tooling access: dashboard subscription porting is documented as early access, so coordinate with Paddle first.
- Identifier changes: never match subscriptions only by billing email; store import metadata and explicit mapping records.
- Historic reports: Paddle says Classic reporting history remains available in Classic, not newly copied into Billing. Export and preserve partner payout records independently.
- Paused or past-due subscriptions: check collection and retry state. Import does not mean a failed payment became commissionable.
- Affiliate software integration: confirm webhook signatures, event idempotency, partner attribution fields, and support for new Billing subscriptions.
- Customer privacy: restrict exports and avoid embedding personal billing information in public marketing or SEO analytics.
See our Paddle Billing affiliate integration guide for compatible software evaluation and multiple billing-provider attribution for merchants using two payment stacks.
Pilot QA and release criteria
| Test case | Required result |
|---|---|
| One Classic subscription imported | Old and new subscription IDs link to the same merchant account |
| Original partner attribution | One agreed partner remains assigned |
| Imported event | No new customer bounty is automatically issued |
| First paid Billing renewal | One qualifying recurring commission, only if agreement permits |
| Refund and cancellation | Appropriate holds or reversals without erasing valid historical earnings |
| Complete migration batch | All customer and subscription mappings reconcile with export and webhook logs |
Retain rollback procedures for each batch and test webhooks with a limited pilot before changing all customer billing traffic. The product migration and the affiliate payout migration are separate validation workstreams.
Frequently asked questions
Does Paddle automatically migrate affiliate tracking histories?
No general guarantee is documented. Store partner records and commission history in your system and validate the selected affiliate platform's migration support.
Is an imported subscription a new sale?
No. It represents a previously existing contract brought into Billing; do not trigger a second acquisition bounty.
Can every Paddle merchant use the dashboard porting tool now?
The official migration guide describes early-access availability as of the review date. Confirm current account access and supported paths with Paddle.
Does Classic reporting appear inside Billing?
Paddle states historical Classic reporting remains in Classic. Preserve your finance and partner payout exports.
Sources and editorial disclosure
Official documents checked 2 November 2026: Plan a migration, Port subscriptions, and Technical mapping. Ledger controls and testing suggestions are editorial recommendations, not a claim that SaaSAlways performed a live customer migration or that early-access tooling is universally available.