A new offer can afford a rough first week. An existing offer cannot. When you move to a new CRM, a new development partner or new infrastructure, the business already depends on subscriptions that must rebill, affiliates who expect postbacks, and funnels that are converting right now.
Operators who migrate care about three things above everything else: continuity, no downtime and no data loss. A good migration is built around protecting what is already working, and only then improving it.
The goal of a migration is not to rebuild. It is to move without anyone outside the team noticing, then improve.
Step one: inventory everything
You cannot protect what you have not written down. Before any change, build a complete inventory of the current setup. In our experience, this step alone uncovers at least one integration or script that nobody remembered existed.
Systems & ownership
- Current CRM and account access
- Who manages campaigns today: owner, campaign manager or external vendor
- Whether the new team takes over campaign management or collaborates with the existing one
- Hosting, domains and DNS access
Integrations
- Payment gateways and merchant accounts
- Email (ESP) and SMS providers
- Fulfillment and 3PL connections
- Fraud and chargeback alert tools
Custom code
- Custom scripts, APIs and webhooks
- Any non-standard tools already in use, documented honestly
- Cron jobs and scheduled tasks
Assets & backups
- Source code and offer codes for every funnel
- Database access or exports from the previous vendor
- Recent, verified backups
If you are leaving a vendor, secure access to hosting, source code, databases and every third-party account before the relationship ends. Recovering credentials after the fact is slow at best and impossible at worst.
Tracking: keep or change?
Tracking is the part of a migration most likely to break silently. Start by documenting which platforms are in use today, which postback URLs are configured in the CRM, and which events each one fires.
Then make an explicit decision:
- Keep the current tracking setup. Lowest risk. Postback URLs are recreated in the new CRM with the same parameters, and affiliates see no change.
- Move to a new tracker or structure. Sometimes worth it, but do it as a separate project. Changing the CRM and the tracker at the same time makes it very hard to tell which change caused a discrepancy.
Change one major system at a time. If conversions drop after a migration, you want exactly one suspect.
Migrating data
Data migration is where "no data loss" is won or lost. Typical data sets include:
| Data | What to watch |
|---|---|
| Customers | Deduplicate, preserve IDs where possible, and keep consent and opt-out status intact. |
| Transactions | Needed for refunds, chargeback evidence and reporting continuity. Keep original order IDs as a reference field. |
| Active subscriptions | Rebill dates, billing cycle, price, product and status must map exactly, or customers get billed early, late or twice. |
| Payment tokens | Card data is tokenized at the gateway. Moving it usually requires a gateway-level token migration or vault transfer, arranged between processors, not a CSV export. |
| Affiliate attribution | Stored click IDs and affiliate IDs on active subscriptions, so rebill postbacks keep crediting the right partner. |
Always run a trial import into a staging environment first, then reconcile counts and totals against the source system before touching production.
The cutover plan
A cutover should be a rehearsed sequence, not an event. This is the order that has worked reliably for us:
-
Freeze changes
Agree on a short window in which no new campaigns, price changes or funnel edits are made on the old system.
-
Run in parallel
Build and configure the new setup while the old one keeps serving traffic. Compare configurations side by side: products, offers, upsell paths, fulfillment rules, postbacks.
-
Place live test orders
Run real test transactions through every path, including each upsell and downsell, and confirm orders, emails, fulfillment and postbacks all behave as expected.
-
Lower DNS TTLs in advance
Reduce the TTL on affected records a day or two before cutover, so the switch propagates in minutes rather than hours, and so does a rollback.
-
Switch traffic and postbacks
Point domains and checkout to the new system and activate postbacks there, disabling them on the old one so nothing fires twice.
-
Monitor closely
For the first hours and days, compare orders, approvals, rebills and tracker conversions against the pre-migration baseline.
-
Keep a rollback ready
Keep the old setup intact and reachable until the new one has proven itself through at least one full rebill cycle.
Common pitfalls
- Rebills firing on both systems, or on neither, because subscription ownership was not switched cleanly.
- Postbacks pointing at the old CRM's event names or missing parameters, so affiliates suddenly see zero conversions.
- Missing offer codes or page variants that were never in version control.
- Email and SMS flows left on the old platform, sending duplicate or contradictory messages.
- Compliance pages not carried over, or carried over with outdated company details.
- Hard-coded URLs in scripts and emails that still reference old domains.
The most valuable migration document is a simple before-and-after table of every product, campaign, postback and integration, with a checkbox for "verified on the new system". It turns a nerve-racking cutover into a routine one.
Key takeaways
- Existing offers need continuity first: no downtime, no data loss, no broken attribution.
- Inventory every system, integration, script and credential before changing anything.
- Change one major system at a time, especially tracking.
- Subscriptions and payment tokens need careful, gateway-aware migration.
- Rehearse the cutover, monitor closely, and keep a rollback path open.
