How to Set Up Microsoft Ads Import from Google Ads

Set up a Microsoft Ads import from Google Ads by defining the source and destination accounts, selecting the smallest useful scope, mapping currencies and entities, reviewing budgets, bids, targeting, ads, feeds, negatives, and conversion goals, choosing one-time or recurring synchronization, and completing post-import QA before enabling delivery. An import is a migration workflow, not proof that the two platforms have identical settings or business outcomes.

Microsoft's current campaign-import guidance, import-field documentation, and Shopping import guidance describe the platform process. This article is educational setup guidance, not account administration, financial, legal, privacy, or platform-policy advice; the source and destination owners approve access, mappings, spend, and launch.

What should a Microsoft Ads import setup decide?

Write the import contract before connecting the accounts. State which Google Ads data may be read, which Microsoft Advertising account may receive it, which entities are included, which settings may be translated, whether campaigns may serve after import, and what evidence is required before launch.

Define source, destination, and scope

Record:

source Google Ads manager and account;
destination Microsoft Advertising manager and account;
business, brand, legal, billing, market, domain, currency, and time-zone owner;
campaigns, ad groups, keywords, products, feeds, audiences, assets, goals, and statuses in scope;
one-time or recurring schedule, overwrite and deletion behavior; and
approval owner, QA owner, launch state, rollback or pause procedure, and proof condition.

Do not let an auto-selected account, former client, test account, or neighboring regional account become the destination by default. An import log from the wrong account is still a failed setup.

Choose the launch boundary

Decide whether imported campaigns should remain paused, be created as drafts where supported, or be eligible for a controlled launch after QA. Preserve the source running state separately from the destination launch decision. A campaign that is active on Google is not automatically safe to activate on Microsoft.

Keep one import boundary per owner or business decision where possible. If one destination combines several sources, create a mapping table for account, entity, currency, time zone, domain, market, feed, UET tag, owner, and import name.

Record unsupported and transformed settings

List fields that map, translate, default, pause, fail, or require manual recreation. Include campaign type, budgets, bids, currencies, networks, locations, languages, demographics, audiences, negatives, ads, assets, URLs, tracking parameters, product data, conversion goals, UET, schedules, and statuses.

Do not treat an omitted field as equivalent behavior. Mark the owner, expected result, manual follow-up, and proof condition for every material difference.

Should you use Quick, Customized, or Advanced import?

Choose the import mode by the risk and mapping work, not by speed alone. Microsoft's import workflow documents Quick, Customized, and Advanced flows; the live interface and supported options may change.

Use Quick import only for a known, low-risk scope

Quick import can be appropriate when the source and destination are already mapped, account currency and time zone are understood, entity scope is small, and the owner has approved the default behavior. Keep the destination campaigns paused or otherwise controlled until targeting, budgets, goals, pages, and status are verified.

Do not use Quick import to avoid decisions about currency, budgets, conversion goals, negatives, recurring sync, or deletion. A fast import can create a large review queue or a live spending risk.

Use Customized import to control common mappings

Customized import is useful when the owner needs to choose campaigns, adjust budgets or bids, select entity types, control status, map conversion goals, or exclude settings that should be created manually. Record every selection and transformation before running the import.

Compare the selected scope with the import contract. An unchecked campaign, product feed, audience, negative list, or conversion goal can change what the destination can serve or measure.

Use Advanced import for entity and overwrite control

Advanced options are appropriate when the source is large, several account boundaries exist, settings need careful translation, or recurring import and overwrite behavior could affect delivery. Map source entity to destination entity, owner, schedule, status, budget, bid, goal, feed, URL, and deletion rule.

Do not select the most detailed mode just to create a sense of control. The required evidence is the same: known mapping, approved scope, safe status, post-import QA, and an owner for every exception.

How should you prepare the Google and Microsoft Ads accounts?

Prepare both sides before starting the import. Access, account identity, currency, time zone, domain, Merchant Center or feed, UET, payment, and campaign ownership must be clear.

Verify source account and access

Confirm the Google manager and account, user or OAuth access, source owner, account status, billing entity, website, markets, campaigns, feeds, goals, audiences, and current change history. Save the source configuration and reporting boundary that the destination will be compared with.

Do not assume the source campaign's active state, conversion label, budget, location, or landing page will be appropriate in Microsoft Ads. The import reads source settings; it does not decide whether the destination should run them.

Verify destination account, currency, and time zone

Confirm Microsoft Advertising manager and account, user access, account number, business or billing entity, domain, market, currency, time zone, payment readiness, UET tag, Merchant Center store, feed, and destination owner. Microsoft's account guidance, currency guidance, and time-zone guidance are useful references.

If source and destination currencies differ, choose the approved mapping or exclude the entity until an owner confirms the conversion. Do not treat a converted budget or bid as identical to the source amount without recording the date, method, rounding, and owner.

Confirm UET and feed ownership

Decide whether to associate an existing Microsoft UET tag, create or verify a separate goal, or leave conversion goals for manual setup. Confirm that the destination website, checkout, form, app, or CRM path can be tested. For Shopping or product campaigns, verify the Microsoft Merchant Center store, catalog, feed source, product IDs, market, currency, price, stock, and link ownership before importing product-dependent campaigns.

The source's conversion tag or Merchant Center store does not become the destination's authority automatically. A campaign can import successfully while its UET or feed points to the wrong account or stale catalog.

Which imported settings can change Microsoft Ads spend?

Review budgets, bids, bid strategies, targets, schedules, status, networks, locations, languages, audiences, conversion goals, and recurring overwrite behavior before allowing delivery. Microsoft's budget guidance and bid-strategy guidance explain destination concepts; they do not approve the source settings for the business.

Review budget and bid conversion

Create a source-to-destination table for campaign, budget type, amount, currency, daily or lifetime boundary, bid strategy, target CPA or ROAS, manual bids, shared budgets, portfolio strategies, and start or end conditions. Identify what is translated, recalculated, unsupported, or left unchanged.

Do not enable an imported campaign until the destination budget and bid express the approved spending decision. A source amount in another currency, a shared budget with new consumers, or a target based on an unverified conversion goal requires owner review.

Review strategy eligibility and conversion prerequisites

Check that the destination campaign type and market support the imported strategy. Confirm UET, campaign-level goals, count, window, attribution, value, currency, and source-system reconciliation before using Maximize conversions, Target CPA, Maximize conversion value, Target ROAS, or another automated objective.

If the source strategy is unsupported or the destination goal is missing, leave the destination in a safe status and record the required manual setup. Do not substitute clicks, impressions, or a broad goal without documenting the changed objective.

Treat shared budgets as a destination decision

List every source campaign in a shared budget and every destination consumer after translation. Compare market, product or service, currency, conversion goal, value, schedule, capacity, and owner. A shared budget can redistribute spend differently after import even if the campaign names are unchanged.

Keep a separate budget where the destination has a different owner, route, margin, or risk limit. Share only when the owner accepts the combined decision boundary.

Which Google Ads settings do not map one-to-one?

Treat each platform's setting as a claim requiring destination proof. Similar labels do not guarantee similar behavior.

Review network and campaign-type mapping

Record source network, campaign type, destination campaign type, partner or audience reach, product or feed dependency, assets, and landing pages. Confirm that the destination can serve the intended market and that any expanded reach is an explicit decision.

Do not infer equivalent delivery from a completed import. Check destination eligibility, diagnostics, status, and actual preview or test path before launch.

Review location and language settings

Compare source locations, exclusions, location options, language, schedule, market, office or service area, and destination page. Test representative in-market and out-of-market routes through the approved QA process. A translated location can be syntactically valid while changing who sees the ad.

Review keywords, negatives, and match behavior

Compare keyword, match type, search term, negative keyword, list, scope, and receiving page. Microsoft and Google can differ in match behavior, limits, syntax, and campaign structure. Use the Microsoft Ads negative-keyword settings guide for related review, but read the complete query before accepting an imported exclusion.

Do not let an imported negative block an eligible product, service, market, support route, or brand query. Record source, destination, rationale, scope, owner, and proof condition.

Review ads, assets, URLs, and tracking

Test headlines, descriptions, images, videos, extensions, final URLs, redirects, tracking parameters, consent, mobile rendering, forms, calls, product pages, checkout, and confirmation. A source ad can have a destination that is stale, unsupported, disapproved, or inconsistent with the Microsoft campaign.

Keep any policy, professional, legal, privacy, product, or consumer-claim review with the appropriate owner. Importing approved Google copy does not transfer that approval to a new platform, market, or destination.

Review products, feeds, and Merchant Center mapping

For Shopping or product-dependent campaigns, compare Microsoft Merchant Center store, feed source, product ID or variant, title, description, image, price, currency, availability, link, shipping, market, product group, and diagnostics. Microsoft's Shopping import documentation can help identify the mapping, but post-import item and page QA remains necessary.

How should conversion goals be handled during import?

Treat goals as a separate migration decision. An imported goal name can conceal a different trigger, count, window, value, currency, attribution model, or UET association.

Decide whether to import goals or create them separately

List source goals, destination goals, UET tags, event conditions, scopes, count rules, windows, values, currencies, campaign inclusion, and source systems. Import only when the destination can prove that the goal represents the same business stage and uses approved data. Otherwise create or verify the destination goal separately and keep the campaign from optimizing to an unproven event.

Review supported goal types and attribution mapping

Compare URL, event, call, app, offline, or other source conditions with the destination's supported options. Confirm UET on the intended pages or app paths, consent behavior, deduplication, values, currency, and downstream record. Do not assume a Google conversion label maps to a Microsoft goal with identical semantics.

Check goal names and collisions

Create a source-to-destination goal map with unique owner, purpose, event, and campaign scope. Identify names that collide with existing Microsoft goals or represent the same action through multiple integrations. Keep diagnostic, reporting-only, and optimization goals distinct.

How should you set an import schedule and deletion behavior?

Choose one-time or recurring synchronization deliberately. Microsoft's import history and scheduling controls can update the destination after the initial run, so the schedule is part of the account's change-management boundary.

Choose one-time or recurring synchronization

Use one-time import for a controlled migration or when the destination will be managed independently after QA. Use recurring synchronization only when the owner wants source changes to continue affecting the destination and has documented the fields, cadence, owner, review, and stop condition.

Do not create a recurring schedule simply because it is available. Record what the source is allowed to overwrite, what the destination team may edit, and how an intentional Microsoft-specific change is protected.

Decide how removed source items are handled

Define whether deleted, paused, or removed source campaigns, keywords, ads, products, goals, or negatives should be deleted, paused, left unchanged, or reviewed manually in the destination. Preserve the prior destination state before the first scheduled run.

Check recurring overwrite behavior

Test or inspect whether recurring import can overwrite budgets, bids, goals, statuses, ads, URLs, locations, negatives, feeds, or tracking. Keep an import owner and a change-history review. If the schedule can reintroduce a setting the destination owner deliberately changed, disable or narrow it only after approval and document the reason.

What should happen immediately after a Microsoft Ads import?

Treat the import result as the beginning of destination QA. Save the import log, warnings, skipped entities, translated fields, created or updated IDs, and timestamp. Do not activate campaigns because the import completed without a technical error.

Check import results and warnings

Review the import summary, history, errors, warnings, skipped items, unsupported settings, duplicate names, rejected ads, missing goals, feed or product issues, URL changes, and status results. Map each exception to an owner, manual action, proof condition, and launch decision.

If the import created a different campaign type, default, budget, target, location, goal, or feed state, preserve the destination value and explain the difference. A warning that appears minor in the log can change spend or measurement.

Verify account, targeting, and destination paths

Open representative destination campaigns and confirm account, campaign type, market, language, network, locations, exclusions, schedule, device or audience scope, keywords or products, ads, assets, pages, calls, forms, checkout, feed, and tracking. Test in-scope and out-of-scope routes through the approved process.

Do not use source screenshots as proof of destination behavior. Read the destination settings and test the actual page, product, call, form, or checkout path.

Verify budgets, bids, and status before delivery

Compare imported and approved budget type, amount, currency, shared consumers, bid strategy, Target CPA or ROAS, manual bids, schedule, status, and campaign eligibility. Confirm that campaigns remain paused or are approved for the intended controlled launch.

Check recurring imports, automated rules, scripts, portfolio strategies, shared budgets, and future overwrite behavior. Record any setting that can activate or materially change spending after the initial QA.

Verify conversions and downstream records

Test UET, conversion goals, campaign-level inclusion, count, window, attribution, value, currency, deduplication, consent, and offline or CRM handoffs. Reconcile a controlled test with the source record and verify that invalid, duplicate, staff, cancelled, refunded, or returned actions do not count unless explicitly intended.

For product campaigns, reconcile item or variant, price, stock, link, market, currency, group, page, cart, checkout, order, fulfillment, refund, and return. For lead campaigns, reconcile query, page, form, call, contactability, qualification, appointment, and later outcome.

How should you launch an imported Microsoft Ads campaign safely?

Launch is a separate approval from import. The destination owner should approve the exact post-import state, scope, budget, goal, and proof before enabling delivery.

Use a controlled first launch

Start with the smallest approved scope that proves the destination mapping. Record campaign, market, product or service, budget, bid, status, landing page, conversion goal, owner, start condition, stop condition, and review evidence. Do not expand because the source campaign was successful or because the import is technically complete.

If the owner wants a full launch, document that decision and the risks that remain unproven. Keep source and destination reporting separate so the first Microsoft results are not blended into Google history without a defined comparison.

Monitor for translation failures

Review delivery, disapprovals, search terms, product diagnostics, spend, clicks, conversions, calls, forms, orders or leads, values, and downstream outcomes. Compare against the approved destination scope and not against a mismatched source metric. Watch for wrong market, wrong URL, stale product, unexpected network, duplicated goal, excessive spend, or recurring overwrite.

Do not call the import successful because impressions or clicks appeared. The destination must reach the intended route and produce the intended measurable stage.

Preserve rollback and pause evidence

Keep the pre-import export, post-import export, import log, change history, schedule, approvals, and pause or rollback procedure. If a material issue appears, pause or revert only through the authorized owner and record the exact change. Do not delete source or destination entities merely to make the account look clean.

Microsoft Ads import-from-Google setup checklist

Before importing

Define source, destination, entity scope, currency, time zone, domains, markets, owners, launch state, schedule, overwrite, deletion, rollback, and proof condition.
Confirm source and destination access, account identity, billing or payment readiness, UET, Merchant Center or feed, campaigns, goals, and change-history visibility.
Preserve source and destination before-state evidence for campaigns, budgets, bids, targeting, negatives, ads, assets, URLs, products, goals, and status.

During import setup

Choose Quick, Customized, or Advanced based on mapping and risk; record every selection and transformation.
Review budget, bid, strategy, currency, shared budget, portfolio, network, location, language, negative, asset, URL, feed, and status mapping.
Decide whether conversion goals are imported or created separately and verify UET and campaign-level scope.
Choose one-time or recurring import and document overwrite, deletion, paused-source, and removed-item behavior.

After importing and before launch

Review import history, warnings, skipped items, unsupported fields, duplicate names, disapprovals, and diagnostics.
Verify destination account, campaign type, targeting, pages, products, budgets, bids, status, UET, goals, values, currency, and future automation.
Test representative valid and invalid paths and reconcile to the source system.
Obtain explicit launch approval for the exact destination state and retain rollback evidence.

The bottom line on setting up a Microsoft Ads import from Google Ads

A reliable Microsoft Ads import setup is a controlled translation: define source and destination, choose scope, verify account and currency, map spend and targeting, handle goals and UET separately, choose schedule and overwrite rules, preserve before-state evidence, complete post-import QA, and launch only the approved destination configuration.

Do not call an import ready because the wizard completed, entities were created, or clicks appeared. Readiness means the destination account, mappings, budgets, goals, pages, feeds, status, owners, schedule, and proof are understood. adz.so provides educational advertising guidance and does not administer accounts, approve imports, validate legal or privacy decisions, guarantee delivery, or promise performance.

Sources and related reading

The platform details and links above were checked against Microsoft Advertising documentation on 2026-08-15. Import mappings, campaign eligibility, goal behavior, feed handling, scheduling, overwrite behavior, account interfaces, and policy requirements can change; verify the live source and destination accounts and current official documentation before applying an import.