Skip to main content

    Problem-Solution Hub

    Your migration broke your ads.
    Here's how we fix it.

    Platform migrations, agency transitions, and feed restructures cause predictable Google Ads failures. The good news: they follow patterns we have seen 50+ times. We know what breaks and how to fix it.

    The worst thing you can do after a migration is panic and start making random changes. Recovery requires a structured approach - stabilise first, diagnose second, rebuild third.

    Migration Types

    What kind of migration hit you?

    Each migration type creates different damage patterns. The recovery approach depends on understanding which type you are dealing with - and they often overlap.

    Platform Migration

    Magento → Shopify, WooCommerce → BigCommerce, Custom → Headless

    Common breaks:

    • URL structure changes
    • Feed breaks
    • Tracking gaps
    • Algorithm reset

    Agency Transition

    Firing previous agency, bringing in-house, switching to JudeLuxe

    Common breaks:

    • Learning phase disruption
    • Historical data gaps
    • Account structure chaos
    • Bid strategy resets

    Feed Infrastructure

    New PIM, feed tool migration, custom label restructure

    Common breaks:

    • Product ID changes
    • GTIN breaks
    • Category mapping
    • Attribute loss

    Warning Signs

    Symptoms of migration damage

    If you are seeing these after a recent migration, your Google Ads need structured recovery - not random optimisations.

    ROAS dropped 40%+ overnight

    Sudden drops correlate with migration events, not seasonal changes.

    Conversion tracking shows gaps

    Missing or duplicate conversions indicate tracking migration issues.

    Shopping campaigns showing 'limited' status

    Feed issues from migration are blocking products from serving.

    PMax performance collapsed

    Algorithm lost its learning from the previous platform's data.

    Branded search costs spiked

    Competitors bidding on your brand during visible weakness.

    Worked Example

    Fashion Brand - Magento to Shopify Plus Migration

    12-week recovery from 58% revenue drop

    Pre-Migration

    Baseline

    Revenue

    £185k/month

    ROAS

    4.2x

    Stable performance across 3,200 SKUs on Magento.

    Week 1 (Post-Migration)

    Crisis

    Revenue

    £78k/month (−58%)

    ROAS

    1.4x

    Product IDs changed during migration. Google treated every product as new - wiping conversion history, quality scores, and bid strategy learning. 40% of products disapproved due to missing GTINs in the new feed.

    Week 2-4 (Stabilisation)

    Recovering

    Revenue

    £112k/month (−39%)

    ROAS

    2.1x

    Fixed GTIN mapping, restored original product IDs via supplemental feed, rebuilt conversion tracking with Shopify's native tags. Paused all PMax campaigns to stop them bidding on broken data.

    Week 5-8 (Reconstruction)

    Rebuilding

    Revenue

    £168k/month (−9%)

    ROAS

    3.6x

    Rebuilt Shopping campaigns with Shopify's enhanced feed attributes. Restarted PMax with brand isolation. Implemented margin-based custom labels that Magento couldn't support.

    Week 9-12 (Optimisation)

    Exceeded

    Revenue

    £214k/month (+16%)

    ROAS

    4.8x

    Migration used as opportunity to implement POAS-based bidding. Shopify's superior feed capabilities enabled profit-weighted targets per SKU. Ended 16% above pre-migration baseline.

    Recovery Framework

    How do you recover Google Ads after migration?

    Migration recovery is not optimisation. It is reconstruction. Here is our structured approach.

    1. Stabilisation (Week 1-2) - Freeze changes, fix tracking, verify feed integrity.
    2. Diagnosis (Week 3-4) - Identify what broke and map to migration impacts.
    3. Reconstruction (Week 5-8) - Rebuild what was working. Recover before innovating.
    4. Optimisation (Week 9-12) - Implement better practices using migration as opportunity.

    Week 1-2

    Stabilisation

    Freeze non-essential changes. Fix tracking. Verify feed integrity. Establish new baselines.

    • Audit conversion tracking
    • Verify product IDs maintained
    • Baseline performance snapshot
    • Fix any broken feed attributes

    Week 3-4

    Diagnosis

    Identify what broke. Map performance changes to specific migration impacts.

    • Compare pre/post SKU performance
    • Isolate algorithm vs structural issues
    • Prioritise recovery opportunities
    • Quantify revenue impact per issue

    Week 5-8

    Reconstruction

    Rebuild what was working. Don't innovate yet - recover first.

    • Restore high-performing campaigns
    • Rebuild feed structure
    • Re-establish bid strategies
    • Resubmit product approvals

    Week 9-12

    Optimisation

    Now innovate. Use the migration as an opportunity to implement better practices.

    • Implement margin-based bidding
    • Restructure for new platform capabilities
    • Build new testing framework
    • Establish new commercial baselines

    Sector-Specific

    Migration risks by sector

    Each sector faces unique migration vulnerabilities. The recovery priority depends on what your industry values most.

    Fashion & Apparel

    Migration Risk

    Variant structure changes (colour/size) break product group reporting. Image URL changes cause policy violations. Seasonal products lose historical data mid-season.

    Recovery Priority

    Restore product ID continuity first, then rebuild variant-level bidding. Prioritise in-season products over archive items. Accept that out-of-season lines may need to rebuild from scratch next season.

    Beauty & Skincare

    Migration Risk

    Ingredient and safety attribute changes trigger Merchant Centre policy reviews. Subscription product data often fails to migrate cleanly, breaking recurring purchase tracking.

    Recovery Priority

    Fix policy violations before anything else - products can't sell if they're disapproved. Rebuild subscription tracking separately from one-time purchase tracking to restore LTV-based bidding.

    Home & Living

    Migration Risk

    Large catalogues (5,000+ SKUs) with complex category hierarchies lose custom label structures during migration. Shipping calculator changes affect free shipping threshold triggers.

    Recovery Priority

    Rebuild custom label taxonomy from scratch using the new platform's capabilities. This is usually better than trying to replicate the old structure - use migration as an upgrade opportunity.

    How long does Google Ads performance recovery take after a platform migration?

    TLDR: 4-phase recovery over 60-90 days: stabilise, diagnose, reconstruct, then optimise.

    A structured recovery follows four phases: Weeks 1-2 for stabilisation (freeze changes, fix tracking, verify feed integrity), Weeks 3-4 for diagnosis (map performance changes to specific migration impacts), Weeks 5-8 for reconstruction (rebuild what was working), and Weeks 9-12 for optimisation (innovate on the stable base). Most accounts recover to pre-migration levels within 60-90 days.

    Stabilisation phase:
    Weeks 1-2(JudeLuxe)
    Full recovery timeline:
    60-90 days(Client data)

    What causes Google Ads performance drops after a Shopify migration?

    TLDR: URL changes, feed breaks, tracking gaps, and algorithm resets - product ID changes are the worst offender.

    The most common causes are: URL structure changes that break product IDs and campaign history, feed breaks from new platform formatting, tracking gaps from incomplete GA4/GTM migration, and algorithm reset when bid strategies lose their learning data. Product ID changes are particularly damaging - they force Google to treat established products as new, losing all conversion history.

    Frequently Asked Questions

    Post-migration recovery

    Recently migrated and performance tanked?

    Book a recovery assessment. We will diagnose what broke, quantify the revenue impact, and give you a recovery timeline with clear milestones.

    Book Recovery Assessment

    We use cookies to improve your experience. Privacy Policy