Your Microsoft Ads account spends every week, but qualified leads barely show up. If you run search on Google and Bing, the choice is adapt the existing Google Import or pay for a native Microsoft Ads build. An imported campaign is not automatically a bad campaign. Starting over is not automatically an improvement.

I used to vote for the rebuild by default. Fresh structure felt cleaner, and it was easier to sell than untangling someone else’s import. I was wrong often enough to change the rule. Now I want the diagnosis first: broken tracking, irrelevant searches, unsuitable budgets, or a structure that genuinely does not fit Microsoft. Only the last one makes a structural rebuild the obvious answer.

For an existing Microsoft advertiser whose campaigns spend without producing qualified leads, adaptation is my default winner. The native build has to earn its fee.

The contenders: repair the import or replace the structure

Option A: Adapt the existing Google Import campaigns. Keep the useful structure and Microsoft account history, then fix what does not fit. That means validating Microsoft measurement, correcting bids and budgets for lower Bing volume, tightening locations and networks, and rewriting the parts that need it. Keep the winners. Stop paying for the same mistakes.

Option B: Build new campaigns specifically for Microsoft Advertising. Create a fresh structure with Microsoft-specific settings, keyword groupings, budgets, and relevant platform controls. The old account data remains available, but the new campaigns have to establish their own performance. This is the right call when the existing structure cannot be patched into shape. Most of the time, it can.

I judge the choice on five axes: diagnostic evidence, continuity, channel controls, implementation risk, and structural fit. A cleaner-looking account is not one of them.

Two labeled filing trays comparing an adapted Google Import with a fresh Microsoft Ads build

Decision axisAdapt the Google ImportBuild native for Microsoft
Diagnostic evidenceUses existing Microsoft search-term, publisher, location, and conversion dataNeeds the same diagnosis; a fresh structure does not explain the old failure
ContinuityKeeps proven campaigns, negatives, and Microsoft performance historyLeaves old evidence available, but new campaigns must establish performance
Channel controlsAdds Microsoft-specific settings to a useful baseBuilds those settings in from the start
Effort and riskTargets changes in layers, making their effects easier to readAdds build work and risks changing too many variables together
Structural fitWins when the campaign blueprint still worksWins when the blueprint itself needs to change

1. Diagnostic evidence: prove the failure before choosing the fix

Check tracking against actual lead outcomes

Imported campaign structure does not prove that Microsoft measurement works. UET and conversion goals need their own setup and validation. If tracking is missing or broken, the account can report clicks and spend without recording the enquiries those clicks produce. Automated bidding also lacks the conversion feedback it needs.

I have seen more than one “failing” Bing account that was really an untracked account. Before approving either proposal:

  1. Validate the UET installation with UET Tag Helper.
  2. Check for partial installs and consent-banner blocks that can break tracking.
  3. Confirm that conversion goals match the actions that matter.
  4. Compare reported conversions with qualified leads and pipeline in the CRM.

There are two different failures here. If real leads exist but Microsoft does not record them, repair measurement. If the CRM confirms that qualified leads are missing too, the acquisition problem is real. Tracking can hide performance; fixing tracking cannot manufacture pipeline.

Separate bad traffic from a bad structure

Next, inspect the imported settings rather than assuming the keywords are guilty. Bid strategies and other settings can change during import. Check what each campaign actually runs now, especially when Microsoft conversion goals were not ready at import.

Locations and networks deserve the same suspicion. Unsupported locations can map to broader regions. Location options can include people interested in an area rather than physically in it. Search-partner settings can expose the account to traffic you did not intend to buy.

That combination can create the cheap-click feedback loop described here: weak traffic produces weak signals, and the account keeps buying more of it. My starting point is boring and specific: restrict delivery to Bing, AOL, and Yahoo owned-and-operated traffic, select people in the targeted locations, and review the publisher report after two weeks.

When searches look right but leads still fail, check the landing page and budget. Microsoft budgets need their own math, not a copy of Google’s allocation. Underfund the account and learning stalls. Overfund a broken import and you buy failure faster.

If a page converts on Google traffic but struggles on Microsoft traffic, investigate intent and publisher mix before declaring the offer broken. Neither adaptation nor a rebuild gets to skip this work. Choose the remedy after identifying the failure, not before.

2. Continuity: keep the evidence the account already paid for

Adaptation keeps the receipts, provided you know which receipts you actually have. The Google structure may bring useful keywords, ads, and negatives. The Microsoft account then accumulates its own search terms and performance history. Importing a campaign does not transfer Google’s historical performance into Microsoft.

That distinction matters. I am not defending an import because it once worked somewhere else. I am defending the parts that have evidence behind them, especially qualified pipeline from the Microsoft account itself.

I start by turning off Google auto-import so the next sync does not overwrite Microsoft-specific fixes. Then I separate brand from generic and keep what proves itself.

For a fresh or staged import, one useful pattern is to import paused and enable brand plus the strongest generic campaigns first. Google’s auction settings are not a reason to switch everything on unchanged in Microsoft.

A rebuild does not erase the old reports. It does, however, move delivery into new campaigns whose performance you still have to establish. That is a cost worth paying when the structure is wrong, not a ritual to perform whenever a new manager arrives.

Pause what wastes money; do not delete useful campaigns just to make the takeover look busy. Let the publisher report and CRM tell you what deserves to survive.

3. Channel controls: break the mirror without smashing the account

This is where adaptation stops being a copy-and-paste exercise. A useful keyword base can stay. Google’s settings do not get diplomatic immunity.

My post-import QA follows this order:

  1. Budgets and bid strategies.
  2. Networks and location options.
  3. Conversion goals and tracking templates.
  4. Extensions and negatives.
  5. Microsoft-specific opportunities that fit the business.

Networks come first among those channel-specific decisions. I keep search on Bing, AOL, and Yahoo owned-and-operated traffic until the account proves it can handle syndicated partners without the junk loop returning. A native build needs the same judgment. “Built for Microsoft” is not a network-quality policy.

For relevant advertisers, LinkedIn profile targeting through search bid adjustments offers another control: company, industry, and job function. Those controls belong in the plan when they connect to the customers who actually buy, not because the proposal needs a platform-specific bullet point.

Budgets also need to match Microsoft’s volume. Copying Google’s allocation assumes the same opportunity exists in both auctions. It does not make the account more ambitious. It makes the budget less considered.

I wrote up the agency version of this approach in Import Google Ads to Microsoft Ads. Then Break the Mirror.. The principle is simple: keep the useful base and rebuild the settings around Microsoft’s auction. A native campaign can bake those controls in from day one, but adaptation can apply them without replacing the whole structure.

4. Effort and risk: change one layer at a time

Adaptation can mean days of QA. A rebuild can mean weeks of construction followed by much of the same QA. Both still need UET, goals, templates, extensions, and sensible delivery settings. New campaigns do not arrive pre-diagnosed.

The bigger cost is losing the ability to explain the result. Change structure, bids, budgets, networks, and ads in the same week, and you may improve the account without knowing why. Or make it worse without knowing which lever to reverse. That is an expensive way to discover that the network setting was the problem all along.

I adapt in layers:

  1. Repair tracking and confirm the goals.
  2. Correct networks and locations.
  3. Adjust bids and budgets.
  4. Change ads and other elements that still need work.

I detailed that sequence in Why Microsoft Ads Spends Without Converting: The Google Import Problem.

This is not an argument for leaving obvious waste running while someone completes a tidy experiment. It is an argument against bundling every possible change into one grand reset and calling the result strategy.

A native build earns the extra work when it removes a structural constraint. Otherwise, adaptation is the more disciplined choice: fewer moving parts, clearer evidence, less rebuilding for the sake of rebuilding. Change one layer, read the result, then choose the next move.

5. Structural fit: the one axis that can justify a native build

Adapt when the blueprint still fits

Adaptation wins when the underlying offer and campaign structure are healthy. If brand and a few generic themes carry the useful volume, and the failure sits in Microsoft settings, keep the import.

That covers most takeovers I see: repair UET, reset bids for Microsoft’s auction, right-size budgets, restrict networks, correct the location option, and add relevant Microsoft controls. Keep the negatives, useful ads, and Microsoft search-term evidence.

A healthy Google account is a useful starting point, not proof that every imported campaign belongs on Microsoft. I still want evidence from the channel being fixed.

Keep a working blueprint when the fault sits in the settings. Patching settings is not an inferior service just because rebuilding produces a longer task list.

Build selectively when the blueprint itself fails

A native build wins when the structure needs to change materially. Think of one ad group holding 200 keywords with no coherent theme, or budgets scattered across ten micro-campaigns that cannot support useful learning at Bing volume.

Other inherited problems, such as negatives fighting the keywords beside them or unsuitable device adjustments, still need correction. They do not automatically justify replacing every campaign.

Even when structure is the problem, I rarely want a full reset. I want the broken part rebuilt: perhaps one prospecting campaign with tight themes, Microsoft budgets, and owned-network limits, while proven brand and generic campaigns keep running on the adapted base.

This is who should choose the losing option in this comparison: an advertiser whose existing structure cannot support the channel, not merely one whose current results are poor. A selective rebuild earns its fee. A full reset rarely does.

My verdict: adaptation wins unless the structure proves otherwise

For an existing Microsoft Ads customer spending without qualified leads, adaptation wins and a full rebuild loses. It preserves useful campaigns and evidence while targeting the failures that actually explain the waste. A native build wins only when a materially different structure is necessary, and even then I would rebuild selectively.

If the manager cannot name the failure, show the evidence, and explain why the proposed change addresses it, do not approve the rebuild.

The evidence your manager should supply

Ask for this before paying for a new structure:

  • UET validation: Tag Helper checks across the relevant page templates, plus conversion rules that match the real enquiry action.
  • Publisher and network split: the last 30 days of owned-and-operated versus syndicated-partner performance, with exclusions identified.
  • Search-term split: brand versus generic, irrelevant themes, and the negatives needed to stop them.
  • Location proof: current targeting options and any broader-region spillover that needs correction.
  • Bid and budget math: the strategies actually running after import and budgets sized for Microsoft’s opportunity.
  • Pipeline, not clicks: qualified leads and pipeline by campaign from the CRM.

No evidence pack, no rebuild fee. That is the brief to hand the strategist.

What I expect from a groas takeover

This is the work I want from a takeover, and it is how groas approaches one: a named strategist sets the direction and guardrails, while autonomous execution handles the ongoing campaign work. Actions are logged with reasoning you can inspect. The point is not another dashboard full of recommendations for you to implement.

Rather than billing more because the account spends more, groas works for one fixed monthly fee, month to month. The takeover starts with diagnosis, not a promised result or a mandatory rebuild.

No honest proposal can tell you what the account will deliver before tracking, publisher mix, budgets, and pipeline are understood. Demand the audit in writing, keep the winners, fix the fit first, and rebuild only the part that proves it cannot be fixed. Book a consultation and bring this brief with you.