September 2026 — Migrating to AI Max: A 6-Step Plan for B2B Teams to Protect Search Campaigns from Performance Shock
September 2026 won’t be “just another optimization month” for PPC teams—it will be a test of operational maturity. Google is rolling out forced migrations to AI Max for campaigns built on legacy campaign-level Broad Match and Automatically Created Assets, and companies that leave this process on autopilot risk sudden shifts in query matching, creative, and landing page traffic. The biggest mistake I currently see among B2B advertisers is treating this as a routine product update rather than a transformation of the campaign control model.
What exactly is changing—and when you need to act
In this case, timeline clarity—and specific dates—matter most:
August 3, 2026: Google blocked creation of new legacy structures for campaign-level Broad Match and ACA (in UI, Editor, and API).
September 1–30, 2026: gradual auto-migration of campaigns from campaign-level Broad Match and/or ACA to AI Max.
September 2026: launch of in-account notifications for DSA.
January 15, 2027: reminders for accounts with legacy DSA.
February 1–28, 2027: start of DSA auto-migration to AI Max and end of the ability to create new DSA ad groups.
This means one simple thing: if your organization works on a quarterly cadence and decisions are made “at month-end,” your migration control window is closing now, not in September.
Why AI Max is more than just “more automation”
Google positions AI Max as an optimization layer, not a new campaign type. In practice, it combines three levers:
search term matching,
text customization (formerly ACA),
final URL expansion.
According to Google’s non-retail data, the full feature set delivers an average 7% increase in conversions or conversion value at similar CPA/ROAS versus search term matching alone.
But from a B2B lead generation perspective, something matters more than the uplift itself: the team’s center of gravity shifts. Less manual keyword “patchwork,” more guardrail design, signal feed quality, and control over experiment entry/exit.
Where performance shock risk actually shows up
The biggest risk is not that AI Max “works poorly,” but that it works differently than the team assumed.
Critical traps to close before migration
With final URL expansion or URL inclusions enabled, RSA pinned assets may not be respected.
If someone turns off AI Max entirely during testing, active mechanisms may disappear with it—for example, brand exclusions.
In DSA migration, some legacy targets become read-only—you can remove them, but you can no longer edit them freely as before.
Poorly configured tracking templates (e.g., incorrect use of {lpurl}) can generate 404 errors after dynamic landing page swaps.
Budget-constrained campaigns won’t unlock AI Max’s full potential—the platform explicitly flags this limit.
If these points don’t make it into your operational checklist, the issue won’t surface “during implementation,” but only in results 2–4 weeks later.
Migration war room — action plan for the coming weeks
The winners here are teams that treat this as a cross-functional project: PPC + analytics + dev/API + business stakeholder.
Phase 1: Inventory and risk segmentation
Build a list of campaigns using legacy campaign-level Broad Match, ACA, and DSA.
Tag campaigns that are pipeline-critical (high SQL value, high seasonality, low margin for error).
For API-first accounts, prepare an audit of scripts and integrations tied to deprecated entities.
Phase 2: Guardrails before migration
Document current brand inclusion/exclusion settings at campaign and ad group level.
Define a Final URL Expansion policy by campaign:
where it should be ON,
where it should be OFF,
which URLs must be excluded.
Check where RSA pinning is business-critical.
Test tracking templates for dynamic landing pages.
Phase 3: Pre-migration experiments
Launch tests before September auto-migration instead of waiting for default settings.
Build experiments with clearly defined KPI gates:
MQL/SQL cost,
share of brand vs non-brand queries,
lead quality in CRM.
Analyze reports with new AI Max fields (source, query-headline-URL combinations) to quickly filter out irrelevant expansions.
Phase 4: Post-migration monitoring
Treat the first 14 days after migration as a period of heightened supervision.
Set a review cadence every 48–72h for Tier 1 campaigns.
Prepare rollback scenarios for specific settings (not a blanket AI Max shutdown) so you don’t accidentally disable critical controls.
What this means strategically for B2B teams
This migration is a directional signal, not a one-off episode. Google is consistently moving Search from a “manual build” model to an “AI orchestration” model. In this setup, advantage no longer comes from having the most manual tricks—it comes from process quality:
stronger structure and signal design,
faster anomaly detection,
stricter experiment discipline.
Companies that build their own war room and migration standard now will gain something more valuable than a short-term uplift—a repeatable adaptation system for future forced changes across the ads ecosystem.
