Importing a Google Ads campaign into Microsoft Advertising can save setup time, but a copied structure is not automatically a ready-to-launch campaign. This checklist shows what to review before and after a Google Ads to Microsoft Ads import, including keywords, audiences, bidding, conversion goals, ad assets, tracking, budgets, and editorial approvals.
Overview
A campaign migration is best treated as a translation between advertising platforms, not a simple duplication exercise. The original campaign contains useful decisions about account structure, keyword intent, landing pages, messaging, and measurement. However, settings that look similar may behave differently, use different labels, or require separate setup in Microsoft Advertising.
Before importing, define the purpose of the Microsoft campaign. Are you testing a new source of search demand, extending a seasonal campaign, supporting a publisher offer, or creating a second channel for an established PPC keyword strategy? The answer affects how much of the original campaign you should copy. A tightly controlled test may need only a small group of high-intent ad groups, while a full migration may require a broader review of the account hierarchy.
Keep the Google campaign unchanged during the first Microsoft Advertising launch unless there is a deliberate reason to alter both. This creates a useful comparison point. At the same time, do not assume that identical settings will produce identical traffic, query patterns, conversion rates, or costs. Use the imported campaign as a starting framework, then apply Microsoft-specific keyword management, budget controls, audience choices, and tracking.
Platform comparison before import
| Area | What may carry over | What requires a manual review |
|---|---|---|
| Campaign and ad group structure | Names, hierarchy, and much of the organization | Naming conventions, status, network settings, locations, languages, and rollout scope |
| Keywords | Keyword text and, where supported, corresponding match types | Match-type behavior, bids, close variants, search intent, and the negative keywords list |
| Audiences | Some audience associations or remarketing concepts | Audience availability, list membership, targeting versus observation settings, and exclusions |
| Ad assets | Ad copy, final URLs, and selected creative fields | Editorial review, asset limits, extensions, image requirements, tracking parameters, and approvals |
| Bidding | Some budget or bid fields may be transferred | Whether the chosen bid strategy exists, has enough conversion data, or should be replaced with a manual or automated alternative |
| Conversion goals | The intended conversion definitions can guide setup | Tags, goal selection, counting rules, attribution settings, and reporting columns |
Interface labels and import capabilities can change. Confirm the available options in both accounts before relying on an older internal procedure. Treat the table as a planning aid, not a promise that every field will transfer.
Checklist by scenario
Scenario 1: Importing a new campaign for a controlled test
- Choose a limited scope. Start with campaigns that have clear intent, stable landing pages, and a manageable number of ad groups. Avoid importing every historical experiment.
- Record the baseline. Save the Google campaign name, date range, spend, impressions, clicks, conversions, conversion value, and primary search themes. These figures are for context, not a guaranteed forecast.
- Set a distinct naming convention. Include the platform, market, objective, and test status in the Microsoft campaign name. This prevents duplicate reporting and makes budget pacing easier to inspect.
- Review network and location settings. Confirm that the imported campaign is eligible to reach the intended locations, languages, devices, and search network. Do not assume Google selections transfer with the same scope.
- Launch with a deliberate budget. Use an amount that can be monitored without putting the main program at risk. Document the reason for the starting budget and the condition for increasing it.
Scenario 2: Migrating an established search program
- Map campaign intent. Group campaigns by a clear purpose such as brand, non-brand, product, service, location, or high-intent problem. Preserve useful separation rather than importing a cluttered account structure.
- Audit keyword coverage. Compare keyword text, match types, estimated intent, current landing pages, and historical search query themes. Remove obsolete terms and flag keywords that overlap with other imported campaigns.
- Rebuild exclusions. Transfer campaign-level and account-level negative keywords only after checking syntax and scope. A negative keywords list that is too broad can suppress valuable searches; one that is too small can allow irrelevant traffic.
- Reconsider bidding. A target CPA or target ROAS setting from Google should not be copied blindly. Confirm that Microsoft has a comparable option and that the imported campaign has a suitable conversion goal and enough observed activity for the selected approach.
- Separate launch and optimization decisions. First verify delivery, tracking, and relevance. Then evaluate bid strategy, budgets, and query quality using a consistent review period.
Scenario 3: Repeating a seasonal or promotional campaign
- Update dates and offers. Check every headline, description, sitelink, promotion, landing page, and URL parameter for expired language or old deadlines.
- Confirm inventory and destination pages. A valid ad can still create a poor experience if the landing page is unavailable, slow, out of stock, or inconsistent with the offer.
- Recheck budgets and pacing. Use a simple ad budget calculator or pacing sheet to estimate daily spend, then review actual delivery frequently during the first few days.
- Prepare a pause plan. Record who can pause the campaign, what conditions trigger a pause, and which URLs or offers need to be restored after the season.
What to double-check
Conversion tracking and attribution
Do not treat imported conversion names as proof that measurement is working. Confirm that the Microsoft tracking tag or equivalent setup is present on the correct pages and events, that the selected conversion goals are included in optimization, and that test conversions appear as expected. Check whether the goal counts one conversion per user or every qualifying action according to the business objective.
Use consistent UTM conventions across both platforms. A UTM builder can reduce manual errors, but the important decision is the naming standard: define the source, medium, campaign, content, and term values before launch. Then inspect the resulting sessions and conversions in the analytics platform. Differences between platform-reported conversions and analytics-reported conversions are normal enough to investigate rather than immediately label as a tracking failure. A monthly paid media attribution reconciliation workflow can help explain those differences.
Keywords and search intent
Review every imported keyword for intent, destination, and overlap. A keyword that worked in Google may produce a different mix of queries in Microsoft Advertising. Start search query analysis after enough data has accumulated to identify irrelevant themes, new opportunities, and wording that belongs in a separate ad group.
Check the imported negative keywords at the correct level. Brand exclusions, employment terms, free-seeking queries, unrelated products, and competitor terms may require different decisions depending on the campaign objective. Maintain a change log so editors can see why a negative keyword was added or removed.
Ads, extensions, and landing pages
Read every ad as if it were newly written. Confirm that the benefit, qualification, call to action, and landing page message agree. Review extensions or assets separately because a field that exists in one platform may not transfer, may use another label, or may require a different approval process. Avoid assuming that a successful Google ad is automatically compliant or effective in another account.
Run a landing page check on mobile and desktop, test forms and key buttons, and verify that redirects preserve tracking parameters. For a fuller review, use the landing page conversion review template before judging campaign performance.
Post-import QA template
| Check | Status | Evidence or action |
|---|---|---|
| Campaign and ad group names are unique | Pass / Fix | Record the final naming convention |
| Locations, languages, devices, and network settings are correct | Pass / Fix | Compare against the launch brief |
| Keywords and match types were reviewed | Pass / Fix | Note removed, changed, and retained terms |
| Negative keywords are applied at the intended level | Pass / Fix | Record list name and scope |
| Ads, extensions, URLs, and tracking parameters work | Pass / Fix | Save test URL and approval notes |
| Conversion goals and reporting columns are correct | Pass / Fix | Record test event and selected primary goal |
| Budget, bid strategy, and status are intentional | Pass / Fix | Record launch budget and review date |
Common mistakes
- Launching immediately after import: Imported campaigns often need review of settings, tracking, assets, and exclusions before activation.
- Copying bids without context: A bid or target reflects the original platform’s data and conversion setup. Reassess it for the new campaign.
- Assuming match types are interchangeable: Preserve intent, but validate how the destination platform interprets each match type and monitor search terms.
- Ignoring audience differences: Audience lists, eligibility, targeting modes, and exclusions may not align. Treat imported audiences as candidates for review.
- Duplicating conversion goals: Multiple tags or overlapping goals can inflate reports and distort bid optimization. Define one clear primary action for each campaign objective.
- Comparing channels too early: Allow enough time for a useful sample, while monitoring for obvious tracking, policy, relevance, or budget problems from the start.
- Failing to document edits: Without an import log, later performance changes are difficult to explain. Record what transferred, what was rebuilt, and why.
When to revisit
Revisit this checklist before each seasonal planning cycle, before importing a materially different campaign type, and whenever either advertising platform changes its interface, import workflow, supported features, audience options, or policy requirements. A practical minimum is a review at least twice a year, with an additional check after a major account or tracking restructure.
Use this short maintenance routine:
- Confirm the current import path and available field mappings in both accounts.
- Update the comparison notes for match types, audiences, extensions, bidding, and conversion goals.
- Run the QA template on one low-risk test campaign before repeating the process at scale.
- Review search queries, conversion tracking, budget pacing, and landing-page performance after launch.
- Record lessons in the campaign migration log so the next import begins with current guidance.
For ongoing cross-platform reporting, pair the import checklist with a cross-channel paid media reporting template. The goal is not to make Google Ads and Microsoft Advertising identical. It is to preserve the campaign’s intent while adapting its controls, measurement, and editorial decisions to each platform.