Import Google Ads Campaigns into Microsoft Ads

Microsoft Advertising can import campaigns from Google Ads, but an import is a translation, not a verified launch. Review campaign status, budgets, bids, locations, schedules, negative keywords, assets, URLs, and UET conversion tracking before enabling delivery. Scheduled imports can also overwrite later Microsoft-side decisions, so configure their scope deliberately.

What can the Google Ads import do?

Microsoft's current Google Ads import guide supports quick, customized, advanced, and scheduled import flows. The available flow depends on the accounts and items selected. Read the import summary and history instead of assuming every object moved successfully.

Choose a narrow first import when the account is complex. Mapping one Google account to one intended Microsoft account makes ownership and rollback easier to understand. Preserve paused status during review if the imported campaigns are not ready to spend.

Which settings need manual review?

• Currency, daily budgets, minimum bids, bid strategies, and campaign status.
• Countries, location intent, radius targets, languages, devices, and ad schedules.
• Negative match behavior, shared lists, account exclusions, and campaign routing.
• Assets, final URLs, tracking templates, custom parameters, and unsupported media.
• Conversion goals, UET tags, attribution, values, and primary optimization actions.

Microsoft notes that broad-match negatives from Google are treated as phrase-match negatives during import. That is exactly why a negative keyword conflict audit belongs in the verification step.

How should tracking be rebuilt and tested?

Decide whether existing UET tags and Microsoft conversion goals already represent the imported campaigns. Test each intended outcome from click through confirmation and confirm it appears once with the right value and currency. Do not map campaigns to a generic goal just because it is available. On the Google side, verify the Google tag is still firing correctly on any page shared between platforms before you trust either account's numbers.

Use the same reasoning as Google Ads conversion counting: define whether repeat actions should count, separate lead stages, and know which goals control bidding before campaigns serve.

Should you schedule recurring imports?

Schedule only after deciding which platform owns each setting. A recurring import can keep ads and campaigns aligned, but it can also restore a Google-side status, bid, budget, or entity that a Microsoft manager intentionally changed. Review the import options, deletion behavior, schedule, and history after every material account redesign.

Record exceptions that should remain Microsoft-specific. Search demand, network behavior, policy, location options, and platform features differ, so synchronized structure does not imply identical performance or identical settings.

What is the safest launch sequence?

Import paused, inspect the results log, run the settings checklist, test UET, confirm billing and account identity, and obtain approval for the exact campaigns and budgets. Then enable a bounded set and monitor queries, spend, conversions, and disapprovals before expanding.

An AI manager can prepare the import and verification report, but activation and spend changes should remain gated. Apply the one-job-per-campaign principle and a disciplined budget pacing review.