How AI Agents Migrate a Large Product Catalogue in Hours, Not Weeks

Migrating a large product catalogue used to take weeks because every product, variant, price, image and category was reshaped by hand. At Varsuite, an AI agent reads your existing catalogue, maps it onto the new store's structure in hours, and a human checks the result before launch. The outcome that matters is a store that is correct on day one, not a spreadsheet you are still cleaning up a month later.

Why does catalogue migration usually take so long?

The products themselves are rarely the problem. The structure around them is. Two platforms almost never describe the same product the same way, so a migration is really a translation job: variants, tax rules, category trees, SEO fields and image references all have to line up.

Done by hand, that translation is slow and error-prone. You export a messy CSV, reshape columns for days, re-upload images one at a time, then discover halfway through that variants or VAT settings did not map. The bigger the catalogue, the more places an inconsistency can hide.

How do agents migrate a catalogue in hours instead of weeks?

An agent does the translation work a person would do row by row, except it stays consistent across thousands of rows and never gets bored on row 800. In practice it:

• Reads your current catalogue and works out the structure: which fields mean what, how variants are grouped, how categories nest.
• Maps that structure onto the new platform's schema, including prices, options, stock, categories and SEO fields.
• Pulls, optimises and re-links every image so product pages are not left with broken thumbnails.
• Produces a clear list of anything ambiguous that needs a human decision.

Because the rules are applied uniformly, the same logic that handles the first product handles the ten thousandth. That consistency is where most of the time saving comes from, and why the error rate drops against manual entry.

What about variants, pricing and images, the parts that always break?

These three areas quietly wreck most manual migrations.

Variants are the classic trap. A T-shirt in five colours and four sizes is one product with twenty buyable options, and platforms model that relationship differently. An agent keeps the parent and child relationships intact rather than flattening everything into twenty unrelated listings.

Pricing carries hidden complexity in the UK because of VAT. Whether your old prices include or exclude tax, and how the new store expects them, must be handled deliberately or you will over or undercharge from the first order. The agent normalises this, and a human confirms the tax treatment before anything goes live.

Images are tedious rather than tricky, which is why they get rushed. The agent re-hosts them, compresses them for fast loading, and reconnects each one to the correct product, so you are not matching photos to SKUs by hand.

Where do humans fit in, and why does that matter?

This is the part I care most about, because an import that is fast but wrong is worse than no import at all. At Varsuite, agents do the heavy, repetitive translation, and a human perfects and signs off the result before your store opens.

A person checks the edge cases the agent flags, confirms tax and shipping logic, spot-checks product pages across categories, and handles what needs judgement rather than rules: the tone of descriptions, how collections are merchandised, whether the navigation makes sense to a shopper. The agent removes the grind. The human guarantees the standard.

How do I keep my SEO when I move platforms?

A migration is a real risk to your search rankings, and it is the part store owners most often forget until traffic drops. Two things protect you.

First, the catalogue carries its meaning across: page titles, meta descriptions and alt text are part of the field mapping, not an afterthought. Second, old URLs are redirected to their new homes so you keep the authority you have built and do not strand customers on dead links.

Handled this way, the move is invisible to your customers and to Google. Handled carelessly, it can cost you months of recovery.

What does this mean for launch day?

The promise is simple to state and hard to deliver: a store that is correct when it opens. Prices that match, variants that work, images that load, categories that make sense, and SEO that holds. You spend your time on the work only you can do, while the data shovelling happens in the background. A small deposit secures the build, and the balance is due only when you approve the finished store, so the incentive to get it right sits with us.

Frequently asked questions

How large a catalogue can agents migrate?

Size is rarely the limiting factor. A few hundred products or many thousands are handled by the same mapping process, and a large catalogue tends to benefit most because consistency across thousands of rows is where manual work falls down.

Will my prices and VAT be correct after the move?

Yes, this is treated as a deliberate step rather than an assumption. The agent normalises how prices and tax are stored to match the new platform, and a human confirms the VAT treatment before launch, so you are not over or undercharging from the first order.

Do I lose my Google rankings when I switch platforms?

Not if the migration is done properly. SEO fields move across with the products, and redirects send old URLs to their new locations so you keep the authority you have built. The aim is a switch that is invisible to customers and search engines.

What do I actually have to do during the migration?

Much less than with a manual move. You provide access to the existing store, answer a short list of decisions on anything ambiguous, and review the finished result before sign-off. The repetitive data work is handled for you.