White-Label Platform Migration Runbook (Delivery)

White-Label Platform Migration Runbook (Delivery)

1. 01

   Inventory every client asset that depends on the current platform

   List domains, DNS records, email accounts, payment integrations, and custom code snippets. Confirm which clients have active retainers tied to the platform so migration effort is prioritized by revenue.

2. 02

   Map feature parity between the old platform and the white-label replacement

   Compare the specific features each client uses, not just the marketing feature lists. For example, if a client relies on A/B testing in their funnel builder, verify the new platform supports it before committing.

3. 03

   Stage the new platform in a sandbox with a sample client build

   Recreate one representative client site or funnel end-to-end, including custom domain mapping and payment processing. This surfaces integration gaps early, before any client data is touched.

4. 04

   Schedule the migration window per client and communicate downtime

   Pick a low-traffic period for each account and send a notice at least 72 hours in advance. Include what changes, what stays the same, and who to contact if something breaks.

5. 05

   Execute the cutover with a rollback plan in place

   Export all client data from the old platform and verify the backup is restorable. Keep the old platform live for at least one billing cycle so you can revert if the new environment fails.

6. 06

   Verify post-migration functionality against a checklist

   Test forms, checkout flows, email notifications, and any third-party integrations on the live domain. Confirm SSL certificates are valid and that analytics tracking is firing correctly.

7. 07

   Update internal documentation and client-facing credentials

   Record new login URLs, API keys, and support contacts in your agency's knowledge base. Send clients their new access details and a short guide on any interface changes.