What is \u201cmigrating from Affise to Scaleo\u201d?<\/h2>\n\n\n\n
Migrating from Affise to Scaleo<\/a><\/strong> is the structured process of moving all core entities \u2013 advertisers, affiliates, offers, tracking links, postbacks, and (optionally) historical stats \u2013 from your legacy Affise instance into Scaleo<\/strong>, while preserving data integrity, partner relationships, and live traffic flow, using a staged, zero-downtime cutover strategy.<\/p>\n\n\n\n The goal is simple: switch brains without stopping the heartbeat.<\/p>\n\n\n\n Before you touch an export button, you need a clear dependency map. If you import in the wrong order, Scaleo will simply reject part of your data, and you\u2019ll be stuck debugging half-created offers.<\/p>\n\n\n\n The strict order that works in practice looks like this:<\/p>\n\n\n\n Why this order matters<\/p>\n\n\n\n In our experience analyzing millions of clicks across large migrations, the single biggest mistake is trying to \u201clift and shift everything\u201d in one shot. You don\u2019t need every dead offer and every dormant affiliate. You need a clean, operationally useful mirror of your current revenue engine.<\/p>\n\n\n\n So at this stage:<\/p>\n\n\n\n You have two practical avenues out of Affise: API (JSON) and GUI CSV exports. For casino programs with any sort of scale, I strongly prefer an API-first approach, using CSV only where it\u2019s operationally simpler (for example, a quick affiliate list sanity check).<\/p>\n\n\n\n You\u2019ll use your Affise Admin API key and your tenant domain. The patterns look like this:<\/p>\n\n\n\n From a migration standpoint, you don\u2019t want everything. You want the fields that map cleanly to Scaleo and help reconstruct relationships.<\/p>\n\n\n\n For advertisers, keep at minimum:<\/p>\n\n\n\n For affiliates, keep:<\/p>\n\n\n\n Password note: you can\u2019t and shouldn\u2019t migrate passwords. More on that later.<\/p>\n\n\n\n For offers, keep:<\/p>\n\n\n\n This is where things get interesting. Casino flows typically have multiple payout models per GEO, plus different goals (FTD, qualified deposit, NGR<\/a> share, hybrid deals). Affise stores these in one way; Scaleo expects a cleaner \u201cGoals\u201d structure. We\u2019ll map that in Step 3.<\/p>\n\n\n\n If your program is mid-size or you simply prefer a visual sanity check:<\/p>\n\n\n\n Practical tip some have learned the hard way: keep a frozen copy<\/strong> of the raw exports before you start manipulating anything. That way, if your transformation scripts go sideways, you always have a clean baseline.<\/p>\n\n\n\n Scaleo is flexible, but it\u2019s not magic; it expects data in a specific format whether you use CSV imports or the API. This step is where you go from \u201craw dumps\u201d to \u201cScaleo-ready\u201d entities.<\/p>\n\n\n\n In Scaleo:<\/p>\n\n\n\n At a minimum, map:<\/p>\n\n\n\n Top-tier operators typically use this phase to clean up naming conventions. If you\u2019ve had years of \u201cAdvertiser 01 \/ Casino Test \/ John\u2019s Deals\u201d, now is the moment to standardize.<\/p>\n\n\n\n Affiliates are trickier because you\u2019re dealing with user accounts and security.<\/p>\n\n\n\n In Scaleo:<\/p>\n\n\n\n Key steps:<\/p>\n\n\n\n Two patterns that work well:<\/p>\n\n\n\n I tend to prefer option 2 for serious casino programs. It feels more professional and avoids the security smell of shared temporary passwords.<\/p>\n\n\n\n If you get postbacks wrong, you\u2019ll have conversions firing into a void.<\/p>\n\n\n\n From Affise, you\u2019ll typically export partner-level, offer-level, or global postbacks in a structure that contains macros like:<\/p>\n\n\n\n In Scaleo, the equivalent macros look like:<\/p>\n\n\n\n When you recreate postbacks in Scaleo (either through the UI or via API), you essentially:<\/p>\n\n\n\n Here\u2019s the bottom line: invest time here. When we audit rocky migrations, 80% of the pain traces back to loose macro mapping and inconsistent postback<\/a> reconstruction.<\/p>\n\n\n\n Offers are where casino migrations either feel elegant or descend into spreadsheet hell. Affise and Scaleo both support complex payouts, but they model them differently.<\/p>\n\n\n\n Scaleo uses a clean Offer + Goals<\/strong> structure:<\/p>\n\n\n\n![\"zero](\"https:\/\/www.scaleo.io\/blog\/wp-content\/uploads\/2025\/12\/Migration-Roadmap-scaleo-zero-downtime.webp\" "\\"-\\"")
<\/figure>\n\n\n\n
\n\n\n\nStep 1 \u2013 Design the migration architecture<\/h2>\n\n\n\n
\n
\n
\n
\n\n\n\nStep 2 \u2013 Export data from Affise correctly<\/h2>\n\n\n\n
2.1 Export via Affise API<\/h3>\n\n\n\n
\n
GET https:\/\/api.YOUR_DOMAIN.affise.com\/3.0\/admin\/advertisers\n<\/code><\/pre>\n\n\n\n\n
GET https:\/\/api.YOUR_DOMAIN.affise.com\/3.0\/admin\/partners\n<\/code><\/pre>\n\n\n\n\n
GET \"https:\/\/api.YOUR_DOMAIN.affise.com\/3.0\/offers?status[]=active\"\n<\/code><\/pre>\n\n\n\n\n
id<\/code> \u2013 you\u2019ll use this as a reference during transformation.<\/li>\n\n\n\ntitle<\/code> \u2013 maps to Scaleo company\/advertiser name.<\/li>\n\n\n\nmanager_id<\/code> \u2013 so you can map the right account manager, if you structure your team that way.<\/li>\n\n\n\n\n
id<\/code> \u2013 becomes your external reference when transforming.<\/li>\n\n\n\nemail<\/code><\/li>\n\n\n\nlogin<\/code> or main contact name<\/li>\n\n\n\nstatus<\/code> \u2013 so you don\u2019t accidentally re-activate banned partners.<\/li>\n\n\n\nmanager_id<\/code> \u2013 again, for team ownership mappings.<\/li>\n<\/ul>\n\n\n\n\n
id<\/code> \u2013 the original offer ID.<\/li>\n\n\n\ntitle<\/code> \u2013 offer name.<\/li>\n\n\n\npreview_url<\/code> \u2013 what affiliates see.<\/li>\n\n\n\ntracking_url<\/code> \u2013 the advertiser landing URL (not the Affise tracking link \u2013 Scaleo will generate its own).<\/li>\n\n\n\npayments<\/code> \/ payouts<\/code> \u2013 including model and GEO-specific rules.<\/li>\n\n\n\ncaps<\/code> \u2013 daily\/weekly\/monthly; timezones; event types.<\/li>\n\n\n\ntargeting<\/code> \u2013 GEOs, devices, OS, etc.<\/li>\n<\/ul>\n\n\n\n2.2 Export via CSV (GUI)<\/h3>\n\n\n\n
\n
Export<\/code> button.<\/li>\n\n\n\n
\n\n\n\nStep 3 \u2013 Transform data for Scaleo<\/h2>\n\n\n\n
3.1 Import advertisers first<\/h3>\n\n\n\n
\n
Advertisers<\/code> \u2192 Add Advertiser<\/code> (for manual tests)<\/li>\n\n\n\nPOST \/network\/advertisers<\/code><\/li>\n<\/ul>\n\n\n\n\n
title<\/code> \u2192 Scaleo Company Name<\/code><\/li>\n\n\n\nid<\/code> \u2192 store as a custom field or external reference if you want cross-system traceability during the overlap period.<\/li>\n\n\n\nmanager_id<\/code> \u2192 Scaleo Manager<\/code> (after you create your internal manager users in Scaleo).<\/li>\n<\/ul>\n\n\n\n3.2 Import affiliates with a re-onboarding strategy<\/h3>\n\n\n\n
\n
Affiliates<\/code> \u2192 Add Affiliate<\/code><\/li>\n\n\n\nPOST \/network\/affiliates<\/code><\/li>\n<\/ul>\n\n\n\n\n
email<\/code>, login<\/code>\/name, and status.<\/li>\n\n\n\n\n
\n
\n
Postback migration \u2013 the critical link<\/h4>\n\n\n\n
\n
{clickid}<\/code><\/li>\n\n\n\n{sum}<\/code><\/li>\n\n\n\n{goal}<\/code><\/li>\n\n\n\n{action_id}<\/code><\/li>\n<\/ul>\n\n\n\nVariable<\/th> Affise Macro<\/th> Scaleo Macro<\/th><\/tr><\/thead> Click ID<\/td> {clickid}<\/code><\/td>{click_id}<\/code><\/td><\/tr>Payout \/ Amount<\/td> {sum}<\/code><\/td>{payout}<\/code>\/{amount}<\/code><\/td><\/tr>Transaction ID<\/td> {action_id}<\/code><\/td>{transaction_id}<\/code><\/td><\/tr>Source ID<\/td> {pid}<\/code><\/td>{source_id}<\/code><\/td><\/tr>Offer ID<\/td> {offer_id}<\/code><\/td>{offer_id}<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n\n
{goal_value}<\/code> for multi-goal setups).<\/li>\n<\/ul>\n\n\n\n
\n\n\n\nStep 4 \u2013 Import offers and rebuild goals<\/h2>\n\n\n\n
![\"-\"](\"https:\/\/www.scaleo.io\/blog\/wp-content\/uploads\/2025\/02\/affiliate-marketing-scaleo-metrics.webp\" "\\"-\\"")
<\/figure>\n\n\n\n