By Waqas Mehboob · Google Shopping & Product Feed Specialist · 17 October 2026
Moving a Shopify product feed between the Google & YouTube channel, Simprosys, DataFeedWatch or another source is a data-mapping project. The aim is to understand what is live, preserve the intended product identities and validate the replacement before retiring the old connection.
This checklist is a practical review framework. Exact settings depend on your apps, Merchant Center account and target markets. Keeping the same IDs does not guarantee unchanged rankings, approval, ad delivery or performance.
Start with the current setup
1. Record every source and destination. Make a simple inventory of the Shopify store, domains, Merchant Center accounts, feed tools and selling markets. Note which source currently supplies each channel. Include automatically discovered products and supplemental sources in the review so you can explain overlapping or missing records.
2. Save a baseline before changing anything. Export a dated product sample and record item counts, diagnostics, active countries and the last successful update. Save the existing rule logic and mapping decisions where your tool allows it. Include a few products with discounts, stock changes and several variants.
Check identity before rebuilding rules
3. Compare the old and new item IDs. Google requires a unique ID for each product and says to keep that ID unchanged when updating data. Compare the exact IDs the new source will submit against the current records. Do not assume that two apps build the same ID from a Shopify product or variant. Google product data specification.
4. Trace a complete variant family. Choose one product with several sizes or colors. Check that each variant has its own record and that related variants use the intended group. Open the submitted links and check the selected variant against the feed values. Google documents how item group ID and variant-identifying attributes work together.
Rebuild the intended output
5. Recreate rules from their purpose. List what each rule is meant to do: add the brand to a title, separate stock groups, map a category or assign a custom label. Test the result for representative products instead of copying a rule name and assuming the behavior is identical. Keep a short rule register with the input, condition, output and example item.
6. Check each selling market separately. For every intended country, inspect the destination URL, price, currency, availability and shipping settings. Test a normal product and a variant from that market. A correct default-market page does not establish that every localized URL is correct.
7. Review supplemental sources and attribute precedence. A supplemental source enriches existing product information; it is not a standalone source for adding or removing products. Check how it will match the new primary source, and which rules should determine the final values. See Google’s guidance on supplemental product data sources and attribute rules.
Validate the transition
8. Test the replacement before retiring the old setup. Use a limited product set or other controlled validation method where your tool and account support it. Compare exported or processed output with the baseline. Agree the cutover and rollback steps before making changes to live sources. Avoid an unplanned period when multiple sources compete to define the same product.
9. Check campaign and tracking dependencies. Review whether campaign filters, product groups or custom labels depend on values being changed. If Meta Catalog is also moving, compare the event product IDs with the catalog IDs as a separate check. A feed import finishing successfully does not establish that advertising and tracking dependencies still match.
10. Monitor the next updates. Record the first successful processing result, then inspect the next agreed update cycles. Compare counts and issue categories, and check recent price or stock changes on sample products. Keep the rollback criteria specific, such as an unexpected loss of an intended market or a material mapping mismatch.
What a useful handover contains
Keep a dated baseline, an old-to-new ID comparison, a rule register, market checks, sample product links, diagnostics findings and a change log. State what was tested, what remains unresolved and who owns future updates. These records make later troubleshooting easier.
Does keeping product IDs preserve Google Shopping performance?
Stable IDs are an important data requirement, but they are not a performance guarantee. A migration can also change attributes, eligibility, destinations or campaign segmentation. Review those dependencies and monitor the account after the transition rather than treating matching IDs as the only success criterion.
Can I use a supplemental source to replace the primary feed?
A supplemental source supports existing products. It cannot serve as a standalone source for adding or removing the catalog. Choose the source structure around the job it needs to do, then verify matching and final values.
Need help reviewing a Shopify feed migration?
Exultant Commerce provides DataFeedWatch and Shopify product feed support and Google Merchant Center setup and troubleshooting. Start by sharing your store URL, feed tools, target markets, catalog size and the reason for the migration.
For an example of how we document diagnostic outcomes and their limits, see the 22,000 item Merchant Center catalog case study. That case concerns disapproval cleanup; it is not presented as a feed-migration result.