Google Ads
Display to Demand Gen Migration: A Preflight Checklist
Updated: September 2026
The safest Display-to-Demand Gen migration starts with a settings audit, a same-day budget plan, asset QA, and a measurement baseline. Google’s migration tool can carry up to 42 days of performance history and reduce the learning period, but unsupported features, a daily-budget reset, and newly submitted ads can still create delivery surprises.
Why this migration needs a preflight
Demand Gen is not simply Display with a new label. It changes eligible bidding, audience handling, exclusions, creative formats, and reporting. Google says migrated campaigns adopt the name of the original campaign plus “#2,” and the original campaign is marked removed. Newly created ads must go through approval.
The migration tool is preferable when eligible because it carries recent history and can reduce learning time to roughly one or two days. A manual rebuild should be a deliberate exception, not a reflex.
Preflight checklist
1. Audit unsupported settings
- Remove ad-group bid modifiers before migration.
- Replace shared budgets with a dedicated campaign budget.
- Map product filters to Demand Gen product scopes or listing groups.
- Remove unsupported legacy business-data feed links.
- Document any portfolio bidding, seasonality adjustment, or payment model that will not carry over.
2. Plan the migration-day budget
Google warns that spend from earlier in the day is not recognized by the new campaign. If the old campaign spends $10 of a $50 daily budget before migration, the new campaign can start with a fresh $50 budget for the rest of that day. Migrate early, lower the temporary budget, or accept the bounded overspend explicitly.
3. Review assets and brand identity
Demand Gen requires a business logo. If the Display campaign lacks one, Google may insert a placeholder. Check logos, business names, aspect ratios, headlines, descriptions, destination URLs, product feeds, and mobile crops. Treat migrated assets as a new creative release.
4. Rebuild exclusions deliberately
Some content-suitability exclusions work at the account level rather than the campaign level. Confirm placement, topic, content, geographic, demographic, and first-party audience controls instead of assuming every legacy setting maps one-to-one.
5. Capture a measurement baseline
Export at least four weeks of spend, impressions, clicks, conversions, value, assisted outcomes, frequency, and placement performance. Preserve campaign IDs and annotate the migration date in analytics. Compare by conversion lag, not only calendar day.
A 72-hour monitoring plan
| Window | What to verify |
|---|---|
| Before launch | Eligibility, approvals, links, budget, exclusions, conversion actions |
| First 6 hours | Delivery, spend pace, destination errors, policy status |
| Day 1 | Budget reset impact, channel mix, asset serving, obvious tracking gaps |
| Days 2–3 | Learning progress, conversion quality, placement patterns, CPA/ROAS direction |
For creative preparation, use the creator-video selection workflow. If the campaign uses fast paths to purchase, review the Demand Gen checkout-link guide.
Frequently asked questions
Will historical performance carry over?
Google says the migration tool can port up to 42 days of performance history, which helps continuity. A manually created campaign does not receive the same stitched history.
Can migrated campaigns overspend on migration day?
Yes. Earlier same-day spend is not counted against the new campaign’s refreshed daily budget.
Do migrated ads need approval?
Yes. Google says they are considered newly created ads and must be submitted for approval, so migrate before a critical launch window.