Introduction
Switching from a SaaS affiliate platform to a self-hosted solution like Affilentra (PRO/NETWORK) provides control and flexibility: merchants retain sovereignty over products and terms, partners receive transparent tracking links and payout histories, and there is no revenue share. This article offers a practical, role-based migration checklist for merchants and network operators who want to safely take over product data, tracking links, cookie settings, webhooks, payout batches and partner accounts.
Overview: Phases of the Migration
- Phase 0 – Preparation & Inventory: Identify data sources, define stakeholders and downtime windows.
- Phase 1 – Export & Mapping: Export data from the SaaS platform and map it to the Affilentra schema.
- Phase 2 – Staging & Tests: Import into a staging system, perform end-to-end tests (tracking, conversions, webhooks).
- Phase 3 – Production & Cutover: Migrate production data, switch DNS/endpoints, minimize downtime.
- Phase 4 – Post-Migration & Monitoring: Reconciliations, live monitoring, provide partner support and rollback options.
Phase 0 – Preparation & Inventory
Create a complete inventory of all relevant objects in your SaaS platform:
- Products/SKUs including prices, variants and availability
- Partner accounts (affiliate IDs, tracking preferences, payout accounts)
- Tracking links and link formats (parameters, short URLs)
- Cookie settings: lifetime, domain rules, first-/last-click attribution
- Webhook configurations and external integrations (ERP, billing, CRM)
- Open payout batches and historical payouts
Also define responsibilities: Who exports, who transforms, who tests, who decides on go-live.
Phase 1 – Export & Mapping
Export structured data (CSV/JSON/SQL). Create a mapping document that assigns source fields to Affilentra fields. Example mapping fields:
- Product: source_product_id → product_id
- SKU: sku → sku
- Title/Description: title, description → name, description
- Price: price → price_net / price_gross (depending on need)
- Commission model: commission_type (fixed/percent) → commission_model + rate
- Partner: source_aff_id → affiliate_id
- Tracking link: deeplink_template → tracking_template
- Cookie: cookie_lifetime, cookie_domain → cookie_duration, cookie_scope
Check for special cases: multiple commission rates per product, country-specific prices, coupon or subID handling. Capture Affilentra field validations (e.g. required fields, allowed characters).
Phase 2 – Staging & Tests
Set up a staging environment on your self-hosted Affilentra installation. Goals: validate the data structure, test all integrations, and run end-to-end scenarios without affecting live partners.
Data Import & Validation
- First import a representative subset (10–20%), including products, 50–100 partner accounts, and some payout batches.
- Validate data integrity: look for missing required fields, incorrectly formatted prices, or invalid IDs.
Tracking and Conversion Tests
- Create test tracking links in Affilentra, tagged with test SubIDs.
- Execute test orders (staging shop or test transactions) and verify that conversions are correctly tracked and validated.
- Simulate cookie behavior: expiration, cross-domain scenarios, and first-/last-click attribution.
Webhook and Integration Tests
- Set up webhook endpoints and use signed payloads or secrets for authentication.
- Send test payloads and check reception, parsing, and downstream processing (e.g., ERP/Billing).
- For external dependencies: deploy a temporary proxy logger to inspect requests and responses.
Phase 3 – Production & Cutover
Plan a tight cutover window with minimal user load. Typical sequence:
- Final data synchronization from SaaS (delta export since the last snapshot).
- Data imports into Affilentra production.
- Final check of key KPIs: outstanding payout amount, number of active partners, live tracking.
- Switch DNS/endpoints for tracking and webhook URLs. Alternatively: set shorter TTLs beforehand.
Minimize downtime: use parallel processing (SaaS continues running until cutover), lower TTLs for the relevant domains/VHosts in advance, and schedule cutover for times with low conversion rates.
Payout Batches and Partner Accounts
Process for payouts:
- Export open payout batches with payment details and status.
- Map payout accounts (e.g., bank/PayPal IDs) to Affilentra partner profiles.
- Import payout batches as “imported batches” and perform a reconciliation between the SaaS export and the Affilentra import.
- Verify payment history: partners should be able to view historical payouts seamlessly after migration.
Accounts and access:
- Create or import partner accounts including login hash/communication email.
- Communicate access information and tracking link changes to partners promptly with a clear support path.
Rollback Strategy
Prepare a clear rollback plan:
- Snapshot/Backup: Take full database and filesystem snapshots before starting production imports.
- SaaS parallel operation: Keep the SaaS platform active as a backup for an agreed window (e.g. 48–72 hours).
- Rollback steps: (1) Reset DNS/endpoints, (2) disable Affilentra changes, (3) verify follow-up synchronization.
- Communication: Immediately inform partners and internal stakeholders about the rollback and expect limited downtime.
Acceptance, Monitoring and Follow-up Work
After a successful cutover:
- Conduct an official acceptance with a checklist (conversion tracking, webhooks, payout reconciliation, partner access).
- Set up monitoring: error logs, failed webhooks, tracking anomalies and latency of commission calculation.
- Schedule a support window for partner questions and corrective data adjustments.
Practical Examples and Typical Pitfalls
Common issues and prevention:
- Incomplete mapping tables: Pre-run sample imports on staging to avoid surprises.
- Tracking parameters lost during redirects: Check redirect logic and preserve SubIDs.
- Cookie domain conflicts with subdomains: Intentionally set cookie_scope and test cross-domain cases.
- Webhook auth errors: Sign payloads and test with replay scenarios.
Conclusion and Recommendations
A structured migration to self-hosted Affilentra reduces operational risks and strengthens control over products, commissions and payouts. Work in clearly defined phases, use staging environments, perform comprehensive end-to-end tests and plan a reversible cutover. Affilentra offers the ability to transparently consolidate tracking, conversion validation, commission calculation and payout across separate roles — ideal for merchants who want to remain independent and scalable.
Next step: Choose your entry point and review appropriate editions (PRO / NETWORK) for your requirements: Choose entry
Next step
Try Affilentra Yourself
A 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 without revenue sharing; merchants retain control over products, terms and creatives; partners receive personal tracking links and a transparent payout history.