Best Microsoft Ads Import from Google Ads Settings

The best Microsoft Ads import from Google Ads settings make the source account, destination account, campaign scope, currency, budgets, bids, goals, targeting, status behavior, and schedule explicit before anything is synchronized. Use a customized or advanced import when the defaults could alter spending or targeting, and treat the first run as a migration that requires post-import review—not as proof that the two platforms are identical.

Microsoft's current import guidance supports quick, customized, and advanced flows. It says an import can adjust bids, bid strategies, budgets, entity statuses, UET associations, and other items; it also provides an Import schedule & history view for logs. This article is educational setup guidance, not a guarantee that every Google Ads entity or setting will map to Microsoft Advertising.

What should you decide before importing Google Ads into Microsoft Ads?

Write the import contract before connecting the accounts:

Source: which Google Ads manager, account, campaigns, ad groups, products, feeds, goals, and statuses may be read.
Destination: which Microsoft Advertising account, currency, time zone, store, website, UET tag, and owner will receive the data.
Scope: one-time migration or recurring synchronization, selected entities, status treatment, deletion behavior, and schedule.
Transformations: bid, budget, currency, network, location, language, demographic, negative-keyword, ad, feed, and conversion-goal mappings.
Approval: spending boundary, launch status, QA owner, rollback or pause procedure, and evidence required before serving.

Do not treat an import as a copy-and-paste operation. The source and destination have different campaign types, minimums, networks, targeting options, conversion definitions, account currencies, and reporting. A clean import log can coexist with a destination campaign that targets the wrong market or optimizes toward no usable goal.

Choose one source account and one destination account where possible

Microsoft recommends importing a single Google Ads account into a single Microsoft Advertising account. Mapping several sources into one destination increases the chance of account-level keyword limits, naming collisions, mixed ownership, duplicated goals, conflicting budgets, and unclear reporting.

If the business truly needs multiple accounts, create a mapping table before the import. Include source account, destination account, currency, time zone, domain, market, Merchant Center store, UET tag, owner, and import name. Do not let an auto-selected destination become the authority for a client, brand, or regional budget without review.

Should you use Quick, Customized, or Advanced import?

Microsoft's current import flow offers a choice between speed and control. The appropriate option depends on whether the source configuration is already approved for Microsoft Advertising or whether the destination needs deliberate changes.

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

Quick import uses Microsoft's default import settings. It can be appropriate when the source account is small, the destination is prepared, budgets and statuses are allowed to change according to the defaults, and a named owner will review the result before campaigns serve.

Quick does not mean consequence-free. Confirm the destination account, currency, budget authority, UET readiness, campaign status, and post-import QA path before starting. If the source includes sensitive locations, active budgets, automated bids, Shopping campaigns, or conversion goals, prefer a customized or advanced review.

Use Customized import to control common changes

Customized import lets the owner adjust settings such as budgets, bids, bid strategies, entity status, and schedule before the import runs. Use it when the source structure is useful but the Microsoft account needs different spend, market, or delivery boundaries.

Record each override and its reason. A budget conversion, pause rule, bid adjustment, or status choice is part of the destination design. Do not hide a material transformation inside an import wizard that another owner cannot reproduce.

Use Advanced import for entity and mapping control

Microsoft's advanced flow allows selection of campaigns and ad groups, item-level import choices, bid and budget adjustments, bid-strategy settings, and UET associations. Use it when importing only a subset, excluding unsupported items, mapping goals, or controlling the status and deletion behavior is necessary.

The advanced flow is not a substitute for post-import validation. It gives you more choices before import; it does not prove that a destination ad, location, negative keyword, product, goal, or final URL behaves as intended.

Which account and currency settings should you verify?

Confirm the destination account and time zone

Check the Microsoft Advertising account number, manager relationship, business, domain, market, billing owner, time zone, and account status before authorizing import. Account time zone affects reporting and campaign behavior; record it alongside the source account's reporting time.

Do not import several markets into one destination simply because their Google campaigns are under one manager account. Separate accounts may be necessary when currency, billing, legal entity, access, or reporting ownership differs.

Handle currency differences explicitly

Microsoft's currency documentation says an account's currency is selected at setup and cannot be changed later. When Google Ads and Microsoft Advertising currencies do not match, the import offers choices to convert currency data or opt out and adjust bids and budgets manually.

Before choosing conversion, define the exchange-rate interpretation and the owner who approves the resulting bid and budget values. A numeric budget that looks unchanged may represent a different authorization in the destination currency. Preserve source and destination values in the import record.

If the destination account has the wrong currency, do not use import settings to disguise the problem. Microsoft directs advertisers toward a new account and campaign migration. Treat that as a separate account and billing project with its own QA.

Confirm Merchant Center store mapping for Shopping

Microsoft says Google Shopping campaigns require a Microsoft Merchant Center store. The Shopping import documentation describes mapping an existing store, importing a Google Merchant Center store, or creating a draft store.

Check store name, domain, markets, catalog, feed, currency, product availability, approval, and campaign association. A draft store is not an active Shopping destination until its setup is completed. Do not enable imported Shopping campaigns before the product data and store status support the intended market.

Which import settings can change spend?

Budget and bid transformations deserve explicit approval because a destination import can make an otherwise paused or low-spend campaign eligible to use a different amount or strategy.

Review bid and budget conversion

Microsoft says its minimum bid and budget requirements can differ from Google Ads. During import, Microsoft may raise values that are too low to meet its minimums unless the owner opts out; campaigns below the applicable minimum may not import. Record the source value, destination value, currency, adjustment, minimum warning, and approval.

Do not assume that copying a Google bid produces the same auction position or cost in Microsoft Advertising. Check campaign type, network, market, device, competition, match types, bid strategy, maximum CPC, and conversion signal. A translated bid is an input, not a performance prediction.

Review strategy eligibility and conversion prerequisites

If an imported campaign uses a conversion-dependent strategy but the destination has no usable conversion goal, Microsoft may convert it to a strategy that does not require conversion tracking, such as Maximize clicks for certain cases. The destination can then behave differently from the source while appearing structurally similar.

Before importing an automated strategy, verify UET, active conversion goals, inclusion in “Conversions,” campaign-level goal selection, values, currency, and consent. Use the Microsoft conversion tracking settings guide to review the destination measurement path after import.

Treat shared budgets as a destination decision

Review whether the source budget is campaign-specific or shared, which campaigns belong to it, and whether that grouping makes sense in Microsoft Advertising. A shared budget can redistribute money among campaigns that do not share the same market, objective, target, capacity, or owner.

Keep a destination budget map. Include source budget name, source campaigns, destination budget, destination campaigns, currency, daily or lifetime behavior, and the owner who approves allocation. Do not let an import quietly join an existing shared budget without checking its other members.

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

Review network and campaign-type mapping

Microsoft documents different network behavior and campaign types. For example, source Search and Display settings may map to a Microsoft Search campaign rather than preserving the same network combination. Performance Max, Demand Gen, video, and other campaign types may map to different Microsoft formats or require destination-specific assets.

Read the import summary and the current Microsoft import mapping documentation for the source campaign type. Verify where ads can appear, what assets were created, which inventory is eligible, and whether the destination page and measurement support the new surface.

Review location targeting and expansion

Microsoft says unsupported Google location targets may be mapped to a supported parent location, such as a state, region, or province. If both the focused and expanded locations are unsupported, the target may not import. Location groups are not supported in the documented import behavior.

Inspect every destination location, radius, presence or interest interpretation, exclusion, and language. If a location target is unsupported, choose explicitly whether to opt out of expansion or pause campaigns with no supported location targets. A campaign that serves worldwide because a location target was skipped is not a successful import.

Review language and demographics

Microsoft maps supported Google campaign languages to its own supported list and may set ad-group languages to use campaign settings. Unsupported target languages can prevent a campaign from importing. Demographics also differ: Microsoft documents age and gender mappings but does not import every Google demographic category or unknown group in the same way.

Check language, ad copy, landing page, market, age and gender targeting, exclusions, and any applicable advertising restrictions. Do not infer that a missing demographic setting means no targeting exists; read the destination settings and import warnings.

Review negative keywords and match behavior

Microsoft states that it does not use broad-match negative keywords. A Google broad negative can be treated as a phrase-match negative on import, and negative keyword lists and associations can be merged or overwritten according to the import behavior.

Export the source negative lists, compare them with destination lists, identify duplicate names, and inspect account-, campaign-, and ad-group-level associations. Confirm that the resulting negatives do not block eligible service, product, brand, or market queries. Keep the destination-specific cleanup separate from the source import until the resulting lists have been reviewed.

Review ad formats, assets, and videos

Ads may be transformed into destination-supported formats. Microsoft notes that video files used in Google Ads Video campaigns cannot be imported because of YouTube terms limitations; the video must be uploaded separately for the destination campaign to serve.

Check headlines, descriptions, paths, final URLs, assets, images, videos, business names, prices, offers, policies, editorial status, and mobile landing pages. A campaign can import its text while missing the asset needed for delivery or retaining a claim that is not valid in the Microsoft market.

Review product feeds and page feeds

Shopping and dynamic or asset-based campaigns may use a Microsoft Merchant Center store, page feed, or destination-specific mapping. Confirm the product IDs, titles, prices, availability, feed markets, domains, landing pages, and approval state. An imported campaign without a valid feed or page feed is not ready to launch.

If a Google asset-based feed is converted to a Microsoft Dynamic Search Ads page feed, inspect feed names, items, campaign associations, and any legacy feed relationships. Do not assume that feed conversion preserves the same targeting or page selection logic.

How should conversion goals be handled during import?

Conversion goals are one of the highest-risk mappings because a campaign can appear complete while bidding toward no destination event or toward a different event than the source.

Decide whether to import goals or create them separately

Microsoft documents Google conversion-goal import as a feature that may not be available to every account. When the option is available, the import can bring over Google goal settings, but online goals still need a Microsoft UET tag to receive destination events. Existing Microsoft goals and UET tags are not automatically replaced by imported goals.

If the feature is unavailable or the source goal is not a reliable fit, create or repair the Microsoft goal after importing the campaigns. Record whether the destination goal is imported, recreated, mapped to an existing goal, or intentionally omitted.

Review supported goal types and attribution mappings

Microsoft says the imported conversion goals it supports are online, tag-based, destination-URL goals created in Google Ads, rather than every Google Analytics, SA360, hosted, Smart Goal, or custom-event configuration. It also notes that data-driven attribution can be imported as last-click attribution.

Do not call an imported goal equivalent without checking goal type, UET tag, destination condition, attribution, window, inclusion in “Conversions,” count, value, currency, and account or campaign scope. If the attribution or event type is transformed, annotate it and reset the performance baseline.

Check goal names and collisions

Microsoft notes that a Google goal with the same name as an existing Microsoft goal may not import unless the name is changed. Search the destination goal list before import, define the naming convention, and avoid making two goals with the same event but different labels.

After import, inspect which goals are included in the optimization column, which campaigns use campaign-level goals, and whether the bid strategy still requires a usable conversion signal. Use the destination conversion-tracking settings guide for the detailed QA path.

How should an import schedule and deletion behavior be set?

Choose one-time or recurring synchronization deliberately

Use a one-time import when the destination needs a controlled migration and separate Microsoft ownership. Use an automatic schedule only when Google Ads remains an approved source of truth and the owner understands which destination changes may be overwritten.

Microsoft's import flow lets an owner name the import, set a schedule, run it again, modify it, and review history. Record the import name, frequency, source, destination, entity scope, last run, next run, owner, and escalation path.

Decide whether removed source items should be deleted

Advanced import options can delete items removed from Google Ads. This is powerful and potentially destructive to a destination that has intentionally diverged. Choose the deletion setting only after deciding whether Microsoft is a mirror or an independently managed channel.

If deletion is enabled, define what happens to paused, archived, renamed, unsupported, or manually created destination entities. If deletion is disabled, define how stale items are found and reviewed. Do not let an import delete a Microsoft campaign, negative, goal, product, or asset without an owner-approved source-of-truth policy.

Check scheduled-import overwrite behavior

Microsoft warns that import runs can overwrite campaign data, pause or remove entities, rename items, and modify bids, budgets, and settings. A change made directly in Microsoft Advertising may not persist if the recurring source import restores the Google setting.

Maintain a conflict register: setting, source authority, destination owner, allowed override, overwrite behavior, and review method. Use Change history and Import schedule & history to identify whether a person, import, API, editor, rule, or portfolio made a change.

What should happen immediately after a Microsoft Ads import?

The first post-import review should be a destination readiness audit, not an optimization session.

Check import results and warnings

Microsoft's Import schedule & history view provides logs for newly added, updated, or unimported entities. Save the import summary, warnings, errors, skipped items, mapping decisions, update count, and change-history evidence. Separate a successful file transfer from a successful campaign setup.

Review campaign and ad-group counts, active and paused statuses, keywords, negative lists, budgets, bids, strategies, goals, locations, languages, devices, audiences, assets, products, feeds, final URLs, tracking templates, and policy status. Search all statuses so a missing active row is not mistaken for an absent entity.

Verify targeting before enabling delivery

Check location expansion, location exclusions, language, device adjustments, network, audiences, search partners, ad schedule, and market. A source location that was unsupported may have been mapped to a parent location or skipped, and a skipped location can broaden delivery beyond the intended market.

Open representative ads and final URLs on mobile and desktop. Confirm that the product or service, price, offer, availability, shipping or service area, form, phone, appointment, checkout, consent, and tracking parameters agree with the destination.

Verify budgets, bids, and status

Compare source and destination budget amounts in native currencies, budget type, shared membership, bid strategy, target, maximum CPC, bid adjustments, and active or paused state. Check whether Microsoft raised a value to meet a minimum or converted the strategy because tracking was unavailable.

Do not enable all imported campaigns at once merely because they imported. Start only within the approved delivery scope, confirm billing and policy readiness, and keep the rest paused when the destination owner needs more review.

Verify conversions and downstream records

Test UET, imported or recreated goals, “Conversions” inclusion, campaign-level goals, value, currency, transaction IDs, and the CRM or order system. If the destination does not yet have a trustworthy conversion path, do not leave a conversion-dependent bid strategy running as if it were optimized.

A practical Microsoft Ads import checklist

Before and after each import, capture:

Account map: source Google account, destination Microsoft account, manager, domain, market, currency, time zone, owner, and billing authority.
Scope: campaigns, ad groups, products, feeds, goals, statuses, languages, locations, networks, and negative lists selected.
Import mode: Quick, Customized, or Advanced; one-time or scheduled; import name; deletion behavior; and overrides.
Spend controls: source and destination budgets, currency conversion, minimum adjustments, bid strategy, targets, shared budgets, and status.
Mapping warnings: unsupported campaigns, locations, languages, demographics, networks, assets, videos, feeds, goals, and negative-keyword transformations.
Measurement: UET tag, goals, event or URL, attribution, window, count, value, currency, consent, and “Conversions” inclusion.
Destination QA: ads, assets, final URLs, product data, Merchant Center store, landing page, policy status, mobile path, and operations.
Evidence: import summary, error log, Import schedule & history, Change history, source export, destination export, and reviewer sign-off.
Launch decision: what can serve, what remains paused, the owner, the spending boundary, and the condition for rollback or correction.

If any mapping is uncertain, preserve the destination in a controlled status and report the evidence gap. Do not turn a missing mapping into a silent default.

Common Microsoft Ads import mistakes

Assuming Google settings transfer unchanged

Campaign types, networks, locations, languages, negatives, goals, budgets, bids, assets, and feeds can map differently. Import is a translation, not a byte-for-byte copy.

Running Quick import with live budget authority

Default options can be wrong for a destination currency, status, budget, goal, or market. Use the mode that gives the owner enough control and require post-import review.

Ignoring currency mismatch

An unchanged numeric bid in a different currency is not an unchanged spending decision. Review conversion, minimums, budgets, values, billing, and reporting.

Enabling imported campaigns before targeting QA

Unsupported locations may map to broader parents or be skipped. A campaign can serve outside its intended market if the destination is not reviewed first.

Assuming imported conversions are ready

Imported goal support is limited, may be unavailable, and still requires a Microsoft UET tag and destination validation. Check attribution, windows, inclusion, values, names, and source records.

Letting scheduled imports overwrite intentional Microsoft changes

If Google remains the source of truth, record the boundary. If Microsoft is independently managed, do not schedule a mirror that silently restores source settings.

Sharing several sources into one destination account

Multiple source accounts can create naming, limits, billing, currency, ownership, and reporting collisions. Keep account mappings explicit.

Treating the import log as performance QA

The log confirms what the import processed. It does not confirm that ads are eligible, locations are correct, UET fires, orders are reconciled, or the business can fulfill the traffic.

The bottom line for Microsoft Ads Google imports

Use Microsoft Ads imports to accelerate a controlled migration, not to bypass destination design. Choose the source and destination accounts, currency, time zone, campaign scope, budgets, bids, goals, targeting, negative behavior, feed mappings, status, schedule, and deletion policy before you run the import. Then validate every translated boundary in Microsoft Advertising and keep campaigns paused until the owner has evidence that delivery and measurement are ready.

For adjacent setup context, use the Microsoft Ads conversion tracking settings guide, Microsoft Ads budget settings guide, and Microsoft Ads bid strategy settings guide. Those pages cover destination controls; this page covers the risks of moving settings from Google Ads into them.