# Google Ads Import for Microsoft Advertising **Category:** platform **Short Description:** Microsoft Advertising's native one-click import tool that copies campaigns, ad groups, keywords, ads, bids, negatives, and most extensions from a Google Ads account, with optional scheduled recurring sync. **Last Updated:** 2026-05-30T00:00:00Z ## 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. ## 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.** — 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.** — 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.** — Demonstrates the most common pitfall — assuming everything imported and not auditing the campaign-type mapping for PMax and Demand Gen gaps. ## Key Points - The single most common onboarding workflow for new Microsoft Advertising accounts - Authenticates against a Google Ads account via OAuth — no manual export required - Performance Max, Demand Gen, and YouTube assets do not transfer cleanly and need separate setup - Audiences and remarketing lists must be rebuilt against Microsoft's UET tag, not the Google tag - Recurring imports keep core search hygiene synced but should be paired with Microsoft-native optimization ## 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 ## FAQs ### What is Microsoft Ads import from Google Ads? It's a built-in Microsoft Advertising feature that imports your existing Google Ads campaigns — structure, keywords, ads, and many settings — into Microsoft Advertising, so you can extend proven Google campaigns onto the Microsoft Search Network without rebuilding from scratch. It's the standard fast path for advertisers to start on Microsoft using their established Google setup. ### How does the Google Ads import work? You connect your Google Ads account in Microsoft Advertising and run an import, which copies campaigns, ad groups, keywords, ads, and supported settings into Microsoft. You can do a one-time import or schedule recurring syncs to keep Microsoft updated as Google campaigns change. After import, you review and adjust for Microsoft-specific features and the different audience before the campaigns go live. ### Why import from Google Ads instead of building fresh? Because it saves significant time and replicates proven structure — most advertisers already have refined Google campaigns, and importing extends them to Microsoft's incremental audience quickly. Rebuilding manually is slow and error-prone. The import gets you running on the Microsoft network fast, after which you optimize for its lower competition, different audience, and unique features (like LinkedIn profile targeting). ### Should I schedule recurring imports or import once? A one-time import is fine to get started, but scheduled recurring imports keep Microsoft campaigns in sync as you change Google campaigns, reducing maintenance. The trade-off: automatic sync can overwrite Microsoft-specific optimizations you've made, so many advertisers import once to launch, then manage Microsoft independently — or sync selectively. Choose based on whether you'll optimize Microsoft separately or mirror Google. ### Do imported campaigns need adjustment for Microsoft? Yes. Although the import replicates structure, the Microsoft network has a different audience, competition, and feature set, so you should review bids, budgets, and settings, remove or adjust anything that doesn't translate, and take advantage of Microsoft-specific capabilities (e.g. LinkedIn profile targeting). Treat the import as a fast starting point, then optimize for Microsoft's distinct environment rather than assuming Google settings are optimal there. ## Related Terms ### Similar Terms - **[Microsoft Advertising](/resources/glossary/platform/microsoft-advertising)**: The import tool is the native onboarding feature of Microsoft Advertising. - **[Microsoft Audience Network](/resources/glossary/platform/microsoft-audience-network)**: Audience Network campaigns are typically built natively rather than imported, since GDN does not map 1:1. - **[Microsoft Ads LinkedIn Profile Targeting](/resources/glossary/platform/microsoft-ads-linkedin-profile-targeting)**: LinkedIn targeting is a Microsoft-native layer to add after import, since it has no Google equivalent to import from. ### Alternatives - **[Google Performance Max](/resources/glossary/platform/google-performance-max)**: Google PMax campaigns are the most common campaign type that does not import cleanly and must be rebuilt. ### Parent Terms - **[Pay-Per-Click (PPC)](/resources/glossary/metrics/pay-per-click-ppc)**: Import enables PPC advertisers to operate a second auction with minimal incremental setup cost.