Google Ads

Google Display Ads to Demand Gen Migration: Agency Checklist

Migrate Google Display Ads to Demand Gen with an agency checklist for eligibility, budgets, bidding, assets, approvals, tracking and post-cutover validation.

•9 min read•By Advertisng Research Team•Reviewed September 2, 2026
Google Display AdsDemand GenGoogle Display NetworkCampaign MigrationAgency WorkflowGoogle Ads
Advertisng Research Team
Public Ad Intelligence Research
Google Ads
9 min read

The Advertisng Research Team studies observable public Meta and Google ad evidence, documents limitations, and turns repeatable findings into agency research workflows.

Advertisng Research Team reviews public ad-library evidence and separates observable facts from performance assumptions. Read our editorial policy and research methodology.

Direct answer

Google is moving Display campaign management into Demand Gen, with a phased migration tool already available to eligible advertisers and the broader transition expected to complete in 2027. Agencies should inventory unsupported settings, record a performance baseline, avoid mid-study migrations, control same-day budget exposure, review newly submitted ads and validate delivery before changing bids or expanding beyond Google Display Network inventory.

What is changing for Google Display Ads?

Google Display Network inventory is gaining a new campaign-management home inside Demand Gen. Advertisers can still run Display-only campaigns by keeping Google Display Network selected without adding YouTube, Discover, Gmail or Maps.

Google launched the migration tool in phases beginning June 2026. Its official blog says the broader transition is expected to complete by 2027. Google has not published a single compulsory migration date for every remaining Display campaign, so agencies should use the account notification and eligibility status as the operational source of truth.

The migration is not a cosmetic rename. A migrated campaign becomes a Demand Gen campaign, the original Display campaign is marked removed, and the migration cannot be reversed.

What should an agency inventory before migration?

Start with a written account inventory before clicking Upgrade to Demand Gen.

Control areaEvidence to recordWhy it matters
Campaign identityAccount, campaign ID, name, status and ownerCreates a durable mapping to the migrated campaign
Goals and biddingConversion goals, bidding strategy, target and attribution windowSome Display bidding options do not map directly
BudgetDaily budget, shared-budget status and spend at cutover timeSame-day spend is not recognized by the new campaign budget
AudiencesAudience lists, exclusions, observation settings and seed sourcesSome audience controls work differently in Demand Gen
CreativeAd formats, disclaimers, logos, business name, feeds and approvalsUnsupported assets can block migration; migrated ads are reviewed again
MeasurementConversion tags, URL parameters, lift studies and reporting baselineMigration can interrupt studies and change comparison conditions
Placement controlsInventory, exclusions and suitability settingsConfirm what transfers and what must be rebuilt
Historical baselinePrior 28 days plus conversion-lag contextSupports a like-for-like post-cutover review

For broader channel allocation, use the Google Ads versus Facebook Ads decision framework. Migration eligibility should not be confused with evidence that Display deserves more budget.

Which settings can block or change the migration?

Google's migration documentation lists several common blockers and feature differences. Agencies should verify the live account because availability can change.

  • Campaigns using shared budgets need a dedicated budget before migration.
  • Manual CPC, viewable-impression bidding and pay-for-conversions are not supported as the same Demand Gen bidding options.
  • Portfolio bidding, seasonality adjustments and some bid adjustments are not supported.
  • Some ad-group exclusions, click-to-call assets, lead-form assets, disclaimers, product filters and legacy business-data feeds can block the tool.
  • A business logo is required. Google may insert a placeholder when the source campaign has no logo, but the agency should review it before serving.
  • Uploaded HTML5 and third-party ads are documented as coming later, with late 2026 planned availability.

Do not remove a working control simply to force migration without documenting the client impact. If an unsupported feature is material to delivery or compliance, hold the cutover and choose a supported alternative with the client.

Original artifact: the Display-to-Demand-Gen cutover ledger

Use one row per migrated campaign. Store screenshots or exports separately; the ledger should remain readable without them.

FieldBefore cutoverAfter cutoverPass conditionOwner
Campaign mappingDisplay ID and nameDemand Gen ID and nameOne-to-one mapping recordedMedia buyer
StatusEnabled or pausedSame intended statusNo accidental activationMedia buyer
Daily budgetSource budget and spend-to-timeNew budget and launch timeSame-day exposure approvedAccount lead
BiddingStrategy and targetSupported mapped strategyClient KPI unchanged or exception loggedStrategist
ChannelsGDN sourceGDN-only or approved expansionChannel scope matches planStrategist
CreativeAsset count and approvalsNew review statusRequired assets approvedCreative lead
TrackingURLs, UTMs and conversionsLanding and conversion checksTest path completesAnalyst
DeliveryLast 7-day baselineFirst 24-hour deliveryNo unexplained zero or spikeAnalyst
EvaluationPrior 28 daysFirst full conversion cycleLike-for-like window definedAccount lead

This ledger is a control document, not a performance forecast. It records what changed, who approved it and when the account is ready for evaluation.

How should agencies schedule the cutover?

1. Avoid active lift studies

Google says a migrated campaign is not automatically associated with an existing lift study. Do not migrate in the middle of Conversion Lift, Brand Lift or another study unless the study owner has documented the impact.

2. Control the same-day budget reset

Spend earlier in the day on the source Display campaign is not recognized by the new Demand Gen campaign. If the old campaign spent part of its daily budget, the migrated campaign can still begin with its full daily budget for the rest of that day. Schedule a low-risk cutover time, record spend immediately before the change and obtain approval for the maximum same-day exposure.

3. Allow for ad review

Google treats migrated ads as newly created ads, so they must be reviewed. Migrate before a critical launch window and check policy status rather than assuming uninterrupted serving.

4. Preserve the initial channel scope

Google Display Network is selected during migration and cannot be removed in that flow. Keep the campaign GDN-only when the goal is a controlled transfer. Add YouTube, Discover, Gmail or Maps only as a separate, documented test.

5. Wait before judging performance

The migration tool can carry up to 42 days of performance history and Google says this can reduce learning time to about one or two days. That is not a promise of identical results. Monitor delivery immediately, then use a complete conversion cycle and the client's conversion lag before judging efficiency.

The GA4 campaign-data import validation checklist provides a separate reconciliation workflow when non-Google and Google costs are compared in Analytics.

Should every eligible campaign migrate immediately?

No. Eligibility means the tool can process the campaign; it does not prove that today is the best cutover date.

Migrate when the agency has a clean inventory, a compatible control plan, client approval for material feature changes, a safe budget window and enough time for review and observation. Hold when a lift study is active, a required feature is unsupported, the campaign is tied to a critical launch or the same-day budget risk is unacceptable.

Google advises against migrating more than 100 campaigns in a single batch. Agencies should use smaller cohorts, validate one representative campaign and then expand the rollout.

Can public competitor-ad research help with this migration?

Only at the creative and market-evidence layer. The Google Ads Transparency Center research workflow can help an agency record visible advertiser identity, creative, copy, format, region and served-date context. The multi-platform ad-intelligence framework can organize comparable Meta and Google observations.

Use the ad creative analysis rubric to turn repeated visible patterns into testable hypotheses. Do not treat a competitor's presence on Google surfaces as evidence that the agency should expand a client's migrated campaign beyond GDN.

What can public ad data not prove?

Public Google ad evidence cannot reveal a competitor's Demand Gen channel selection, campaign settings, audience logic, bid strategy, budget, migration path, conversion data, profitability, incrementality or causal lift. It also cannot prove that a visible ad served through Demand Gen rather than another eligible Google campaign type. Those decisions require first-party account data and controlled measurement.

What should the agency deliver to the client?

The migration handoff should include:

  1. The source-to-destination campaign map.
  2. A list of settings that transferred, changed or were removed.
  3. The approved same-day budget exposure.
  4. Creative and policy-review status.
  5. Tracking and landing-page validation.
  6. A baseline window and post-cutover evaluation date.
  7. Named owners for delivery, measurement and escalation.

The deliverable should separate platform facts from agency choices. Google's migration tool defines what can transfer; the client and agency still own the risk decision.

Frequently asked questions

Is Google shutting down the Display Network?

No. Google says advertisers can continue serving on Google Display Network inventory. The campaign-management workflow is moving into Demand Gen.

When will every Display campaign migrate?

Google says the broader transition is expected to complete by 2027, but the current Help page uses "coming later" for universal new-campaign and automatic-migration milestones. Check account notifications instead of inventing a single deadline.

Can an agency undo the migration?

No. Google says a campaign migrated with the tool cannot be reverted to a Display campaign.

Does the migration preserve history?

The tool can port up to 42 days of performance history to support continuity. The original Display campaign remains removed in the account and its reporting history can remain available for up to five years.

Will migrated ads be reviewed again?

Yes. Google treats them as newly created ads, so they are submitted for approval.

Can the migrated campaign stay Display-only?

Yes. Keep Google Display Network as the only selected channel. Expansion to other Demand Gen surfaces should be a separate test.

A restrained next step

If the migration plan needs a creative evidence set, use Advertisng's public Meta and Google ad workspace to organize observable ads in a private board. Keep the cutover decision in the client's first-party account data; public ad references do not expose competitor campaign performance.