Feed Format Migration — step by step
Pick where you are and where you are going
Choose a source and a destination from Google Merchant Center, Meta Catalog and ChatGPT Ads. Each is offered only because its mapping is complete against that platform's published spec — you cannot convert onto a feed missing twenty required columns. If the destination is a feed-file-only channel like ChatGPT Ads, the screen says so before you start.
Read the column plan before you commit
Every destination column is classified as carried, rewritten, derived or unavailable. Unavailable columns are named with what to do instead — Meta's own taxonomy has no published mapping from Google's, for instance, so the feed carries google_product_category as the fallback Meta accepts and tells you to set the Meta field in Commerce Manager if you want its own categorisation.
See what the destination would refuse
The analysis counts feed rows rather than products, because one product with five sizes is five rows. It reports how many are ready and how many the destination would reject, groups one problem across many products instead of repeating it, and shows per-column fill coverage so an empty column is visible rather than silent.
Export, then connect
Export as CSV, XML or JSON. For Google and Meta you can push directly from Push to channels, behind the same per-change approval as every other platform write. For ChatGPT Ads you get the validated file and a hosted URL, and you connect it in OpenAI's Ads Manager.
Features used in this guide
Related guides
All use cases →Ready to try it?
FeedGraph is in early access. Apply to join and we'll onboard you personally — no credit card required.
Join early access