Moving Google Ads campaigns into Microsoft Advertising can save setup time, but an import is not a guarantee of parity. This guide shows how to compare keywords, match types, negatives, targeting, tracking, budgets, bids, and editorial status so you can estimate the effort and risk of an import before spending against it.
Overview
Microsoft Advertising campaign import is best treated as a controlled migration, not a one-click copy. The source campaign may contain settings that do not translate exactly, and a setting that appears equivalent can behave differently after import. Keyword management therefore has two jobs: transfer the campaign structure and verify that the transferred campaign still represents the intended search strategy.
Start by choosing the Google Ads campaigns that are suitable for reuse. Mature campaigns with clean conversion tracking, current landing pages, and an understandable negative keyword strategy are generally easier to validate than campaigns that already contain duplicated ad groups, old URLs, or unresolved tracking issues. Do not use an import to conceal structural problems. If the source campaign needs a major cleanup, document and fix those issues before treating it as the migration baseline.
A useful parity review compares the source and destination across six areas:
- Keywords: names, status, match type, destination URL, and bid settings.
- Ad groups and ads: grouping, responsive search ad assets, final URLs, and editorial status.
- Targeting: locations, languages, devices, audiences, networks, and exclusions.
- Economics: budgets, bid strategy, keyword bids, and conversion goals.
- Measurement: UTM parameters, auto-tagging choices, UET tracking, conversion actions, and URL redirects.
- Governance: naming conventions, labels, ownership, review dates, and change history.
Platform interfaces and supported features can change. Confirm the available import options, match-type behavior, bidding controls, tracking requirements, and editorial rules in the destination account before launch.
How to estimate the import and QA effort
Estimate the work by counting objects and assigning a review requirement to each one. A simple planning formula is:
Total QA effort = campaign review + ad group review + keyword review + tracking review + targeting review + launch monitoring.
This is not a cost forecast or a platform benchmark. It is a repeatable way to decide whether an import can be reviewed in one focused session or needs a staged migration.
- Count the campaigns. Separate search, shopping, audience, and other campaign types because their settings and import behavior may differ.
- Count ad groups and keywords. A campaign with many ad groups or a large keyword list needs sampling plus exception checks, not just a visual scan.
- Count special settings. Add review time for location exclusions, audience lists, shared budgets, automated rules, scripts, schedules, and network controls.
- Score tracking complexity. A single consistent tracking template is simpler than multiple landing-page systems, redirects, dynamic parameters, or separate conversion definitions.
- Reserve post-launch review. The import is incomplete until ads are approved, URLs resolve, spend is visible, and conversions are being recorded as expected.
For prioritization, use a three-level risk score. Low-risk imports have stable naming, limited targeting variations, consistent URLs, and a small number of bid or conversion settings. Medium-risk imports contain several locations, audiences, or tracking templates. High-risk imports include substantial broad-match coverage, complex negatives, shared budgets, multiple conversion actions, or bid strategies that require destination-platform confirmation.
This estimate is more useful than judging the migration by keyword count alone. One hundred keywords with clean structure may be easier to validate than twenty keywords spread across unusual targeting and tracking combinations.
Inputs and assumptions for a safe parity check
Prepare a source export or working sheet before importing. Record the campaign and ad group names, keyword text, match type, status, final URL, tracking template, location settings, negative keywords, audiences, budget, bid strategy, and conversion goal. Preserve the date of the export so later differences can be explained.
| Area | What to compare | Common decision |
|---|---|---|
| Match types | Keyword syntax, destination behavior, and available controls | Reconfirm the intended level of query coverage rather than assuming identical behavior |
| Negatives | Campaign and ad group negatives, lists, spelling variants, and conflicts | Rebuild exclusions where needed and check that valuable queries are not blocked |
| Locations | Included areas, exclusions, presence or interest settings, and radius targeting | Match the business service area and verify the destination options |
| Budgets and bids | Daily budgets, shared budgets, bid strategy, and keyword bids | Use conservative launch controls until destination performance is understood |
| Tracking | UTM parameters, final URLs, redirects, UET, and conversion actions | Test every key path before enabling material spend |
| Editorial status | Disapprovals, limited eligibility, missing assets, and policy review | Resolve destination-specific issues before comparing performance |
Pay particular attention to negative keywords. Importing positive keywords without importing their campaign-level and ad-group-level negatives can broaden traffic in ways that are difficult to detect from aggregate reporting. Conversely, a negative list copied without review can suppress relevant commercial intent keywords. Check conflicts, close variants, brand terms, competitor terms, and informational queries against the actual paid search strategy.
Tracking deserves its own test plan. Use a consistent UTM taxonomy for source, medium, campaign, content, and term where those fields are part of your reporting design. A tracking URL builder can reduce manual errors, but it does not replace a click test. Confirm that parameters survive redirects, that landing pages load, and that analytics and Microsoft Advertising reporting attribute visits and conversions in a way your team can interpret. See the UTM Taxonomy Playbook for a broader governance process.
Worked examples
Example 1: Small, clean search campaign
Suppose a campaign has three ad groups, 45 keywords, one location, a single conversion goal, and consistent final URLs. The import may be operationally simple, but the review still needs to confirm match types, negatives, ad approval, UET coverage, and budget settings. A practical workflow is to import into a paused or controlled state, compare the source sheet with the destination, test URLs and conversions, then activate only after the exceptions are documented.
Example 2: Multi-market campaign with separate location logic
Now consider six campaigns covering different regions, each with location exclusions, localized landing pages, and separate budgets. Keyword transfer is only one part of the decision. The main risks are location interpretation, URL-message match, budget allocation, and reporting consistency. Review each campaign independently rather than assuming that a successful import in one region validates all six. Launch the clearest region first, use its findings to refine the checklist, and then repeat the review for the remaining markets.
Example 3: Automated bidding and extensive negatives
A campaign using automated bidding, shared budgets, audience signals, and a large negative keyword library requires the most caution. Do not assume that a source bid strategy will have the same inputs, eligibility, or learning conditions in the destination account. Record the intended goal, conversion definition, target, budget, and guardrails. Then decide whether to begin with a less automated control while conversion tracking is validated. Preserve the negative library, but inspect it for conflicts and outdated exclusions before launch.
After each example, compare destination performance with the source campaign only after accounting for differences in traffic volume, conversion lag, eligibility, targeting, and launch timing. A cost-per-click or conversion-rate difference is not automatically a migration error; it is a reason to investigate the underlying settings and query mix.
When to recalculate and repeat the review
Run the parity checklist after every import or scheduled sync. Repeat it before increasing budgets, expanding locations, adding new keyword clusters, changing match-type strategy, or moving to a new bid strategy. A monthly comparison with the Google Ads source campaign can reveal drift in search terms, negatives, disapprovals, landing-page performance, and conversion tracking.
Refresh this process quarterly and whenever either platform changes interface labels, import behavior, match-type controls, UET or conversion requirements, editorial workflows, or supported bidding features. Also recalculate the effort when pricing inputs, internal budgets, or performance benchmarks move; a campaign that was acceptable at a small test budget may need stricter controls before expansion.
Use this final action list for the next migration:
- Export the source settings and freeze a dated baseline.
- Import a limited campaign set before duplicating the full account.
- Compare keywords, match types, negatives, URLs, targeting, budgets, bids, and audiences.
- Test UET, conversion actions, UTMs, redirects, and landing-page message match.
- Resolve editorial issues and document every intentional difference.
- Launch with controlled spend and review search terms and conversions promptly.
- Repeat the checklist monthly and before any material budget or market expansion.
For related checks on structure and wasted spend, use the PPC Audit Checklist, and consult the keyword match types guide when documenting differences between platforms.