Google CSS Migration: How to Switch CSS Partners Safely

Google CSS migration is the process of switching an existing Merchant Center account from one Comparison Shopping Service to another. When it is planned correctly, the merchant can keep the same Merchant Center and Google Ads accounts instead of rebuilding the entire Shopping setup.

The administrative switch itself is straightforward. The real work is checking account ownership, target countries, Merchant Center structure, campaign surfaces and user access before the request is approved. This guide explains the full process and the controls that reduce migration risk.

Agencies building their own service should also review how to become a Google CSS Partner, the current Google CSS requirements and our White Label CSS pricing.

What is a Google CSS migration?

A CSS migration changes the Comparison Shopping Service associated with a Merchant Center account. The new CSS initiates the switch in CSS Center, and an administrator of the Merchant Center account approves or declines it.

Google confirms that a Merchant Center account can be associated with only one CSS at a time. The account can be linked directly to the new CSS or placed under a multi-client account associated with that CSS, depending on the agreed operating model.

What changes and what stays the same?

The safest migration normally retains the existing Merchant Center account. This avoids an unnecessary recreation of feeds, links and campaign connections. However, the exact result depends on whether the account remains standalone or is moved under a new CSS multi-client account.

Keeping the same accounts does not remove the need for monitoring. A change in CSS coverage, account access or eligible advertising surfaces can still affect delivery even when campaigns themselves remain untouched.

What should be checked before migration?

A migration should begin with an account audit, not with the switch request. The following checks determine whether the current Merchant Center can move directly or whether a split structure is needed.

Merchant Center ownership and administration

Confirm the Merchant Center account ID and make sure at least one active person on the merchant’s side has administrator access. Google sends the switch request to Merchant Center administrators, and the process cannot proceed without approval.

Current account structure

Establish whether the account is standalone, a sub-account of an MCA, a primary CSS MCA or a marketplace-related account. Google lists several structures that cannot be switched in the standard way, including a primary CSS MCA and certain marketplace MCA sub-accounts.

Target countries

Separate countries covered by the CSS programme from markets outside it. The migration plan must preserve product distribution in both groups. Do not assume that a provider operating in European CSS markets automatically supports Shopping ads and free listings everywhere else.

Advertising surfaces

Confirm that the new CSS supports the surfaces used by the merchant, including dynamic remarketing and placements beyond Google’s general search results. If it is not opted in for those surfaces, product delivery can become more limited after the switch.

Baseline performance

Record spend, impressions, clicks, conversions, revenue, product approval rate and campaign status before migration. A clear baseline makes it possible to distinguish migration issues from normal daily volatility.

Contract and communication

Check the current provider’s notice terms and tell all account stakeholders when approval is expected. The technical switch in Google does not automatically terminate a commercial agreement with the previous CSS.

Google CSS migration step by step

1. Choose the new CSS and account model. Agree whether the Merchant Center will be associated directly with the new CSS or placed under its MCA.
2. Complete the pre-migration audit. Verify the Merchant Center ID, administrators, target countries, campaign surfaces, account links and product status.
3. The new CSS initiates the switch. A CSS Center administrator adds the merchant using the existing Merchant Center account ID and submits the request.
4. The merchant receives the request. Merchant Center administrators are notified and can review the proposed association.
5. A Merchant Center admin approves the switch. The previous CSS is notified after approval. If the request is declined, the account remains with the current provider.
6. The grace period runs. Google applies a period of up to 14 days. The merchant can reverse the decision during this time, while the previous CSS can waive or shorten the period.
7. The account moves to the new CSS. The status changes from pending and approved to completed in CSS Center.
8. Run post-migration checks. Verify association, access, products, campaign delivery, target countries, advertising surfaces and reporting.

How long does a CSS migration take?

The standard Google process can take up to 14 days after the Merchant Center administrator approves the request. The previous CSS can waive or shorten the grace period, so the actual time may be shorter.

Approval speed matters. The grace period starts only after a Merchant Center administrator accepts the request, so an unanswered notification is a common source of delay.

How to migrate without disrupting Shopping campaigns

No provider should promise that every migration is completely risk-free. Continuity is protected by retaining the existing Merchant Center and Google Ads setup, then controlling the settings that can actually change.

• Do not create a new Merchant Center unnecessarily. Use Google’s account-switch process when the current account is eligible to move.
• Do not rebuild Google Ads campaigns. Google Ads accounts do not need a CSS switch; preserve their existing Merchant Center connection.
• Freeze unrelated major changes. Avoid simultaneous feed restructures, campaign rebuilds or tracking migrations that would make diagnosis harder.
• Check product processing before and after. Compare approved, limited and disapproved item counts.
• Monitor the first hours and days. Review impressions, spend, campaign status and conversion tracking by country and campaign type.
• Keep administrators active. Access problems can cause switch failure or leave teams unable to troubleshoot the account.
• Document the rollback window. The merchant can reverse the decision during the grace period, before the switch becomes final.

What about international Merchant Center accounts?

The CSS programme covers Austria, Belgium, Czech Republic, Denmark, Finland, France, Germany, Greece, Hungary, Ireland, Italy, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Spain, Sweden, Switzerland and the United Kingdom.

If the Merchant Center also contains product data for countries outside the programme, verify how the new provider handles those markets. Google warns that ads and free listings can stop serving there if the new CSS has not chosen to place them outside CSS programme countries.

Two common account structures

The right structure depends on target countries, feeds, campaign architecture and the provider’s participation settings. Make this decision before initiating the switch, not after traffic changes.

How migration works with White Label CSS

In a White Label model, the agency owns the client relationship while the infrastructure provider supports the CSS operation. The merchant still controls its Merchant Center account and must approve the switch through an administrator.

Responsibilities of the agency

• select and qualify the client accounts to migrate;
• obtain Merchant Center IDs and confirm active administrators;
• explain the request and grace period to each client;
• coordinate the approval date;
• monitor Google Ads and Merchant Center after completion;
• provide client-facing support under its own brand.

Responsibilities of the infrastructure provider

• verify the intended CSS and MCA structure;
• initiate eligible switch requests in CSS Center;
• monitor pending, approved and completed statuses;
• support access and account-association issues;
• help verify the completed migration.

The agency’s branded comparison domain and the Merchant Center switch are connected parts of the same service, but they are separate technical tasks. Domain or subdomain configuration should be ready before client rollout so branding and account migration do not become competing dependencies.

Post-migration checklist

1. Confirm the new CSS association. Check the Comparison Shopping Services section in Merchant Center and the completed status in CSS Center.
2. Verify Merchant Center access. Make sure the merchant, agency and relevant MCA users have the intended permissions.
3. Review product status. Compare approved, limited and disapproved items with the pre-migration baseline.
4. Check account links. Confirm that the existing Google Ads connection is active.
5. Review campaign delivery. Monitor impressions, clicks, spend and conversion value across Shopping and Performance Max campaigns.
6. Segment by country. Pay special attention to markets outside the CSS programme.
7. Check additional surfaces. Verify dynamic remarketing and placements beyond general search where applicable.
8. Validate conversion tracking. Confirm that GA4, Google Ads conversions and revenue reporting continue to populate normally.
9. Check visible attribution. Verify that the intended CSS or White Label brand appears when eligible ads are served.
10. Record completion. Save the completion date, final structure and verification results for client support.

For the switch workflow itself, see Google’s official documentation on switching merchant accounts between CSS providers and working with Comparison Shopping Services.

Frequently asked questions

Do Google Ads campaigns need to be migrated?

No. Google states that Google Ads accounts do not need to be switched. The Merchant Center association determines which CSS the connected Shopping campaigns belong to.

Will campaign history be lost?

Retaining the existing Merchant Center and Google Ads accounts avoids rebuilding campaigns and preserves their existing account history. Performance should still be monitored after the association changes.

How long does a Google CSS migration take?

After approval by a Merchant Center administrator, the standard grace period can last up to 14 days. The previous CSS may waive or shorten it.

Who initiates a CSS switch?

The new CSS initiates the request in CSS Center using the existing Merchant Center account ID. A Merchant Center administrator then approves or declines it.

Can the migration be cancelled?

The merchant can reverse the decision during the grace period and remain with the previous CSS. After the grace period and completed switch, the change is final within that migration request.

Can only part of a Merchant Center account be switched?

No. Google states that partial CSS switching is not allowed. Where different market coverage is required, separate Merchant Center accounts may be needed.

Does the Merchant Center admin need to approve the migration?

Yes. Administrators receive the request and must approve it before the grace period begins.

Can account access change after migration?

Yes. If a sub-account leaves one MCA and joins another structure, MCA-level access can change. Direct Merchant Center users remain on the account, but administrators should be checked before and after the switch.

Can migration affect dynamic remarketing?

Yes. If the new CSS is not opted in to dynamic remarketing and surfaces beyond general search, products may stop appearing on those additional surfaces.

Can migration affect countries outside Europe?

Yes. Ads and free listings in countries outside the CSS programme may stop if the new CSS does not support placement there. International coverage should be mapped before approval.