Your search campaigns are being migrated this month

There is a particular kind of Monday that only happens in paid search. You open an account you have not touched in three weeks, the numbers look different, and nothing in the change history explains it. You check the notifications. Nothing. You check with the person who owns the account. They have not touched it either.

September is going to produce a lot of those Mondays.

Google set out the migration timeline for AI Max in mid August, and Anu Adegbola laid out the dates at Search Engine Land on August 14. The headline is simple enough. Campaign-level broad match and automatically created assets move to AI Max automatically, gradually, across this month. You do not opt in. You do not schedule it. It happens on Google's calendar.

The email you did not get

Here is what makes migrations like this land badly. They are announced properly, in the right places, by the right people, to an audience that is busy. Adegbola wrote it up. The trade press covered it. The in-account notifications are coming. And a large number of competent teams will still be surprised, because the announcement arrived in the third week of August and the consequence arrives in the second week of October.

That gap is where the damage lives. Not in the change itself.

I want to be careful here, because there is a version of this piece that is just hostility toward automation, and that version would be wrong. Google has been consolidating match types and creative generation for years and the direction has been obvious since long before AI Max had a name. Fighting it is not a strategy. Nobody has successfully held the line on manual control in paid search for a decade, and the accounts that tried mostly did worse than the accounts that adapted early and instrumented properly.

So this is not a warning about the migration. It is a warning about the seam.

What the Google Ads AI Max migration actually does in September

Two things are moving, on two different clocks.

Read the last column, because that is where the real variance is. If you run a lean account with a handful of campaigns and no compliance review on ad copy, this migration will be a non-event and you will barely notice it. If your creative goes through legal, or your category has claims you are not allowed to make, automatically created assets under a new system is a governance question and not a performance one.

Those are not the same risk. They will get discussed as though they are.

The part that carries over, and the part that does not

Google says it migrates campaigns using equivalent AI Max settings to minimize disruption, and that existing brand inclusions and exclusions carry over automatically. Take that at face value. It is a sensible thing to build and there is no reason to think it is not what happens.

The trouble is that equivalent settings do not produce equivalent data.

That fourth row is the whole article. Everything technical survives. The comparison does not.

“A migration that preserves every setting and none of your baselines has not preserved your reporting. It has just made the break invisible.”

This is the same failure we described in the target CPA bidding change earlier this year. The mechanics get documented, the teams read the documentation, and then two months later somebody presents a year-over-year chart with a structural break in the middle of it that nobody labeled at the time. It is always cheaper to annotate a change while you remember it than to reconstruct one from a chart in a meeting.

Why October is when this becomes your problem

Think about how the calendar actually plays out.

September is a gradual rollout, which means different campaigns in the same account may move on different days. Some of your September data is pre-migration and some is post, and the boundary is not clean. Then October arrives, monthly reporting runs, and somebody compares a fully migrated October against a partly migrated September against a clean August.

None of these are catastrophes. All of them are much cheaper to handle in advance than in retrospect, and all of them are things a busy team will skip because the account is still running and nothing looks broken.

There is a fourth one that only shows up in bigger organizations, and it is the quietest. Attribution models and internal dashboards frequently hard-code campaign structures, naming conventions and match type dimensions. When the underlying structure changes, some of those break loudly and some of them keep producing a number that is simply wrong. The loud break gets fixed in a day. The quiet one gets reported for a quarter.

If anyone downstream of your ad platform data has built something that assumes today's structure, tell them this month. They will not read the Google Ads release notes, because it is not their job to, and the first they will hear about it is when a field stops populating. That is a two minute message now and a very long meeting later, and it is the single highest leverage thing a paid search lead can do in the next fortnight.

What to do in the next two weeks

Short list. It is genuinely short.

Export your current state now. Settings, structure, brand inclusions and exclusions, and a clean performance window from before any migration touched the account. You want this as a file, not as a memory, because the value of a baseline is that it exists when somebody disputes it.

Set an annotation the day each campaign moves. Whatever your reporting layer is, it supports annotations, and this is what they are for. The team that can point at a labeled date in a chart wins the October conversation in about fifteen seconds. The team that cannot spends the meeting speculating.

Review your negative keyword coverage before the expansion arrives rather than after. Broader matching finds the gaps in your negatives, and it will find them at spend rather than in an audit. If you have inherited an account with negatives nobody has reviewed in a year, this is the forcing function.

And if creative is governed in your business, get ahead of automatically created assets this week. Not because the copy will be bad, but because the approval conversation takes longer than the migration does, and you would rather have it in September on your terms than in October on somebody else's. If your paid search program sits next to an organic program, this is also the moment to check that the two are not about to start telling the same executive different stories, which is a problem we have written about in the paid and organic integration work.

You are not behind

If you are reading this on the first of the month and have done none of the above, you are on time. The rollout is gradual, most accounts will not move on day one, and the entire preparation list above is an afternoon of work for a normal account.

What you cannot do is start in November. The baseline you need is the one that exists before the change, and after the change it is gone. There is no version of this you can reconstruct later, which is unusual in paid search, where almost everything can be dug back out of an export eventually.

The broader read is that this is what the next several years look like. Structures get retired on a schedule, the schedule is published, and the operating skill is no longer choosing settings but noticing when the ground under your reporting moved and labeling the spot. That skill matters more in a world where organic and paid signals increasingly contradict each other and every channel is being rebuilt underneath you at once, especially for B2B teams running long consideration cycles where a broken baseline hides for two quarters before anybody notices.

One last thought, and it is the reassuring one. Every account in your category is going through exactly this, on exactly this schedule, with exactly the same gradual rollout and the same blended September. Nobody has a head start here worth worrying about. The advantage on offer is small, cheap and entirely procedural: it goes to whichever team wrote down what the account looked like before the change. That is not a competitive moat. It is just a habit, and it is available to you this week for the price of an export.

So do the boring thing this week. Export the state, annotate the dates, check the negatives, brief whoever approves your copy. Then let the migration happen, because it is going to happen either way, and the only question you actually control is whether you can explain what it did.

See where you are cited today

A free snapshot audit of your rankings and AI citations before we ever talk.