Moving a campaign from Google Ads to Microsoft Ads is more than clicking an import button. This checklist helps you compare campaign settings, review keyword and match-type behavior, rebuild tracking consistently, and validate performance before increasing spend.
Overview
A Google Ads to Microsoft Ads migration works best as a controlled duplication rather than a blind copy. The platforms share familiar concepts—campaigns, ad groups, keywords, negative keywords, ads, audiences, budgets, and conversion tracking—but their interfaces, defaults, network controls, editorial requirements, and available bidding options may differ. Import tools can save time, but they do not remove the need for a structured review.
Before starting, define what “successful migration” means. For one advertiser, the goal may be to extend coverage to a new audience. For another, it may be to preserve a proven campaign structure while testing a second source of traffic. Establish the primary conversion, acceptable cost per conversion, target return, daily budget, and launch date before importing anything. These baselines make post-launch decisions less subjective.
Use a campaign inventory as the working document. Record each Google campaign, its objective, location, language, daily budget, bidding approach, network settings, ad groups, landing pages, conversion actions, and current exclusions. A consistent naming system makes the inventory easier to audit; see this PPC campaign naming convention template for a scalable structure.
Do not assume that an imported campaign should launch with identical budgets or bids. Microsoft Ads may reach a different mix of users, devices, partners, and search queries. Treat the initial setup as a measured test with its own pacing and review rules.
What to track
1. Campaign structure and settings
Start with the parts of the account that determine where ads can run and how spend is controlled. For every campaign, compare:
- Campaign name, objective, status, and start date.
- Daily budget, budget delivery settings, and bid strategy.
- Locations, location options, language, time zone, and device adjustments.
- Search network and partner-network selections.
- Ad rotation, audience settings, scheduling, and any campaign-level exclusions.
- Final URLs, tracking templates, and URL parameters.
Document the original Google setting beside the Microsoft Ads setting, then mark each item as “matched,” “adapted,” or “not applicable.” This simple comparison prevents a migration from appearing complete when a meaningful targeting control was not carried over.
2. Keywords and match types
Export or copy the active keyword set before importing it. Group terms by campaign, ad group, intent, and landing page rather than treating the account as one long list. A practical PPC keyword strategy separates branded, non-branded, competitor, product, service, and research-oriented queries when those groups require different budgets or messaging.
Review how each platform represents broad, phrase, and exact matching before launch. Terminology can look familiar while matching behavior and available controls change over time. Verify the current behavior in the Microsoft Ads interface and avoid assuming that an imported match type will produce precisely the same query coverage.
Bring across negative keywords deliberately. Separate campaign-level exclusions from ad-group-level exclusions, and preserve the reason for important negatives. A useful negative keyword list usually includes irrelevant products, unsupported locations, employment or educational searches when they do not fit the offer, and terms that indicate a different buying stage. Review search terms after launch rather than relying only on the original Google exclusions. The negative keyword list guide provides a maintenance framework.
3. Ads, assets, and landing pages
Check every headline, description, display path, image, video, sitelink, callout, structured snippet, and call extension that is relevant to the campaign. Imported assets may need editing because character limits, combinations, approval states, or available asset types may differ. Confirm that each ad group still has a clear message and that its final URL matches the keyword intent.
Use a landing page message match check: the primary promise in the ad should be visible and understandable on the destination page, with the expected form, checkout, phone action, or other conversion path available. A migration is a good time to review the landing page message match checklist rather than assuming the existing destination is suitable for every imported group.
4. Conversion tracking and UTM fields
Conversion actions generally require separate verification in the destination platform. Confirm that the Microsoft Ads conversion goal records the same business event as the Google conversion action, and decide which events are primary for bidding. Test form submissions, calls, purchases, sign-ups, and thank-you pages before enabling automated bid optimization.
Use a consistent UTM naming convention so analytics reports distinguish the platforms without fragmenting campaign data. For example:
| Field | Example | Purpose |
|---|---|---|
| utm_source | microsoft | Identifies the advertising platform. |
| utm_medium | paid_search | Groups the traffic channel consistently. |
| utm_campaign | brand_us_search | Uses the shared campaign taxonomy. |
| utm_term | {keyword} | Captures the keyword where supported. |
| utm_content | {adid} | Helps distinguish ads or creative variants where supported. |
Use the platform’s supported dynamic parameters rather than copying placeholders without testing them. Keep the final URL readable and confirm that redirects do not remove the parameters. For broader governance, use the cross-platform campaign tracking guide.
Cadence and checkpoints
Use three checkpoints: pre-launch, early validation, and recurring review.
Pre-launch checklist
- Export the source campaign inventory and preserve the original structure.
- Import or recreate campaigns, then compare settings line by line.
- Review keyword match types, ad text, assets, negatives, locations, and schedules.
- Confirm budgets and bids are appropriate for a controlled test.
- Install or verify conversion tracking and test at least one conversion path.
- Apply the approved UTM template and inspect a live destination URL.
- Check approval status, disapprovals, broken links, and inactive assets.
First 24 to 72 hours
Check delivery, impressions, clicks, spend, search terms, and conversion data without making large optimizations too quickly. Confirm that traffic reaches the intended locations, that analytics identifies the source correctly, and that no campaign is spending because of an accidental setting or duplicated budget. If conversion data is absent, investigate the tracking path before changing bids.
First two to four weeks
Review performance after enough time has passed for the campaign’s normal buying cycle. Compare click-through rate, cost per click, conversion rate, cost per conversion, impression share where available, and revenue or lead quality. Segment by campaign, search term, device, location, network, and landing page. Then make one class of change at a time—such as search-term exclusions, ad messaging, budget allocation, or bid strategy—so the effect remains interpretable.
For ongoing operations, use a weekly search-term and tracking check, a monthly budget and creative review, and a quarterly structure audit. Larger accounts may need more frequent pacing checks. Maintain a change log with the date, hypothesis, adjustment, affected campaigns, and result.
How to interpret changes
Do not judge the migration by clicks alone. A higher click-through rate can be unhelpful if the traffic is less qualified, while a lower cost per click may reflect weaker intent. Start with the conversion event that matters to the business, then work backward through conversion rate, landing page behavior, search terms, and ad engagement.
Use a simple diagnostic sequence:
- Delivery problem: Check status, budget, bids, targeting, approvals, and network settings.
- Relevance problem: Review search terms, keyword grouping, ad-to-keyword alignment, and negative keywords.
- Experience problem: Inspect landing page message match, speed, mobile usability, and conversion friction.
- Measurement problem: Compare platform conversions with analytics, CRM, or transaction records and inspect attribution differences.
- Efficiency problem: Reconsider bids, budgets, audience adjustments, and low-value segments only after the earlier checks.
Expect the two platforms to produce different results even when the settings appear similar. Differences in audience composition, query volume, network distribution, device mix, and attribution can change the numbers. Compare trends and qualified outcomes, not just a single day or an exact one-to-one ratio. When using automated bidding, allow sufficient conversion information to accumulate and avoid changing targets repeatedly without a clear reason.
For keyword organization and intent decisions, consult the keyword clustering and search intent template. For bidding decisions, use the bid strategy comparison as a planning reference, while confirming which options are available in the destination account.
When to revisit
Revisit this migration checklist whenever you add a campaign, duplicate an existing structure, change a conversion definition, alter the UTM convention, or introduce a new landing page. Perform a fuller audit monthly during the first phase of expansion and at least quarterly once the workflow is stable.
Update the checklist after either platform changes its import process, interface terminology, match-type controls, network settings, conversion setup, or asset requirements. Because these details can change, verify the current options in the account before publishing a new migration run. Refresh screenshots and internal instructions on the same schedule, or sooner if a team member reports that a step no longer matches the interface.
For the next migration, create a copy of the inventory and complete these final actions:
- Record the source campaign’s baseline metrics and business goal.
- Import only the campaigns needed for the test, not every historical campaign by default.
- Mark every setting as matched, adapted, or unverified.
- Test one complete conversion and one analytics session before launch.
- Schedule the 72-hour, two-week, and monthly reviews on the calendar.
- Keep a change log so future decisions are based on evidence rather than memory.
A repeatable migration workflow turns a platform expansion into a manageable experiment. The import may be fast; the durable value comes from preserving intent, validating measurement, and reviewing the variables that determine whether additional spend is justified.
