Everflow to Track360 Migration Playbook: Operator Guide 2026

Migrations from Everflow to Track360 typically fail in one of three places: attribution gets broken when postback URLs do not transfer correctly, affiliates lose trust when commission balances do not reconcile, or payment processors get confused when the API endpoints change without coordination. Each failure mode is preventable with a sequenced migration plan that respects the operational dependencies between data export, tracking infrastructure, and payment workflows. This playbook covers the 10 steps that produce a clean cutover, with the week-by-week timing operators need to plan vendor transitions, internal resourcing, and affiliate communications.

Why operators leave Everflow

Everflow is a strong affiliate tracker with a feature-rich SaaS offering. Operators who outgrow Everflow typically do so for one or more of these reasons. The migration motivation determines the priorities during the migration itself; a compliance-driven migration weights regulator alignment higher, while a cost-driven migration weights commercial terms harder.

• Vertical fit: Everflow targets performance-marketing networks and CPA-affiliate use cases. Operators in iGaming, forex, and prop trading often need deeper vertical-specific commission models (NGR-normalized RevShare, lot-based, multi-tier IB networks) that Track360 supports natively.
• Compliance posture: regulated-vertical operators (MGA, UKGC, ESMA, CySEC, BaFin) need built-in compliance workflows tied to the operator's license. Everflow's compliance layer is generic; Track360 ships regulator-specific templates.
• Multi-tier depth: operators with multi-tier IB or sub-affiliate hierarchies push beyond Everflow's tier support. Track360 handles deeper hierarchies (5+ tier levels) without custom configuration.
• Multi-currency payouts: operators paying affiliates in both fiat (USD, EUR, GBP) and crypto (BTC, ETH, USDT, USDC) need integrated payout infrastructure. Everflow handles fiat well; crypto requires third-party integration.
• Brand control: operators want a brand-skinned [affiliate portal](/glossary/affiliate-portal) that matches their main brand. Both platforms support skinning; Track360's depth of customization is typically deeper.
• Cost: Everflow pricing scales by event volume; high-volume operators sometimes find Track360's commercial structure more predictable.
• Reporting depth: operators with internal data teams sometimes need deeper raw-data exports than Everflow's reporting layer offers. Track360 exposes more granular event data via API.

Identify your primary motivation up front. A migration without a clear motivation produces a stack that solves the same problem with a different vendor, which rarely justifies the migration cost. See our [Everflow alternative comparison](/blog/everflow-alternative-igaming-affiliate-platform-comparison-2026) for the full feature comparison.

Pre-migration audit

Before touching Everflow's export tools, document the current state. Operators that skip this step rebuild it mid-migration under deadline, which is when mistakes happen. The audit produces three artifacts: the current-state document, the target-state design, and the gap analysis between them.

• Affiliate inventory: total active affiliates, tier distribution, geographic distribution, vertical mix, top-50 by volume. Export from Everflow as the source of truth.
• Commission configuration: every active commission rule including model (CPA, RevShare, hybrid, multi-tier), payout percentages, tier transitions, geo-specific overrides. Document as a structured spreadsheet.
• Tracking infrastructure: every postback endpoint receiving conversion data, every active affiliate-link template, every redirect domain. Map each to its current Everflow configuration.
• Payment infrastructure: payout processors, wallet integrations, payment-method coverage, payout frequency, minimum-balance thresholds. Document all active payment relationships.
• Integration inventory: every system integrated with Everflow including the casino or forex platform, CRM, business intelligence, KYC vendor, fraud-detection tool. Map the data flow direction (Everflow to system, system to Everflow, or bidirectional).
• Compliance configuration: regulator-specific reporting, KYC document storage, audit-trail retention. Document the retention obligations for your jurisdiction (e.g., MGA requires 7 years; GDPR requires data-deletion within specific windows).
• Open commission balances: outstanding commission owed to each affiliate, plus pending conversions in the attribution window. Reconcile balances to the cent before migration begins.

The audit takes 7-14 days for a mid-market operator. Output: a 20-40 page current-state document that the migration team references throughout the project. Skip this and the migration extends by 30+ days.

Data export from Everflow

Everflow exposes export functionality through its REST API and the platform UI. The API path supports larger datasets and is the recommended approach for operators with more than 100 affiliates. Export targets and their dependencies:

1. Affiliate records: pull via the /affiliates endpoint. Fields: affiliate ID, name, contact details, tier assignment, status (active/paused/terminated), tax forms, KYC documents, sub-affiliate relationships. Export as JSON or CSV.
2. Campaign and offer configuration: pull via /offers and /campaigns endpoints. Each offer's commission rules, geo-targeting, traffic-source restrictions, creative library.
3. Affiliate link inventory: pull via /tracking-links endpoint. Each link's URL pattern, redirect target, SubID parameters, postback URL bindings.
4. Conversion history: pull via /reports/conversions endpoint with the full historical window. Each conversion record includes timestamp, affiliate ID, conversion type, commission amount, payment status. Export in batches if the dataset exceeds 1M records.
5. Postback log: pull via /postbacks endpoint. Each fired postback record including timestamp, target URL, response code, retry status. This is the attribution audit trail.
6. Payment history: pull via /payments endpoint. Each payout record including timestamp, affiliate ID, amount, currency, payment method, processor reference. This becomes the reconciliation baseline.
7. Audit logs: pull via /audit endpoint. Configuration changes, user actions, regulator-relevant events. Retain for compliance windows.

Storage and security: export to encrypted storage (S3 with KMS, equivalent encrypted block storage), restrict access to the migration team, retain for the regulator-required period (7 years for MGA, varying per jurisdiction). The export contains PII (affiliate names, addresses, tax IDs); treat it accordingly.

Attribution preservation: postback re-routing and link migration

Attribution is the hardest part of the migration. Every active affiliate link points to an Everflow redirect domain that translates clicks into Everflow's tracking format. Every conversion postback fires from the operator's casino or trading platform into Everflow's postback endpoint. Switching both at once breaks attribution; switching either alone breaks reporting. The recommended pattern is dual-attribution during a parallel-operation window.

1. Stand up Track360 postback infrastructure. Configure receiver endpoints for each conversion event type (signup, KYC, first deposit, first trade, recurring trade volume). Test with synthetic data before connecting live traffic.
2. Configure dual postbacks at the operator side. Every conversion event posts to both Everflow and Track360 during the parallel window. Both platforms see the same data; commission calculations run in parallel.
3. Generate Track360 affiliate links for every active affiliate. Track360's link template matches the operator's tracking-link domain (or uses a new subdomain). Each link mirrors the SubID parameters from the corresponding Everflow link.
4. Build a redirect layer for legacy links. Set up server-side redirects from old Everflow links to new Track360 links. This catches affiliates who do not update their creatives during the migration window. Plan to maintain the redirect layer for 6-12 months post-cutover.
5. Communicate new links to affiliates. Provide a 30-day window for affiliates to update creatives. Most affiliates will not update until forced; the redirect layer handles the long tail.
6. Reconcile attribution daily during the parallel window. Compare Everflow conversions vs Track360 conversions for the same period. Differences indicate gaps in dual-postback configuration; fix immediately.
7. Set the cutover date. After 14-30 days of clean parallel attribution, disable the Everflow postback. Track360 becomes the system of record. Maintain the legacy-link redirect layer.

The dual-attribution window is the migration's safety net. Operators that skip the parallel window and switch directly typically find attribution gaps in week 2-3 post-cutover, by which time top affiliates are escalating commission disputes. The 30-day parallel window costs roughly USD 5-15k in incremental platform and ops cost; the alternative (disputed commissions, lost affiliates, regulator complaints) costs 10-50x more.

Payment-history reconciliation

Affiliate-payment reconciliation determines whether affiliates trust the migration. Every cent of historical commission must reconcile between Everflow's records and Track360's records, plus the operator's bank statements. The reconciliation process:

1. Export the full payment history from Everflow. Group by affiliate, then by payment cycle. Sum should match the operator's payout-side ledger.
2. Reconcile with operator bank statements. Every payment in the Everflow record should appear in the operator's bank or processor ledger with matching amount, currency, and timestamp.
3. Identify exceptions. Payments that exist in Everflow but not in bank records, or vice versa. Investigate each exception; usually traceable to currency conversion timing or processor fees.
4. Import historical payment records into Track360. Each Everflow payment record becomes a Track360 historical-payment record with the same reference IDs. Affiliates see their historical payment data when they log into Track360.
5. Reconcile open balances. For each affiliate, compute the open commission balance as: total earned commissions minus total paid commissions. This balance carries over to Track360 as the starting balance for that affiliate.
6. Run a reconciliation report. For each affiliate: opening balance from Everflow, earnings in the parallel window, payments in the parallel window, closing balance. Validate that the closing balance in Track360 matches the operator's expectation.
7. Communicate the reconciliation to top affiliates. Top-50 affiliates by volume should receive a personalized statement showing their balance carry-over. This is the trust signal that holds the affiliate relationship during the migration.

Reconciliation typically uncovers historical discrepancies that pre-date the migration. Resolve each one with the affiliate; do not paper over discrepancies during the migration. Affiliates find discrepancies eventually, and trust lost during a migration is hard to rebuild.

Migration timeline: week-by-week

The 12-week reference plan suits mid-market operators (500-2,000 active affiliates). Smaller operators (<200 affiliates) can compress to 8 weeks; larger operators (>5,000 affiliates) typically extend to 16-20 weeks. The compression points are the parallel-operation window and affiliate communication; the discovery, export, and setup workstreams scale more linearly with affiliate count.

Cutover playbook: 10 steps

The cutover week is the highest-risk period. Follow these 10 steps in order; deviations produce predictable failure modes.

1. T-7 days: send final cutover notice to all affiliates. Confirm new Track360 portal credentials sent. Confirm any remaining creative updates needed. (Owner: Affiliate Management)
2. T-3 days: freeze Everflow configuration. No new affiliates onboarded to Everflow; no commission-rule changes; no new affiliate links created. (Owner: Operations)
3. T-1 day: final reconciliation check. Validate that Track360 has captured all conversions from the parallel-operation window. Validate that payment balances reconcile between Everflow and Track360. (Owner: Engineering + Finance)
4. T-0, hour 0: switch primary attribution to Track360. The casino, trading platform, or other operator-side system designates Track360 as the canonical postback target. Everflow postback remains active in shadow mode for 7 more days. (Owner: Engineering)
5. T-0, hour 1: validate first conversions land in Track360 correctly. Run 5-10 test conversions via known affiliates; confirm attribution, commission calculation, and reporting. (Owner: Engineering)
6. T-0 to T+24 hours: monitor live traffic. Watch for postback errors, attribution misses, affiliate login failures. (Owner: Engineering + Affiliate Management on-call)
7. T+1 to T+7 days: maintain Everflow shadow postback. Daily reconciliation: Everflow conversions vs Track360 conversions. Any divergence triggers immediate investigation.
8. T+7 days: disable Everflow postback. Track360 is now the only attribution path. The redirect layer for legacy affiliate links remains active.
9. T+14 days: first post-cutover payment cycle runs through Track360. Validate that affiliate payouts complete correctly. Resolve any disputed payments immediately.
10. T+30 days: decommission Everflow account. Final data export and archival for compliance retention. Account closure once outstanding balances are zeroed. (Owner: Operations + Finance)

Post-migration validation

The migration is not complete at cutover. The first 30-60 days post-cutover are when latent issues surface. Plan validation activities:

• Week 13: first post-cutover payment cycle. Validate that every affiliate receives correct payout. Top-50 affiliates get personal verification; long-tail handled by automation.
• Week 14-15: attribution audit. Sample 10-20% of conversions and trace them end-to-end through Track360. Validate that the attribution path matches the expected affiliate.
• Week 16: commission-model audit. Validate that complex commission models (multi-tier, NGR-normalized RevShare, lot-based) produce correct calculations in Track360.
• Week 18: affiliate feedback survey. Net Promoter Score (NPS) or equivalent from affiliates on the migration experience. Identify any process gaps for future migrations.
• Week 20-24: regulator audit-readiness check. For regulated verticals, validate that Track360's compliance reporting produces the expected outputs for MGA, UKGC, ESMA, or equivalent regulator. Run a simulated audit.
• Month 6: program-health review. Compare KPIs (active affiliate count, conversion rate, commission cost, fraud rate) pre vs post migration. Validate that the migration improved or maintained program health.

Operators that complete all post-migration validation steps report higher confidence in the new platform and earlier ROI realization. Operators that declare victory at cutover often find issues in months 4-6 that require additional remediation cost.

Frequently Asked Questions

External references

• Everflow API Documentation (developers.everflow.io)
• Everflow Platform Overview (everflow.io)
• IAB Affiliate Tracking and Attribution Standards (iab.com/guidelines)
• MGA Licensee Hub Data Retention Requirements (mga.org.mt)
• EDPB Data Portability Guidance under GDPR (edpb.europa.eu)
• Performance Marketing Association Platform Switching Guidance (thepma.org)
• PCI Security Standards Council Card Data Migration (pcisecuritystandards.org)

Everflow to Track360 migrations succeed when the operator treats it as a 60-90 day program rather than a weekend technical project. The data export is the easy part; the hard parts are attribution preservation, commission reconciliation, and affiliate communication. The 10-step cutover playbook above is the operating sequence that operators have used to migrate cleanly while preserving affiliate trust and avoiding regulator complaints. For sister migration playbooks, see our [Cellxpert to Track360](/blog/cellxpert-to-track360-migration-playbook-2026), [Income Access to Track360](/blog/income-access-to-track360-migration-playbook-2026), and [MyAffiliates to Track360](/blog/myaffiliates-to-track360-migration-playbook-2026) guides.