Microsoft Ads Import Checklist: Validate Google Campaigns Before and After Migration
Microsoft AdsGoogle Adscampaign migrationPPC QAconversion tracking

Microsoft Ads Import Checklist: Validate Google Campaigns Before and After Migration

KKeyword Growth Lab Editorial Team
2026-11-21
8 min read

Use this Microsoft Ads import checklist to validate Google campaign settings, keywords, ads, feeds, budgets, and conversion tracking before launch.

Importing Google Ads campaigns into Microsoft Ads can save setup time, but a completed import is not the same as a launch-ready campaign. Use this repeatable Microsoft Ads import checklist to compare settings before and after migration, identify fields that need manual review, and confirm that budgets, targeting, ads, tracking, and conversion goals are recording correctly.

Overview

A campaign migration should be treated as a quality-assurance project rather than a copy-and-paste task. Google Ads and Microsoft Advertising share many familiar campaign concepts, but their interfaces, available features, naming conventions, audience options, bidding controls, and conversion settings may not map perfectly.

The safest process has three stages:

  1. Prepare: document the Google campaign and define the Microsoft Ads version you intend to launch.
  2. Import: transfer the appropriate campaigns, ad groups, keywords, ads, assets, and supporting settings.
  3. Validate: compare the imported account with the source, correct differences, test tracking, and approve the launch.

This checklist is useful whether you import an entire account, selected campaigns, or a revised campaign structure. It also gives teams a consistent way to review future imports after a rebuild or platform update. For broader allocation decisions, compare this workflow with the Google Ads vs Microsoft Ads ecommerce guide.

A simple migration risk score

To estimate whether an import is ready for launch, score each review area from 0 to 2:

  • 0: not checked or known to be incorrect
  • 1: checked, but requires a manual decision or has a material difference
  • 2: checked and confirmed against the intended setup

Review these ten areas: campaign settings, budgets, locations, audiences, keywords and match types, negative keywords, ads and assets, feeds, conversion goals, and tracking. A maximum score is 20. Do not treat the score as a performance forecast; use it as a sign-off aid. Any zero in tracking, conversion goals, budget, location, or campaign status should block launch until resolved.

How to estimate

Before importing Google Ads to Microsoft Ads, create a source-of-truth worksheet. Record the settings that affect spend, eligibility, targeting, measurement, and reporting. Then compare the worksheet with the imported account rather than relying on memory or a quick visual scan.

Pre-import checklist

  1. Inventory the source account. List campaigns, ad groups, enabled and paused entities, keyword counts, negative keyword lists, ads, extensions or assets, feeds, audiences, and conversion actions. Separate active items from historical or experimental items that should not be imported.
  2. Confirm campaign structure. Note the campaign type, network settings, daily budget, start and end dates, language, location targeting, ad rotation or delivery preferences, and any shared budgets. Record whether a campaign is intended for brand, non-brand, shopping, remarketing, or another defined purpose.
  3. Export keyword controls. Preserve keyword text, match types, final URLs, landing-page parameters, labels, and bids where applicable. Review your negative keyword list separately so important exclusions are not overlooked.
  4. Document measurement. List conversion actions, counting choices, value rules, attribution settings, primary versus secondary goals, imported analytics events, and the tracking parameters used in destination URLs.
  5. Capture bid strategy intent. Record the current bidding approach and its business purpose, such as controlling cost, maximizing volume, or meeting a target efficiency. Settings with similar names may not behave identically across platforms, so plan a manual review.

Post-import checklist

  1. Check campaign status and dates. Confirm that intended campaigns are enabled only after QA. Look for campaigns that imported as paused, changed start dates, or carried over an unintended end date.
  2. Compare budgets and currency. Verify each budget, shared-budget relationship, and account currency. Do not assume that a visually similar number represents the same spending plan; record the intended daily allocation in your sign-off sheet.
  3. Validate locations and languages. Check included and excluded locations, location options, language targeting, and campaign-level overrides. A targeting difference can change traffic more than a keyword edit.
  4. Review audiences. Confirm audience lists, exclusions, observation or targeting choices, remarketing dependencies, and any audience expansion settings. Imported audience names do not prove that the underlying list is available or active.
  5. Inspect keywords and match types. Compare counts and samples by ad group. Check punctuation, match-type mapping, destination URLs, status, bids, labels, and duplicate terms. Use a PPC search term report template after launch to identify queries that require new negatives or keyword refinement.
  6. Review ads and assets. Confirm headlines, descriptions, paths, final URLs, display URLs, image assets, callouts, sitelinks, structured information, and mobile-specific destinations where relevant. Check that imported text still fits the destination platform's fields and that every link resolves.
  7. Check product feeds. For shopping campaigns, verify the selected merchant or product feed, account linkage, product filters, labels, inventory scope, and destination settings. A campaign can appear complete while its product source still needs separate configuration.
  8. Test conversion goals and tags. Confirm that the intended Microsoft Ads conversion goals exist, are associated with the correct campaigns, and use the desired counting and value logic. Test lead forms, purchases, phone calls, or other primary actions in a controlled way before relying on reported performance.
  9. Inspect tracking parameters. Compare final URLs, auto-tagging choices, UTM parameters, and redirect behavior. Keep naming consistent with your UTM parameter convention so platform, campaign, source, medium, and content values remain usable in analytics.
  10. Review bid strategy and limits. Check the imported strategy, targets, bid limits, portfolio relationships, and learning or eligibility messages. If the platform does not support an exact equivalent, choose a deliberate starting configuration and document the change. The Google Ads bid strategy guide can help structure the decision, but the destination platform's current controls should take precedence.

Transfer, review, and warning matrix

AreaOften transferred or representedManual review requiredCommon warning to investigate
Campaigns and ad groupsNames, hierarchy, statuses, and much of the basic structureTypes, networks, dates, delivery, and unsupported settingsUnexpectedly paused or changed campaign type
BudgetsBudget values may be brought acrossCurrency, shared budgets, and intended allocationBudget relationship or amount differs from the source
KeywordsText, ad-group placement, and match-type informationMapping, duplicates, bids, URLs, and statusTerms are rejected, altered, or placed in a different group
Negative keywordsSome campaign or list exclusionsScope, match behavior, and list associationsImportant exclusions are missing or attached at the wrong level
Ads and assetsText and selected supporting assetsField limits, combinations, approvals, and linksAsset omitted, disapproved, or truncated
AudiencesReferences to available audience typesList availability, exclusions, and targeting modeAudience unavailable or applied differently
FeedsSome campaign references or product selectionsFeed connection, filters, labels, and inventoryNo eligible products or missing feed connection
Conversions and trackingSome goal names or imported referencesTags, primary goals, values, attribution, and UTMsClicks record but conversions do not
Bid strategiesIntent or a comparable strategy may be selectableTargets, limits, portfolios, and behaviorNo exact equivalent or strategy not eligible

The table is a planning aid, not a guarantee of feature parity. Import options and supported features can change, so verify the current Microsoft Advertising workflow during every major migration.

Inputs and assumptions

A reliable import review depends on clearly defined inputs. Keep these fields in a worksheet or shared document:

  • Source snapshot: export date, account, campaign names, statuses, budgets, and major targeting settings.
  • Destination plan: intended Microsoft Ads campaign names, daily budgets, locations, languages, and launch status.
  • Keyword controls: keyword totals, match types, landing pages, negative keyword lists, and any ad-group naming rules.
  • Creative inventory: ad text, assets, URLs, tracking templates, and approval-sensitive elements.
  • Measurement design: conversion goals, primary actions, values, tag locations, UTM rules, and the analytics destination.
  • Acceptance rules: which differences are acceptable, which require correction, and who can approve launch.

Assume that platform reports may use different definitions, attribution windows, time zones, or processing delays. For that reason, compare configuration first and performance second. Do not conclude that an import succeeded merely because campaigns are visible or impressions appear in a report.

Also distinguish a technical import from a business-equivalent migration. A campaign can transfer successfully while still requiring a different budget, audience approach, bidding setup, or creative review for the Microsoft audience. If you are comparing platform roles and budget allocation, use the platform comparison guide rather than copying spend mechanically.

Worked examples

Example 1: Search campaign

Suppose a branded search campaign imports with its ad groups and keywords intact. The QA worksheet confirms the campaign name and keyword count, but the negative keyword list is not attached and the conversion goal is not marked as a primary optimization action. The campaign is not launch-ready, even if the ads appear correct. The required fixes are to attach and inspect the exclusions, confirm the intended conversion goal, test the tag, and then approve the campaign.

Example 2: Shopping campaign

A shopping campaign imports with the expected budget and product-focused structure, but the destination feed and product filters have not been confirmed. Treat the campaign as incomplete. Verify the feed connection, eligible products, inventory scope, labels, tracking URLs, and conversion goal before enabling it. The imported campaign name alone is not evidence that product delivery will match the source.

Example 3: Budget and bid strategy change

A non-brand campaign imports with a comparable automated bidding option, but its target and budget do not map exactly to the source setup. Record the source strategy as context, select a deliberate Microsoft Ads starting configuration, and set a review date. Do not judge the new strategy from the first reporting interval; first confirm that spend, clicks, conversions, and search-term data are being collected as intended. For keyword-level diagnosis, pair this review with the quality score improvement checklist and your search-term workflow.

Reusable launch sign-off

Migration: [source account] to [destination account] — date: [date]

  • Campaign settings, budgets, dates, and status: [pass / fix]
  • Locations, languages, audiences, and exclusions: [pass / fix]
  • Keywords, match types, URLs, and negatives: [pass / fix]
  • Ads, assets, feeds, and approvals: [pass / fix]
  • Conversion goals and tracking tags tested: [pass / fix]
  • UTM and analytics reporting verified: [pass / fix]
  • Bid strategy and targets reviewed: [pass / fix]
  • Open issues and owners: [list]
  • Launch approver: [name]

Approve only when critical measurement and spend controls pass, and document any accepted differences.

When to recalculate

Run this checklist for every new import, major campaign rebuild, account restructure, feed change, tracking change, or platform update that affects import options or supported features. Recalculate the readiness score whenever budgets, locations, audiences, match types, negative keyword lists, conversion goals, or bid strategies change.

After launch, perform a second review once enough data is available to inspect delivery and conversion reporting. Compare planned versus actual budget, confirm that URLs preserve tracking parameters, check that conversions are attributed to the intended goals, and review search terms for irrelevant traffic. If reported results look inconsistent, return to configuration before changing bids or keywords.

Finally, refresh this checklist on a regular editorial or operational schedule and whenever Microsoft Advertising changes its import interface, supported campaign features, conversion requirements, or policy guidance. The practical rule is simple: every migration gets a pre-import baseline, a post-import comparison, a tracking test, and a named sign-off.

Related Topics

#Microsoft Ads#Google Ads#campaign migration#PPC QA#conversion tracking
K

Keyword Growth Lab Editorial Team

Senior SEO Editor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.