Microsoft Ads Import from Google Ads
Import from Google Ads is the native onboarding workflow inside Microsoft Advertising that lets an advertiser authenticate a Google Ads account and replicate its campaign structure into Microsoft Advertising in minutes. It is by far the most-used onboarding path for the platform and the practical reason most Google advertisers can stand up a Microsoft account in an afternoon rather than a sprint. The import is available both in the web UI (Import menu) and via Microsoft Advertising Editor (the desktop bulk-editing tool, analogous to Google Ads Editor). What imports cleanly: campaigns and their settings, ad groups, keywords (with match types), Responsive Search Ads, Expanded/standard text ads, bids, negative keywords and negative lists, most ad extensions (sitelinks, callouts, structured snippets, call extensions), Shopping campaigns linked to a Microsoft Merchant Center, and audience associations where an equivalent exists. What does not transfer cleanly: Google Performance Max campaigns have no 1:1 equivalent and convert to Microsoft's own PMax or are skipped, Demand Gen/Discovery campaigns don't map, certain audience types and remarketing lists must be recreated against Microsoft's UET tag rather than the Google tag, and YouTube-specific campaign assets are not relevant. The most important best practice is to schedule a recurring import (daily or weekly) rather than treating import as a one-time setup. This keeps new keywords, ads, and budgets synced from the Google account, but it also creates a discipline trap: advertisers who never customize beyond the imported structure leave Microsoft-specific value on the table — notably LinkedIn profile targeting, Audience Network campaigns, and bid modifiers tuned to Microsoft's older/desktop audience. The recommended pattern is to import as a baseline, then add Microsoft-native layers on top, and use the recurring sync to keep core search campaign hygiene in lockstep with Google.
Definition
Import from Google Ads is the native onboarding workflow inside Microsoft Advertising that lets an advertiser authenticate a Google Ads account and replicate its campaign structure into Microsoft Advertising in minutes. It is by far the most-used onboarding path for the platform and the practical reason most Google advertisers can stand up a Microsoft account in an afternoon rather than a sprint. The import is available both in the web UI (Import menu) and via Microsoft Advertising Editor (the desktop bulk-editing tool, analogous to Google Ads Editor). What imports cleanly: campaigns and their settings, ad groups, keywords (with match types), Responsive Search Ads, Expanded/standard text ads, bids, negative keywords and negative lists, most ad extensions (sitelinks, callouts, structured snippets, call extensions), Shopping campaigns linked to a Microsoft Merchant Center, and audience associations where an equivalent exists. What does not transfer cleanly: Google Performance Max campaigns have no 1:1 equivalent and convert to Microsoft's own PMax or are skipped, Demand Gen/Discovery campaigns don't map, certain audience types and remarketing lists must be recreated against Microsoft's UET tag rather than the Google tag, and YouTube-specific campaign assets are not relevant. The most important best practice is to schedule a recurring import (daily or weekly) rather than treating import as a one-time setup. This keeps new keywords, ads, and budgets synced from the Google account, but it also creates a discipline trap: advertisers who never customize beyond the imported structure leave Microsoft-specific value on the table — notably LinkedIn profile targeting, Audience Network campaigns, and bid modifiers tuned to Microsoft's older/desktop audience. The recommended pattern is to import as a baseline, then add Microsoft-native layers on top, and use the recurring sync to keep core search campaign hygiene in lockstep with Google.
Key Points
- 1The single most common onboarding workflow for new Microsoft Advertising accounts
- 2Authenticates against a Google Ads account via OAuth — no manual export required
- 3Performance Max, Demand Gen, and YouTube assets do not transfer cleanly and need separate setup
- 4Audiences and remarketing lists must be rebuilt against Microsoft's UET tag, not the Google tag
- 5Recurring imports keep core search hygiene synced but should be paired with Microsoft-native optimization
Examples
A new advertiser connects their Google Ads account, runs a one-time import, and has 40 Search campaigns, 600 ad groups, and 12,000 keywords live in Microsoft Advertising the same afternoon.
Context
Illustrates why the import tool is the canonical onboarding path — the alternative manual rebuild would take an agency week of bulk-sheet work.
An e-commerce account schedules a weekly recurring import to mirror Google Shopping campaign changes, while running a separate manually-managed Audience Network prospecting campaign.
Context
Shows the recommended hybrid pattern: sync the core search/shopping spine from Google, and build Microsoft-unique inventory separately.
An agency imports a Google account that uses Performance Max heavily, then discovers conversion volume is much lower than expected because PMax did not transfer 1:1 and needs to be rebuilt as Microsoft Performance Max with fresh asset groups.
Context
Demonstrates the most common pitfall — assuming everything imported and not auditing the campaign-type mapping for PMax and Demand Gen gaps.
Best Practices
- ✓Schedule a recurring import (weekly is the most common cadence) rather than treating it as a one-time setup
- ✓Run the pre-import preview and explicitly review which Google Performance Max and Demand Gen campaigns are being skipped or remapped
- ✓After the first import, install UET, rebuild audiences against UET, and add Microsoft-native layers (LinkedIn targeting, Audience Network campaigns)
- ✓Use Microsoft Advertising Editor for large bulk imports and ongoing edits — it is materially faster than the web UI at scale
