Moving campaigns to a new ad account without rebuilding everything

The real switching cost

The obvious cost of changing accounts is losing signal history. The larger and less discussed cost is labour: recreating campaigns, ad groups, audiences, budgets, bidding rules and hundreds of creatives through an interface.

For an established advertiser that is days of work with a high error rate, and errors made during migration surface later as unexplained performance differences.

What migration looks like programmatically

The API and CLI can reconstruct campaign structures rather than requiring manual rebuilding. Existing Meta campaigns can be moved across, hundreds of creatives uploaded in bulk, and winning structures recreated rather than reinvented.

One demonstrated pattern went further: point the system at a competitor's Ad Library, ask it to recreate the strongest concepts, and launch the result. The same mechanism that rebuilds your own campaigns builds new ones from research.

What not to migrate

Do not bring across campaigns that were not working. Migration is a rare, cheap opportunity to delete things, and rebuilding a structure faithfully includes rebuilding its mistakes.

Do not assume budgets transfer meaningfully. A new account has no optimisation history, so budgets set for a seasoned account can behave differently on day one.

Fix reporting currency and account timezone before migrating, not after. Changing conventions later makes before-and-after comparisons unreliable at exactly the moment you need them.

Run both for a while

Keep the existing account running while the new one accumulates data. Parallel operation is the only way to distinguish an account difference from a creative, seasonal or market difference.

It also means a migration that goes badly is recoverable, which a hard cutover is not.