Why plan a migration to Affilentra instead of improvising
A technical migration from third-party platforms carries risks for tracking, payouts and partner links. Affilentra provides a self-hosted affiliate solution with clear roles (software operator, merchant, partner), tracking, commission calculation and payout capabilities in a single platform. To ensure a smooth transition, you need a data-driven approach: data export, field mapping, link preservation, test runs and a secured cutover. This checklist guides merchants and network operators through the process with practical steps.
1. Pre-Migration Audit: Inventory
Before exporting, create a complete inventory of all relevant elements. Document the following:
- Merchant accounts, product or offer IDs and associated terms
- Partners (affiliates) with IDs, contact details, standard commissions
- Tracking link formats, parameters used (e.g. affiliate_id, partner_id, subid, click_id)
- Conversion events, postback URLs, S2S integrations and pixels
- Creative assets, landing pages, vanity or shortlink domains
This audit forms the basis for clean mapping into Affilentra and prevents gaps in tracking and reporting.
2. Data Export: Structure and Formats
Export the following data from the legacy system database or backend into CSV/JSON files:
- Merchants/Offers: Offer ID, name, default commission, payout logic
- Partners: Partner ID, name, email, tracking ID, status (active/paused)
- Campaigns/Creatives: Creative ID, link template, landing URL, media files
- Clicks & Conversions (historical): Click ID, timestamp, partner ID, offer ID, conversion status, order ID
Ensure consistent character encoding (UTF-8) and identical field delimiters to avoid import errors.
3. Data Mapping: Fields and Rules
Define field mappings between the source format and the Affilentra schema. Key points:
- Partner ID → Affilentra partner_id (no duplicate assignments)
- Offer ID → Affilentra merchant_offer_id
- Tracking parameters: Note old parameter names and map them to the new template (e.g. affiliate= → aff_id=)
- Commission rules: Ensure tiered, fixed or CPA rules are represented exactly
- Historical conversions: Import only verified, completed conversions; mark any uncertainties
Create a mapping table (CSV) for reusability and as documentation for future audits.
4. Tracking Link Preservation: How to keep partner links valid
The central goal: existing partner links should continue to convert after the switch without partners needing to change their links. Approach:
- Analysis of the existing link structure: hostnames, path patterns, query parameters
- Redirect strategy: Implement 301 redirects from old click URLs to Affilentra tracking URLs. In self-hosted setups you can map redirects at the web server level (Nginx/Apache) or via a shortlink service.
- Parameter mapping: Ensure that all relevant parameters (Partner ID, SubID, Campaign) are transferred into the new template.
- Vanity domains: If partners use their own domains, you should either redirect them or register CNAME/tracking hosts in Affilentra so that vanity links are preserved.
Important: Use permanent redirects (301) so that existing caches and search engines are not disrupted.
5. Conversion validation: Test before flipping the live switch
Conduct extensive tests to validate click-to-conversion tracking and commission calculation:
- Test clicks: Generate test clicks with different parameters (various partners, SubIDs, campaigns).
- End-to-end orders: Simulate orders and check whether conversion events arrive correctly in Affilentra.
- S2S postbacks: Validate server-to-server postbacks with signed data, if your shop supports S2S.
- Reconciliation: Reconcile imported historical conversions with legacy data; mark discrepancies and investigate their cause.
6. Import into Affilentra: roles, tools and steps
Affilentra clearly separates software operator, merchants and partners — use this separation during the import:
- Software operator: Install/configure the self-hosted instance (PRO or NETWORK Edition) and set up basic settings.
- Merchant import: Create merchant accounts, import offers and commission settings.
- Partner import: Import partner profiles with tracking IDs; inform active partners about upcoming tests in parallel.
- Conversion import: Upload verified conversion datasets only into the historical area, not into the live payout pipeline.
Use the platform's existing CSV import functions or APIs for automated, repeatable import steps.
7. Cutover plan & checklist
Plan a clear cutover window and follow this checklist:
- Schedule a maintenance window (lowest traffic)
- Perform final synchronization of legacy data
- Enable redirects (301) and spot-check them
- Live tracking: verify URLs, trigger test conversions
- Inform partners: communication template with status and support contact
- Set up monitoring for the first 72 hours (logs, error rates, conversion rates)
- Define rollback triggers (e.g. significant deviation in conversion volume over a defined timebox)
8. Post-Cutover: Monitoring and Reconciliation
Immediately after the cutover, the most important activities are:
- Continuous review of click and conversion logs
- Reconciliation with shop/CRM data to detect lost revenue early
- Verify commission calculation: are master data and rules applied correctly?
- Prioritize and document a support queue for partner inquiries
After one week, perform a detailed reconciliation report and close any remaining discrepancies through defined processes.
9. Communication with Partners
Clear, concise communication reduces support effort and uncertainty:
- Advance notice with date and expected changes (if partner links need to be adjusted)
- Technical guidance for partners if their own vanity links must be reconfigured
- FAQ and a dedicated support channel for the first days after the cutover
10. Safeguards: Rollback and Lessons Learned
A tested rollback plan is mandatory. Define:
- Which criteria trigger a rollback (e.g. >X% drop in converted orders during Y hours)
- How redirects and DNS will be reverted quickly
- Who makes the decision and who performs which steps
Document lessons learned after the migration is complete and adjust operational processes to prevent recurrence.
Conclusion
A successful migration to Affilentra requires structured preparation: clean data mapping, preserving tracking links via redirects, thorough testing, and a secured cutover with monitoring. The self-hosted architecture and separation of roles in Affilentra give you control over products, terms, and payout history — without revenue sharing in license models.
Act now: Choose your entry point and plan your migration with clear export, mapping, and testing steps. Choose entry: https://affilentra.de
Next step
Try Affilentra yourself
Unified platform that transparently brings together product provisioning, tracking, conversion validation, commission calculation and payout across clearly separated roles; option for self-hosted installation with a perpetual license and no revenue share; merchants retain control over products, terms and promotional assets; partners receive personal tracking links and a traceable payout history.