Google’s 2026 Display-to-Demand-Gen migration introduces a practical choice for eligible advertisers: migrate with the tool and preserve recent campaign history, or rebuild manually with more control. Google says the migrated campaign cannot be reverted, may enter a one-to-two-day learning period, receives a new name ending in #2, and can experience first-day pacing effects because the budget resets. Demand Gen can include Gmail alongside YouTube, Discover, Maps, and the Google Display Network, subject to eligibility and settings. This lesson turns those facts into a cutover checklist.

VISUAL LESSON

What you will learn

  1. 01Decide whether the migration tool fits the campaign.
  2. 02Plan the irreversible cutover and first-day pacing.
  3. 03Verify Gmail and other eligible Demand Gen delivery.
A legacy display campaign preserves history while passing through a migration gate into a multi-surface campaign
A safe migration protects history, checks eligibility and surfaces, anticipates the learning window, and verifies the resulting campaign before expansion.

ILLUSTRATIVE WORKED EXAMPLE

Plan an illustrative migration readiness scorecard

Settings capturedComplete before migration
24/24
Assets approvedTwo require replacement
14/16
Destinations retestedTwo block cutover
6/8
Overall readinessIllustrative gate, not a Google score
70%
Illustrative example—not a benchmark. Replace every sample value with your own campaign, market, and measurement data.

PRACTICAL INTERFACE MAP

Prepare, migrate, and verify the campaign

Baseline01Capture the legacy campaign

Preserve settings, assets, audiences, exclusions, destinations, conversion actions, and a matured performance baseline.

Migration02Review the generated Demand Gen campaign

Use the current tool, confirm the #2 campaign, GDN choice, budget timing, assets, audiences, and irreversible handoff.

Stabilization03Watch the first two days carefully

Verify review, delivery, Gmail and other surface eligibility, pacing, tracking, conversions, and qualified outcomes before edits.

Conceptual walkthrough. Labels, controls, and availability can vary by account, region, plan, and interface version; verify the current screen before acting.

STEP-BY-STEP LESSON

Legacy evidence → migration gate → learning window → verified Demand Gen

PreserveSettings and baseline
MigrateTool and surface choices
StabilizePacing, tracking, quality

THE LEAD ATLAS METHOD

Lead Atlas Data can create a campaign-specific contact list for the same locations, business categories, and market, giving the team an independently measured outreach lane while the migrated campaign stabilizes.See how custom list research works ↗
01

Decide whether to migrate or rebuild

Open Google’s current migration guidance and confirm the campaign is eligible, the tool is available, and its defaults match the business need. Compare tool migration with a manual rebuild based on history preservation, control, asset readiness, audiences, exclusions, surfaces, bid strategy, and timing.

Record the irreversible consequence: Google states that the migrated campaign cannot be reverted. Keep the legacy campaign evidence and define an external fallback, such as pausing the new campaign and launching a separately prepared build, rather than promising an in-tool undo.

02

Preserve the legacy baseline

Capture account and campaign IDs, dates, budget, bidding, locations, languages, audiences, exclusions, content suitability, frequency logic, ads, assets, URLs, UTMs, conversion goals, values, attribution, experiments, approvals, and recent performance after an equal conversion-lag window.

Export the source-of-truth outcome report with qualified leads, sales, refunds, or other downstream measures. Google says the tool can retain 42 days of history, but a platform history transfer does not replace your own audit evidence or business-quality baseline.

03

Prepare assets, surfaces, and restrictions

Review Demand Gen’s current image and video specifications and create eligible variants before migration. Decide whether Gmail, YouTube, Discover, Maps, and the Google Display Network fit the campaign, and inspect the migration tool’s GDN selection instead of accepting it without review.

Check audience availability, sensitive-category restrictions, content suitability, exclusions, geo settings, destination experience, mobile rendering, and measurement. A migrated campaign can technically publish while still being unsuitable for a surface, audience, or regulated offer.

04

Choose the cutover window

Select a low-risk day with active campaign, finance, analytics, creative, and destination owners. Google warns that the migrated campaign enters roughly one to two days of learning and that same-day migration resets the budget, which can cause overdelivery or underdelivery in the first 24 hours.

Write the last legacy delivery time, migration time, budget expectation, monitoring intervals, stop conditions, no-edit window, and communications plan. Avoid changing bids, budget, audiences, and assets during the initial observation period unless safety, policy, broken tracking, or severe pacing requires action.

05

Migrate and verify the #2 campaign

Use the current Google Ads migration tool, inspect the resulting campaign whose name Google says ends in #2, and verify every campaign, ad-group, audience, asset, destination, conversion, exclusion, and surface setting before enabling or trusting delivery.

Deliverable: migrate-versus-rebuild decision, eligibility capture, legacy inventory, 42-day and matured business baseline, asset matrix, surface decision, restriction review, budget-reset plan, cutover log, #2 settings audit, first-48-hour pacing and tracking report, qualified-outcome reconciliation, and scale, repair, or pause decision.

THE TAKEAWAY

Migrate only after preserving settings and outcomes, understanding new surfaces and audience restrictions, timing the budget reset, and defining a no-edit verification window with a rollback alternative outside the irreversible tool.

OFFICIAL REFERENCES

Check the platform’s current instructions.

Platform labels, eligibility, and workflows can change. These official help pages were used to validate this lesson.