The Advertising Studio Migration Checklist: A Practical Playbook for SFMC Teams

Salesforce stops selling and renewing Advertising Studio on August 15, 2026. Existing contracts will run to their expiry dates, but the clock is already running — and for teams that have never had to think about their audience activation layer, the timeline can feel uncomfortably short.

I've worked through this with enough teams to know where it stalls — not on the technical work, but on inventory scope ("we thought we had 20 audiences, we actually have 140"), procurement timelines, and security reviews nobody scoped. Start now and you have enough time. Wait until Q4 and you might not.

This post walks you through five phases. I've kept it vendor-neutral: the right destination depends on your contract situation, existing stack, and Data Cloud investment. The process below works regardless of where you land.

Before You Start: Understand What You're Actually Migrating

Advertising Studio has a data model worth understanding before you do anything else, because it shapes how much work your inventory phase creates.

In Ad Studio, an audience is a destination-coupled object. A Customer Match audience is a Google-shaped object — it exists in the context of a Google Ads account. If you want to sync the same underlying contact list to Meta, you create a second, separate audience object. The same contacts might live in three or four Ad Studio audiences across different ad platforms, each requiring its own migration record.

This matters because teams that estimate their migration scope by counting contact lists will undercount. You need to count audience objects by destination, not by unique contact sets. The inventory table template below is built around this.

There is also an API timing issue specific to Google. Google deprecated the Customer Match endpoint in the Google Ads API in favor of the Data Manager API — the first hard cutover was April 1, 2026, and dormant Customer Match connections in Ad Studio now throw CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE. If you have any Google audiences in Ad Studio that are not actively syncing, test them now before assuming they will work through your contract expiry. I wrote about this in detail here: SFMC Advertising Studio Google Customer Match migration.

Phase 1: Inventory

The goal is a complete, accurate picture of every active audience object in Ad Studio, including the metadata your replacement platform will need. For each audience, capture: name, destination platform, ad account ID, source Data Extension or list, refresh schedule (one-time push, scheduled, or Journey Builder-triggered), Journey Builder journeys that add or remove contacts, BU ownership and ad account admin rights, last sync date, record count, and whether an active campaign is drawing from it right now.

Who to involve: This is not a solo Marketing Cloud admin task. Pull in whoever manages the ad accounts on each platform — you will need them for the OAuth re-connection step in Phase 5. Pull in Journey Builder owners, because a journey that adds contacts to an Ad Studio audience needs its activity updated, not just the sync.

Inventory table template (copy into a spreadsheet or Notion):

Fill one row per audience object, not per contact list. A contact list that feeds Google and Meta audiences gets two rows.

Phase 2: Triage

A complete inventory typically surfaces a lot of waste. In my experience, 30 to 50 percent of Ad Studio audiences in established orgs are either paused, stale, or duplicated. Migrating all of them is not worth the effort.

Classify each audience into one of three buckets: active and business-critical (feeding a live campaign, syncing recently — these migrate); dormant but potentially needed (campaign paused, team expects to reactivate — consider whether you can recreate the audience from the source Data Extension on demand rather than maintaining a live sync); and dead (no active campaign, no recent sync, ad account closed or owner gone — archive the record and don't migrate it).

For audiences you do migrate, sequence by use case. Suppression lists go first: a suppression that fails to sync means you spend money targeting people you should not be reaching. Retargeting audiences follow. Prospecting and lookalike seed lists are important but usually more tolerant of a brief gap during cutover.

Phase 3: Choose Your Target Platform

This is where the vendor decision lives, and I am not going to make it for you — but I will give you the honest framing.

Salesforce's recommended path is Data Cloud + Data Cloud Ad Audiences. If you are already moving toward Data Cloud, or are on a new Marketing Cloud edition (Growth, Advanced) where Data Cloud is the architectural foundation, this is probably the right long-term answer. The cost structure is different — a separate platform license, consumption credits, a 3-to-5-year term, and an integration project to get your data into Data Cloud first. Not trivial, and not a flip. But if you need unified customer profiles and AI capabilities, the ad activation piece is not a reason to avoid it.

If your only need is audience activation, there are purpose-built alternatives that install directly into your existing Marketing Cloud org without a Data Cloud license. I cover the full landscape in the alternatives post.

For the purposes of this checklist, what matters at this phase is:

• Have you received a quote and reviewed terms from your chosen replacement?
• Has your security team reviewed the data flow (particularly: where does hashing happen, what data leaves your environment, what does the vendor store)?
• Is procurement moving? Security and procurement are almost always the long pole — not the technical migration itself.

If you are evaluating Cezium Ads, it is an AppExchange-listed package (which means it has passed Salesforce's AppExchange security review) that installs directly in your SFMC org with a single package install. A typical go-live from install to first live audience sync is about a week, most of which is the security walkthrough and OAuth connections to ad accounts. That week-to-go-live is a meaningful advantage when you are running against a contract deadline.

Phase 4: Parallel Run

Do not cut over cold. Run your new audience syncs in parallel with Ad Studio for at least two to four weeks before you decommission anything.

What to verify during the parallel run:

Match rates. Your new platform will report a match rate from the ad network — the percentage of records the platform resolved to a known user. Before you panic at a number that looks low: match rate is determined by the ad platform's identity graph and the keys you send, not by the sync vendor. Email-only audiences on Meta typically match at 40 to 55 percent; additional keys (phone, name, zip) push it higher. If your Ad Studio audiences were email-only, expect the same rate on your new platform — and the same opportunity to improve it by enriching your source Data Extension.

Opt-out propagation. This is the one that creates compliance exposure if it breaks. Test a contact that has opted out or been deleted: does the removal propagate to the ad platform on the next sync cycle? Verify this end to end on every destination, not just one.

Journey Builder activities. If any Phase 1 rows flagged "Journey Activities: Y," update those activities to point to the new platform during the parallel run. Run both the old and new activities for at least one full journey cycle before removing the Ad Studio one.

Account connectivity. Your new platform needs OAuth connections to the same ad accounts Ad Studio was using. A user with admin rights on the ad account grants permission — the same pattern as when you first connected Facebook to Ad Studio. Coordinate with whoever owns those ad accounts; it is often a different person than the Marketing Cloud admin.

Phase 5: Cutover and Decommission

Once the parallel run has validated match rates, opt-out propagation, and journey behavior, you are ready to cut over.

Cutover steps:

1. Pause or deactivate all Ad Studio syncs (do not delete — you want the records for audit purposes).
2. Confirm that replacement syncs are active and have completed at least one successful run post-cutover.
3. Revoke OAuth grants in Ad Studio for each ad platform. This is a clean hygiene step — it removes the authorization tokens so that Ad Studio can no longer make API calls to those accounts even if someone accidentally reactivates a sync.
4. Update any consent or data transfer documentation that references Advertising Studio by name. This includes records of purpose (the legal basis for sending data to ad platforms) and any DPA annexes with your ad platform vendors.
5. Archive audit evidence: export logs of the final Ad Studio sync dates, record counts, and any opt-out propagation records. Store these for however long your data retention policy requires.

Timeline reality check:

The technical migration — standing up syncs, running parallel, cutting over — is typically measured in days to weeks per destination. A team with 15 audiences across three platforms can realistically complete the technical work in three to four weeks once the replacement platform is live.

Procurement and security review are the parts that take longer. If your organization requires a security assessment, a DPA review, and procurement approval for a new SaaS vendor, budget eight to twelve weeks from first conversation to signed contract. Start that process now, in parallel with your inventory.

Putting It Together: Realistic Timeline

The phases overlap. Start vendor selection while you are finishing inventory. Procurement is almost always the long pole — treat it as the first parallel track, not a step that follows everything else.

If your Ad Studio contract expires before August 15, 2026 and you are running month-to-month, the urgency is higher. Get your inventory done this week.

The technical work is manageable. What I see trip teams up is underestimating inventory scope (because of Ad Studio's destination-coupled model), underestimating procurement lead times, and skipping opt-out propagation testing before cutover. Build those into your plan and the rest follows.

For a full breakdown of replacement options, see Advertising Studio alternatives. For the end-of-life timeline and what Salesforce has communicated officially, see Advertising Studio end of life August 2026.