Importing a Google Ads campaign into Microsoft Advertising can save setup time, but a successful transfer requires more than clicking an import button. This checklist gives you a repeatable migration workflow for reviewing campaign structure, keywords, budgets, bidding, audiences, ad assets, URLs, conversion goals, and tracking before and after the import.
Overview
A Google Ads to Microsoft Advertising import is best treated as a campaign replication project, not a perfect copy. The platforms share familiar concepts, but settings, available features, naming conventions, approval requirements, and reporting behavior may differ. An import can complete without obvious errors while still producing campaigns that spend differently or measure results incorrectly.
The practical goal is to preserve the strategy while validating every setting that affects delivery and measurement. Before starting, create a campaign inventory that records each Google campaign’s objective, location, language, daily budget, bidding approach, ad groups, keyword themes, landing pages, conversion goal, and tracking template. This inventory becomes your comparison baseline after the import.
Use a simple status system for every item:
- Imported: the setting transferred as intended.
- Needs review: the setting transferred but requires platform-specific confirmation.
- Rebuild: the feature or value did not transfer reliably and must be recreated.
Keep the first imported version separate from existing Microsoft Advertising campaigns. Clear naming makes it easier to compare performance, identify duplicates, and pause the correct version if a problem appears. For example, append a consistent marker such as _GA_IMPORT_2026Q1 to the campaign name, then remove or revise it after the validation period.
How to estimate
Before importing, estimate the expected workload and risk rather than assuming that the number of campaigns equals the migration effort. A useful estimate separates the campaign inventory into four quantities:
- Campaign count: the number of campaigns to transfer or rebuild.
- Ad group and keyword complexity: the number of ad groups, keyword themes, match types, and negative keyword lists requiring review.
- Measurement dependencies: conversion goals, imported conversions, URL parameters, call tracking, ecommerce values, and analytics destinations.
- Feature exceptions: assets, audiences, bidding settings, or campaign types that need manual confirmation.
You can calculate a simple review workload using this worksheet:
Review units = campaigns + ad groups + conversion goals + audience groups + landing page groups + feature exceptions
This is not a performance forecast. It is a planning measure that helps determine whether a migration can be checked in one sitting or should be divided into batches. A small account with complex tracking may require more care than a larger account with simple search campaigns.
For each batch, assign a pre-import owner, an implementation owner, and a validation owner. In a small business, one person may fill all three roles, but the checkpoints should remain distinct. The person who starts an import may overlook an incorrect setting because it looks familiar from the source platform.
Use the following sequence:
- Export or document the source campaign settings.
- Remove obsolete campaigns, keywords, ads, and audiences from the migration file.
- Import a controlled batch rather than the entire account when the account is complex.
- Review platform differences before enabling delivery.
- Activate with conservative controls and compare early data against the source account.
Inputs and assumptions
Use this comparison table during the migration. The exact options available can change by campaign type, account configuration, or platform update, so treat the Microsoft Advertising column as a verification point rather than an automatic assumption.
| Area | Google Ads source check | Microsoft Advertising validation |
|---|---|---|
| Campaign structure | Record campaign type, objective, network, location, language, and naming. | Confirm the campaign type and delivery settings are supported and named consistently. |
| Budgets | Capture daily budgets, shared budgets, currency, and start or end dates. | Confirm currency, budget behavior, pacing, and dates before enabling ads. |
| Bid strategy | Record the strategy, target values, bid limits, and learning status. | Choose the closest supported strategy and treat target values as new assumptions until performance data is available. |
| Keywords | Export keyword, match type, status, final URL, and ad group. | Check match-type mapping, duplicate themes, editorial status, and keyword limits. |
| Negative keywords | Export campaign-level and shared negative lists. | Confirm list scope, match behavior, and whether every negative transferred correctly. |
| Audiences | Document audience names, membership sources, exclusions, and observation or targeting settings. | Reconfirm audience availability, eligibility, exclusions, and targeting mode. |
| Ads and assets | Record headlines, descriptions, paths, image assets, status, and final URLs. | Review formatting, asset approval, text limits, pinning, and missing creative. |
| Extensions | List sitelinks, callouts, structured information, images, calls, and promotions. | Rebuild or confirm each asset, its association, schedule, and landing page. |
| URLs and tracking | Capture final URLs, tracking templates, custom parameters, and auto-tagging dependencies. | Test redirects, preserve required parameters, and verify the account’s UTM naming convention. |
| Conversions | Document conversion names, categories, values, counting rules, and attribution settings. | Confirm the intended goals exist, are included in optimization, and record data as expected. |
Pay particular attention to tracking. A campaign can appear healthy in the interface while traffic is being attributed to the wrong source or medium. Use a consistent UTM structure and test a live ad click or preview URL where possible. The UTM naming convention guide can serve as the campaign tracking reference.
Keywords also need a human review. Look for duplicate ad groups, broad themes placed in tightly themed groups, outdated terms, and missing exclusions. Maintain a documented negative keyword list rather than relying only on the import process.
Worked examples
Example 1: A small search campaign
Suppose a campaign has three ad groups, 42 keywords, two negative lists, four responsive search ads, six sitelinks, one conversion goal, and one UTM template. Its migration inventory contains the campaign itself, three ad groups, two negative lists, six ads or asset groups requiring review, six sitelinks, one conversion goal, and one tracking setup.
The import may be technically quick, but the validation checklist is not limited to checking whether the campaign exists. Confirm that each keyword remains in the intended ad group, match types are appropriate, negative lists are attached at the correct level, every ad has usable assets, sitelinks lead to the intended pages, and the conversion goal records a test action. If one feature does not map cleanly, mark it for rebuild instead of treating the import as complete.
Example 2: A multi-campaign account
For an account with brand, non-brand, competitor, and remarketing campaigns, import one representative campaign from each structure before transferring the full account. Compare the resulting names, budgets, keywords, audiences, ads, extensions, URLs, and conversion settings. This pilot identifies repeated mapping problems early and gives you a migration convention for the remaining campaigns.
If the source account uses automated bidding, do not evaluate the imported strategy solely by its label. Confirm the target, budget, conversion goal, and eligibility conditions. A similar-looking bid strategy may still require a different starting assumption. Review bid strategy optimization guidance before changing targets or judging early results.
When to recalculate
Revisit this checklist whenever you import a new campaign, replicate a campaign type, change conversion tracking, or receive a platform update that affects supported features. Also repeat the review after substantial edits to budgets, bidding, audiences, landing pages, or URL templates.
Use this post-import validation checklist before considering the migration complete:
- Campaigns are named, enabled, and grouped according to the account convention.
- Budgets, dates, locations, languages, networks, and devices match the approved plan.
- Keywords, match types, ad groups, and negative lists have been sampled against the source.
- Ads and extensions contain the intended messaging, URLs, and approved assets.
- Audiences and exclusions are attached at the correct level.
- Conversion goals, values, counting rules, and optimization settings are verified.
- UTM parameters resolve correctly and preserve the agreed naming convention.
- Landing pages load, match the ad promise, and work on common devices.
- Initial spend and conversion data are monitored separately from the source account.
Schedule a weekly review for import errors and a quarterly cross-platform structure audit. Recalculate the workload when campaign volume, tracking complexity, or platform capabilities change. For broader account checks, use the PPC account audit checklist; for ongoing keyword structure, refer to the PPC keyword management system. The import is finished only when delivery, measurement, and maintainability have all been checked.