Google’s latest AI Max timeline is easy to read as another product update. That would be too shallow. Search Engine Land reported on August 14 that Google will start automatically migrating some legacy Search campaign features in September, and Google’s developer post gives the operational detail: Campaign-level Broad Match and standalone Automatically Created Assets move first, while Dynamic Search Ads are scheduled for a later February 2027 phase.
For PPC teams, the business question is not whether the label changes. The question is whether account governance, scripts, reporting and client expectations are ready for a different control surface. A September migration can distort performance conversations if teams do not know which campaigns changed, what settings carried over and which legacy objects can no longer be created or edited through newer API versions.
What is moving to AI Max
The first phase runs September 1-30, 2026. Google says Search campaigns using Campaign-level Broad Match or standalone Automatically Created Assets will be upgraded in place to equivalent AI Max settings. Existing brand inclusions and exclusions are described as being preserved. Legacy creation blocks were already put in place on August 3 across the interface, Ads Editor and API.
Dynamic Search Ads are on a different timetable. They are not part of the September phase. Google plans warnings in September and January, with automatic upgrades beginning in February 2027. That split matters because many accounts still use DSA logic for coverage, feed gaps or long-tail discovery. Treating everything as one September event will create bad diagnostics.
Why this changes control
The practical change is that older Search structures are being absorbed into AI Max settings. That means the audit has to cover more than bids and budgets. Teams need to know whether text customization, final URL expansion, search-term matching, brand controls and old asset workflows are documented clearly enough for the next optimization cycle.
The API angle is equally important. Future Google Ads API versions released after September 1 remove support for legacy entities used to create or manage the old Broad Match and ACA setups. Older versions keep temporary support until their normal sunset period. If an agency or in-house team runs scripts, client dashboards, bulk builders or QA tools, this is a dependency audit, not a note for the PPC specialist alone.
The audit checklist
- List every Search campaign using Campaign-level Broad Match, standalone Automatically Created Assets or active DSA logic.
- Separate September migration items from the February 2027 DSA phase.
- Record current AI Max-related settings before migration: text customization, final URL expansion, search-term matching and brand lists.
- Check scripts, API clients, labels, bulk upload templates and reporting connectors for legacy entity references.
- Prepare account annotations for September so pacing, CPA and ROAS changes are not read as normal optimization noise.
- Brief stakeholders on what will be automatic, what remains controllable and what needs manual QA after migration.
How to report September performance
Do not compare September Search performance as if nothing changed. Build a short migration view: affected campaign count, spend share, conversion share, migrated date where available, and post-migration changes in query mix, asset coverage and landing-page behavior. If only a small share of spend is affected, keep the narrative narrow. If a large share is affected, avoid making budget cuts until you separate migration effects from market demand.
Agencies should also make the developer work visible. A clean script update or API compatibility check prevents silent errors that later look like media underperformance. The CFO may not care about campaign objects, but they will care if a reporting connector breaks during a budget review.
The CMO takeaway
AI Max migration is another sign that paid search control is shifting from isolated settings to managed systems. The winning team is not the one that complains about automation after it arrives. It is the team that enters September with an inventory, a QA path and a reporting annotation plan.
The immediate action is simple: audit before the platform migrates for you. Then read performance with enough context to know whether the account has a real problem or only a changed operating surface.
