Google Ads to Microsoft Ads Migration Checklist: Map Keywords, Ads, Tracking, and Budgets Safely
Microsoft AdsGoogle Adscampaign migrationPPC setupadvertising platforms

Google Ads to Microsoft Ads Migration Checklist: Map Keywords, Ads, Tracking, and Budgets Safely

CCampaignIQ Editorial Team
2026-11-18
7 min read

Use this Google Ads to Microsoft Ads migration checklist to map keywords, ads, tracking, budgets, bidding, and post-import validation.

Moving a campaign from Google Ads to Microsoft Advertising is more than copying keywords and pressing import. This checklist helps you map campaign settings, match types, negatives, ads, audiences, conversion tracking, UTM parameters, budgets, and bidding assumptions before launch, then validate performance after the campaigns are live.

Overview

A Google Ads campaign can provide a useful starting structure for Microsoft Advertising, but an imported campaign should be treated as a draft rather than a finished build. Platform capabilities, naming conventions, editorial requirements, audience availability, conversion definitions, and bid behavior may differ. Some settings may not transfer exactly, while others may require a separate setup or review.

The safest approach is to preserve the original Google Ads campaign, document its important settings, import or rebuild a controlled copy in Microsoft Advertising, and compare the two platforms using consistent tracking. Do not judge the migration solely by whether the campaigns appear in the interface. Confirm that the right searches, ads, landing pages, budgets, and conversion events are working.

Migration areaGoogle Ads source to recordMicrosoft Advertising review
Campaign structureCampaign name, objective, location, language, network, scheduleConfirm equivalent settings and document any unavailable or changed options
KeywordsKeyword, match type, status, bid, final URLCheck match-type behavior, editorial status, duplicates, and landing-page relevance
Negative keywordsCampaign and account exclusionsRebuild, deduplicate, and verify scope before enabling traffic
AdsHeadlines, descriptions, paths, assets, final URLsReview format support, character limits, policy status, and approval results
MeasurementConversion actions, values, attribution settings, UTMsRecreate goals, test events, and confirm reporting columns
Budgets and bidsDaily budget, bid strategy, device adjustments, targetsRecalculate starting limits and avoid assuming equal delivery or CPCs

Before beginning, export or record the source campaign's settings and performance window. Include spend, clicks, impressions, conversions, conversion value, search terms, and top landing pages. A consistent baseline makes it easier to separate migration errors from normal platform differences. For keyword structure, see the PPC keyword clustering guide and the keyword management tools comparison.

How to estimate

Estimate the migration using a controlled budget model rather than assuming that imported campaigns will produce identical results. Start with a planning period, such as the first two to four weeks, and calculate a conservative spend ceiling.

Planned spend = daily budget × number of active days

Then create three outcome scenarios using assumptions you can change:

  • Expected clicks = planned spend ÷ assumed CPC.
  • Expected conversions = expected clicks × assumed conversion rate.
  • Expected cost per conversion = planned spend ÷ expected conversions.
  • Expected conversion value = expected conversions × assumed value per conversion.
  • Expected return on ad spend = expected conversion value ÷ planned spend.

Use the source campaign's recent results as a starting assumption only. Microsoft Advertising traffic may have a different mix of queries, devices, locations, and search volume. If you do not have a reliable baseline, use a range instead of a single forecast. For example, model low, middle, and high conversion rates and keep the budget small enough that an incorrect assumption is recoverable.

Budget planning should also account for measurement delays and learning time. Avoid making a large increase because the first few days look efficient, and avoid pausing the campaign after a short period without checking delivery, tracking, search terms, and approval status. The PPC budget allocation template can help separate test spend from established campaign spend.

Inputs and assumptions

1. Campaign and targeting settings

Record the original campaign's objective, location targeting, language, ad schedule, device settings, network selections, and campaign status. Recheck location options carefully: a campaign can appear correctly configured while targeting a broader or narrower audience than intended. Also confirm time zone and billing-account settings before launch, because these affect daily pacing, reporting dates, and budget reviews.

2. Keywords and match types

Export keyword text, match type, landing page, bid, status, and quality-related diagnostics where available. Do not assume that a match type has identical reach or query interpretation across platforms. Preserve tightly grouped intent themes, but review whether each ad group still points to one relevant landing page.

Check for duplicate keywords, unusual punctuation, outdated terms, and keywords that no longer match the offer. Review the search terms report after launch rather than relying only on the imported keyword list. The search terms report workflow provides a repeatable way to identify wasted queries and new opportunities.

3. Negative keywords

Separate negatives into brand protection, irrelevant intent, product exclusions, competitor terms, and operational exclusions such as jobs or support queries. Record whether each negative is applied at account, campaign, or ad-group level. Rebuild the list in the destination platform, then check for conflicts with valuable keywords. A negative keyword library and import template can make this review easier to repeat.

4. Ads, assets, and landing pages

List every headline, description, display path, final URL, tracking suffix, image, extension, and call to action. Imported ad formats may not have a one-to-one equivalent, so identify which elements need rewriting or reformatting. Keep the core promise consistent initially, but do not force text into a format that reduces clarity or violates the destination platform's editorial requirements.

Check that redirects, mobile layouts, forms, phone numbers, pricing, availability, and thank-you pages work from the destination URLs. Use the landing page conversion audit template before sending paid traffic.

5. Audiences and bidding

Document remarketing lists, customer lists, in-market or interest audiences, exclusions, bid adjustments, and observation settings. Audience names do not guarantee that the underlying membership or eligibility transfers. Confirm consent requirements, list status, and audience size within the destination account.

Record the original bid strategy and target values, but treat them as starting references. A strategy that depends on historical conversion data may need a fresh calibration period. Start with a controlled bid and budget plan, then increase exposure after conversion tracking and search quality are confirmed.

6. Conversion tracking and UTMs

Define the primary business actions before importing: purchase, qualified lead, phone call, registration, or another agreed event. For each action, document the trigger, counting method, value, attribution setting, inclusion in optimization, and reporting owner. Recreate or connect the destination platform's conversion goals; do not assume that a Google Ads conversion action automatically reports in Microsoft Advertising.

Use a consistent UTM structure so analytics can distinguish platform, campaign, and ad variation. For example: utm_source=microsoft, utm_medium=paid_search, utm_campaign={campaign_name}, and utm_content={ad_or_asset}. Confirm the platform's supported dynamic parameters before using them, and test the complete URL through a real click or preview process. A cross-channel reporting template can keep Google Ads, Microsoft Advertising, and analytics columns aligned.

Worked examples

Example A: controlled budget estimate

Assume a migration test has a daily budget of $50 for 14 active days. The planning budget is $700. If the working CPC range is $1.75 to $2.50, estimated clicks range from 280 to 400:

  • $700 ÷ $2.50 = 280 clicks
  • $700 ÷ $1.75 = 400 clicks

If the assumed conversion-rate range is 2% to 4%, the estimate is approximately 6 to 16 conversions. These are planning outputs, not performance promises. Replace the assumptions with actual destination-platform results after enough qualified traffic has accumulated, and keep the original Google Ads campaign available for comparison.

Example B: migration worksheet

For each campaign, create one row with these fields:

Source campaign: original name and objective. Destination campaign: new name and status. Targeting: locations, languages, devices, schedule, and network. Keywords: count by match type and landing page. Negatives: account, campaign, and ad-group scope. Ads: approved formats, URLs, and assets. Tracking: conversion goal, UTM pattern, and test result. Budget: daily limit, bid strategy, and review date. Owner: person responsible for validation.

Mark each field as mapped, recreated, not supported, or requires review. This status makes gaps visible before launch and creates a record for the next migration or quarterly parity audit.

When to recalculate

Recalculate the plan whenever an input changes, including CPC, conversion rate, average order value, lead qualification rate, daily budget, campaign schedule, or target market. Revisit the worksheet before a seasonal rebuild, new-market launch, major landing-page change, or bid-strategy change.

Run a post-import validation immediately after launch. Check that campaigns are enabled as intended, ads are approved or clearly flagged, keywords are eligible, negatives have the correct scope, URLs resolve, UTMs persist, and conversion events appear in the intended analytics systems. Then review delivery and search terms on a defined schedule rather than making untracked edits.

Platform interfaces, import capabilities, supported formats, naming conventions, and editorial requirements can change. Review this checklist at least twice a year and whenever either advertising platform announces a material workflow change. Finish with a parity audit: compare settings, spend, clicks, search themes, conversions, and landing-page behavior—not just headline metrics. That process turns a one-time Google Ads to Microsoft Ads migration into a repeatable PPC platform management practice.

Related Topics

#Microsoft Ads#Google Ads#campaign migration#PPC setup#advertising platforms
C

CampaignIQ 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.