Move your feed setup from another feed tool with an AI agent
Connect Claude or another AI agent to Renable and let it look at your setup in the feed tool you use today. It rebuilds your catalogs, rules and channels in Renable and lists what it couldn't rebuild. You check it product by product and switch one channel at a time.
Updated November 6, 2026
If you use Claude, or another AI agent that supports MCP, it can move your setup from another feed tool to Renable
for you. It looks at what your old feed tool does today, rebuilds your catalogs, rules and channels in Renable, and
checks real products against what the old tool sends.
Your ads keep running on the old tool's feeds the whole time. You switch one channel at a time, when you decide: by
swapping its feed address at the destination, or, where the old tool pushes a file to the destination by SFTP, by
having Renable push it instead.
What to have ready#
- Your agent connected to Renable. See Connect Claude or another AI agent. The agent
works in a Renable organization you already belong to, so sign up first if you haven't.
- Your old feed tool open in your browser. If your agent can work in your web browser, sign in to the old tool
there yourself. The agent then reads your projects, rules and channels on the old tool's own screens. Renable's
guide tells the agent to only look there and never to ask for your login to the old tool.
- Otherwise, your feeds, exports and screenshots. Give the agent the address of your store's own product feed and
of each feed the old tool publishes, plus any exports or screenshots of its setup. It reads those itself and asks
you about what they don't show, such as a rule.
Start the move#
Ask in your own words, for example "Move my feeds for sportgear from the tool I use today to Renable." You can also
pick Inventory my current feed setup from Renable's prompts in your agent. The agent starts by taking stock:
which organization to use, which feeds and channels you have, and what each one contains. It shows you that list
and its plan before it builds anything.
What the agent builds#
- A project for the store, or it uses one you already have.
- A catalog whose Product feed is your store's own feed, with its columns mapped on the Mapping tab.
- Rules that do the old tool's job: Set field for a title fix, Exclude product for a filter, Mapping
tables for categories, Split into variants where a product needs splitting.
- A channel for each destination, with its Fields and Rules set up to match the feed the old tool sends.
The agent can put one of your Studio templates into a channel, but it can't create or change a template. If your
old feed uses designed images and you have no template for them yet, design one in Studio, where Aimée can help,
publish it, and ask the agent to use it.
Publish and check, in this order#
Everything the agent sets up waits as Unpublished changes until it publishes, and it publishes when you ask.
Connect Claude or another AI agent says what a
publish does.
- The catalog. When its rules are in place, the agent publishes the catalog and Renable imports your products.
Nothing changes outside Renable.
- Each channel, product by product. Before a channel is published, ask the agent to check real products, or pick
Verify a migrated channel from Renable's prompts. It takes products from the feed the old tool publishes, finds
the same products in Renable by their ID, and compares every field. Then it lists what matches and what
differs, and why.
- The channel. Publishing a channel changes nothing for a destination that fetches a feed address: it keeps
fetching the old tool's address until you change it. Publishing a channel with SFTP delivery sends its file to
that server straight away, so the agent adds SFTP delivery only when you switch that channel.
Name the products you know are tricky: "Check products 10442 and 10587 on the Google channel." A variant, a sale
price or a product the old tool leaves out are good tests.
To look for yourself, Trace on a catalog's Rules tab walks one product through every rule, and Trace on
a channel's Fields tab shows how each field got its value.
What doesn't carry over#
Renable prepares product feeds and creative for ad networks and comparison sites. The agent lists anything it
couldn't rebuild; check those products first. These never carry over:
- Selling on marketplaces. Renable doesn't list products on marketplaces or handle their orders. If the old tool
does that for you, keep it for that and move your ad channels.
- Text ads and campaigns. Renable doesn't create search ads or manage campaigns.
- Designed images. Images the old tool designs don't move with the setup. Design a template in Studio instead.
Move one channel at a time#
- When a channel's checks look right and it's published, wait for its first run to finish on its Activity tab.
- Copy the channel's feed URL.
- At the destination, replace the old tool's feed address with the Renable one.
Connecting a channel to Meta, Google, or TikTok shows where to
find the URL and where it goes. If the old tool pushes a file to the destination by SFTP instead, switch that push
off in the old tool, then ask the agent to set up SFTP delivery on the channel and publish it.
- Watch the channel for a few days, then move the next one.
Keep the old tool running until the last channel has moved. Anything you switch off or change there is your step,
and apart from a push you switch off in step 3, it waits until the destination reads Renable's feed.