Skip to content

How to switch feed manager without losing product IDs

A practical migration guide for product feeds: audit IDs, test in parallel, document rules and transition channel by channel.

J

Julia Villegas

· 8 min read · 389 views
Switch feed manager with ordered products and product ID labels

Switch feed manager with care: your product feed powers catalog ads, Shopping campaigns and dynamic product ads. If product IDs change, URLs break, or price and stock stop matching your store, ad platforms may treat existing items as new or problematic. This guide explains how to migrate methodically, test in parallel and reduce surprises without promising zero impact.

What it means to switch feed manager

A feed manager is the tool that receives your product catalog, cleans or transforms the data, and publishes a feed in the format required by each marketing channel. Your catalog may come from an ecommerce platform, a product file, or an existing feed. Channels such as Google, Meta, TikTok, Pinterest, Snapchat, Criteo or Microsoft Advertising then read a feed URL containing attributes such as product ID, title, price, availability, image link, product URL and category.

Switching feed manager is not just replacing one software tool with another. In practice, you are rebuilding three layers:

  1. Import: where products come from and which fields arrive.
  2. Normalization: which rules correct, enrich, filter or transform the data.
  3. Export: which feed is delivered to each channel and in what format.

The most sensitive part is usually the product ID. The ID is the identifier that the channel uses to recognize an item. If the same product changes from SKU-123-BLACK-UK to SKU-123 without a plan, a platform may treat it as a different product. That can affect diagnostics, approvals, history or campaign learning, although each platform handles changes in its own way.

Google’s product data specification explains that product data should describe the product accurately and match the landing page. For a migration, that makes product ID, link, price, availability and image more than technical details: they are the foundation of the transition.

Why product IDs matter so much

For beginners, think of the product ID as the passport number of an item inside an advertising platform. Titles can be optimized, prices can change, images can be refreshed and stock can go up or down. But the ID should stay stable for as long as the item is still the same product or variant.

A stable ID helps a channel understand that it is seeing an update to an existing product, not an entirely new item. This matters for Google Merchant Center, Shopping, Performance Max, Meta catalog ads, TikTok product feeds, Pinterest catalogs and other dynamic ad environments.

Example scenario

Imagine an online furniture store called “North House”. It sells this product:

Store field Value
SKU TABLE-OAK-120
Variant NATURAL
Market UK
Title Oak dining table 120 cm

The old feed exported the product ID as TABLE-OAK-120-NATURAL-UK. Inside the ecommerce back office, however, the team mostly sees TABLE-OAK-120. If the new feed manager uses the SKU directly as the ID, Google or Meta will receive TABLE-OAK-120 instead of TABLE-OAK-120-NATURAL-UK.

That may be technically valid, but it should not happen by accident. If you want continuity, first find out which ID each channel currently sees. Then either reproduce that logic or decide deliberately when and why to change it.

How to switch feed manager without losing product IDs

A migration should be a transition, not a sudden replacement. The goal is to build the new feed, compare it with the old one and only update each channel once the critical checks are complete.

1. Inventory your current feeds and channels

Before you change anything, list every active feed. One ecommerce catalog can power multiple feeds by country, language, channel, campaign, sale category or product set.

Channel Current URL Market/language Included products ID logic
Google Merchant Center Current feed URL UK / en Full catalog SKU + variant + market
Meta Ads Current feed URL UK / en In-stock products SKU + variant + market
Pinterest Current feed URL UK / en Home and decor SKU only

This table prevents two common mistakes: forgetting a secondary feed and assuming that every channel uses the same ID structure.

2. Export a sample from the old feed

Download a copy of the current feed before migrating. At minimum, save the ID, title, product URL, price, availability, image URL, category, brand if relevant and any custom labels or fields used in campaigns.

You do not need to review every row manually, but your sample should be representative. Include simple products, variants, discounted items, out-of-stock products, best sellers, long titles, category edge cases and products with unusual images. If you sell in multiple markets, also check currency, language and localized landing pages.

3. Identify how each product ID is built

Compare the exported ID with the source fields. Ask:

  • Is the ID exactly the SKU?
  • Does it include variant, color, size, country, language or currency?
  • Does the channel add a prefix or suffix?
  • Is the ID different in Google, Meta and other channels?
  • Is it generated from an internal field that your ecommerce team does not usually see?

Write the rule in plain language. For example:

“For Google UK, the ID is built as SKU + hyphen + variant + hyphen + market.”

This written rule is more useful than a screenshot buried in an email thread. If an agency or previous provider managed the old feed, ask for this logic before the migration starts.

4. Build the new feed in parallel

Do not replace the old URL yet. First, build the new feed alongside it and compare the outputs. With AdMotion’s Feed Manager, you can connect a store, file or existing feed, map fields, normalize data with rules and generate channel-specific feed URLs.

A practical workflow looks like this:

  1. Connect the source: ecommerce store, product file or existing feed.
  2. Map the core fields: ID, title, price, stock, image, link and relevant attributes.
  3. Create rules: for example, rebuild the product ID from SKU + variant + market if that was the previous logic.
  4. Filter product sets: separate products by channel, category, market, stock status or commercial use case.
  5. Generate the output feed: create a feed URL for the required channel.
  6. Review errors and warnings: check required attributes, formats and suspicious values before using the URL in the channel.

At this point, the new URL is not replacing the old feed. It is a controlled audit tool.

5. Compare old feed versus new feed

Create a product-by-product comparison. The goal is not to make every field identical forever. The goal is to make every difference intentional.

Element Should usually stay stable Can change with control
Product ID Yes, unless you plan a deliberate ID migration Only if you accept the possible impact
Product URL Must be valid Can change if the website changed
Price Must match the store Can reflect real promotions
Availability Must be coherent Can change as stock changes
Title Must be useful and accurate Can be optimized without misleading users
Image Must represent the product Can improve if still accurate

Avoid telling your team that the migration will have “zero impact”. Feed migrations can create changes. The point is to detect differences before the channel processes them as official product updates.

6. Review channel requirements

Each channel has its own feed format. Required attributes depend on the product type, market and destination. Google documents required and recommended product data in its specification; other channels may require different field names, category values or formatting rules.

AdMotion’s Export Channels supports feeds for Meta, Google Shopping, Google Dynamic Feed, TikTok, Pinterest, Snapchat, Criteo, Microsoft Advertising, Thribee, ChatGPT and a custom channel. It also includes an analyzer that reviews each feed against the channel specification.

That review is not a guarantee of approval. A channel can still apply its own policies, landing page checks and account-level validations. Treat the analyzer as a pre-flight control layer, not as a promise that every item will be accepted.

7. Replace the URL channel by channel

Once the new feed has been reviewed, change the URL in one channel at a time. Avoid switching every destination on the same day if you have a large catalog or important active campaigns. A staged transition makes it easier to isolate issues.

A cautious order could be:

  1. A lower-risk channel or smaller market.
  2. A test feed or secondary country, if available.
  3. Google Merchant Center or Meta, depending on business priority.
  4. The remaining channels.

Remember an important limitation: the feed manager’s import or generation timing and the channel’s fetch timing are not the same thing. A feed URL may be generated when it is downloaded, but that does not mean Google, Meta or another platform will read and process it instantly.

How to do it with AdMotion

If you are migrating from another feed tool, AdMotion can help with import, cleaning, segmentation and export. The aim is to capture what already works, document the fragile parts and make the setup easier to maintain.

A practical the platform migration flow is:

  1. Connect your catalog from your ecommerce store, file or existing feed.
  2. Map the main fields: ID, title, description, price, availability, product link, image, brand and category.
  3. Recreate critical rules, such as ID construction or excluding unavailable products.
  4. Create product sets by channel or campaign, using real catalog fields.
  5. Generate a feed per channel, using the required destination format.
  6. Review errors and warnings before sending the feed URL to the platform.
  7. Copy the feed URL into the advertising or commerce channel that will read it.

Later, if you also want to adapt product creatives, you can use the Templates Editor to generate one image per product with catalog fields such as photo, title, price or brand. But during the initial migration, the priority should be data stability: IDs, links, prices and stock.

If your immediate task is to organize the transition, start with the Feed Manager. You can test with your own catalog before changing every channel feed URL.

Common mistakes when migrating a product feed

  • Changing the ID because it looks cleaner. A prettier ID is not always better if the channel already knows another one.
  • Copying only the main feed. Check secondary countries, clearance feeds, campaign-specific sets and smaller channels.
  • Ignoring variants. Sizes, colors, bundles and packs may need distinct IDs even when they share a title or image.
  • Confusing feed readiness with channel processing. Your new feed can be ready before the channel downloads, validates and applies it.
  • Failing to document old rules. If nobody knows why an ID contains country, variant or language, someone may remove it later.
  • Migrating and optimizing at the same time. Clean up obvious errors, but avoid changing IDs, titles, categorization and campaign sets all at once unless you have a clear testing plan.

Final migration checklist

Before you replace a feed URL, review this checklist:

  1. All current feeds are listed. Include channel, URL, market, language, scope and owner.
  2. A copy of the old feed is saved. Keep IDs, titles, links, prices, availability and images.
  3. ID logic is documented. You know how each channel receives product identifiers.
  4. The new feed is running in parallel. It has not replaced the old URL yet.
  5. A product sample has been compared. Differences are intentional, not accidental.
  6. Channel errors and warnings are reviewed. You have checked required attributes and formatting issues.
  7. The transition order is defined. You know which channel moves first, second and last.
  8. Stakeholders understand the limits. A new feed URL does not mean instant processing by every platform.

What to do this week

  1. List every active product feed. Include the channel, URL, market, language, products included and internal owner.
  2. Download a representative sample. Save product IDs, titles, links, prices, availability, images and custom fields.
  3. Document product ID rules. Write down how the identifier is built for each channel.
  4. Create a new feed in parallel. Do not replace the old URL until you have compared the output.
  5. Plan the channel-by-channel cutover. Change one destination, review errors and warnings, wait for channel processing, then continue.

Switching feed manager can be a good moment to remove outdated rules, create cleaner product sets and prepare channel-specific feeds. Do it in the right order: preserve product identity first, then optimize.

Frequently asked questions

Can I switch feed manager without changing product IDs?

Yes, if you first identify how your current IDs are built and reproduce that logic in the new feed manager. Check whether each ID uses SKU, variant, market, language or other fields. Then compare the old and new feeds before replacing the URL in each channel.

Should I move every channel to the new feed on the same day?

Usually, no. It is safer to build the new feed in parallel, review it and replace URLs channel by channel. That way, if Google, Meta, TikTok or another destination reports errors or warnings, you can isolate the issue instead of troubleshooting every channel at once.

Will the new feed update instantly in Google or Meta?

Not necessarily. The timing of your feed URL and the timing of each channel’s download and processing are different. A feed can be generated or updated before a platform fetches it, validates it and applies changes. Plan the migration with enough review time.

Sources

  1. Feed Manager de AdMotion — AdMotion
  2. Export Channels de AdMotion — AdMotion
  3. Especificación de datos de producto de Google — Google
Share:
J

Written by

Julia Villegas

Performance Marketing

Julia Villegas works in performance marketing at AdMotion.

Related posts