Skip to content
Tell us about your project

Migration · · 9 min read

VTEX to Shopify migration: data, catalog and URLs

Migrating from VTEX to Shopify means answering three questions early: what data you can actually get out, how the product-SKU model, trade policies and Master Data fit Shopify, and how to keep the /p product URLs from losing their rankings. This guide answers each one from the official documentation of both platforms.

Start with an inventory of what VTEX does for you today

A VTEX store usually runs on more than the storefront shows. Before exporting anything, list every piece in use and who owns it inside the company.

Give each item a destination in Shopify: native feature, app, custom build or left behind. This list is also what makes migration proposals comparable. A partner who never asks about trade policies or Master Data is scoping a simpler project than yours.

If an ERP or OMS is involved, decide which system owns each data type: catalog, prices, stock, orders and customers. Our guide to Shopify ERP integration covers how to split those flows.

  • Trade policies and the channel each one serves
  • External sellers or a marketplace setup
  • Active promotions and price tables
  • Custom Master Data entities beyond customers and addresses
  • Apps and custom work on the storefront, whether Store Framework or FastStore
  • ERP, OMS, logistics and external marketplace integrations

What you can export from VTEX, and where

VTEX announced that every store would have its new spreadsheet import and export experience by the end of February 2026, with all operations under Catalog > Products and SKUs. The Export button there produces separate files for products and SKUs, product specifications, SKU specifications and images. Each export is an .xlsx file; the download link arrives by email and expires after 24 hours.

The products and SKUs export is capped at 300,000 products. Its fields include name, description, brand, department, category, the product URL slug, page title, meta description and the trade policies the product belongs to, plus SKU reference code, EAN, dimensions and weight. Prices and inventory are not part of that file, and images and specifications come in their own spreadsheets.

Prices are exported from the Price List in the Prices module: choose the base price table, the fixed price table or the calculated table, which shows the final price without promotions. SKUs without a price are left out. Inventory is exported from the Warehouses tab of Shipping Strategy with Export items; the file is emailed and has one row per SKU per warehouse.

Customers live in Master Data, split across two data entities: CL holds shopper profiles and AD holds addresses, linked through the userId field. You pull them through the Master Data API, which offers a scroll endpoint for reading large sets across several requests. If the store keeps its own data in other entities, find them and decide what happens to each.

Orders come out through the VTEX Orders API, which lets you list orders and then fetch each one in full, or through a migration app that handles the extraction.

  • Products and SKUs spreadsheet, exported with every field
  • Product and SKU specification spreadsheets
  • Image spreadsheet by SKU
  • Base and fixed price tables
  • Inventory per warehouse
  • Customers (CL) and addresses (AD) from Master Data
  • Orders, whether you will import or archive them
  • Search Console list of URLs with traffic

From VTEX products and SKUs to Shopify variants

In VTEX the product holds the shared data and each SKU is a specific variation with its own reference code, EAN, dimensions and weight. Shopify works in a similar way: a product has options such as size or color, and every combination of values is a variant with its own SKU, price and inventory item. The straight mapping is one VTEX product to one Shopify product and one SKU to one variant.

If you have read that Shopify caps products at 100 variants, that figure is out of date. Since 15 October 2025 every Shopify merchant can create products with up to 2,048 variants. The catch is apps: those not using the in-support GraphQL product APIs may break on products with more than 100 variants, so check your catalog, feed and ERP apps before loading large products.

VTEX specifications need a field-by-field decision. SKU specifications that tell variants apart become options. Everything else, such as composition, measurements or technical data, goes to product or variant metafields; data that deserves its own record and repeats across many products, like a material, fits better as a metaobject. Our guide to Shopify metaobjects explains when each one pays off.

Departments and categories become collections, manual or automated by conditions, and the hierarchy is rebuilt in the navigation menu. Brand can live in a metafield, or in a brand collection if it needs its own page.

A small catalog fits the Shopify product CSV. With thousands of SKUs, specifications and images per variant, a repeatable script on the Admin API or an import app is the safer route, run until the result is clean. At Weblineo this catalog mapping, together with the URL map, is part of our Shopify migration service.

Trade policies, pricing and B2B

A VTEX trade policy bundles catalog, pricing, promotion, logistics, customer segmentation and payment settings for one sales strategy, separating conditions for marketplaces, sellers, the brand’s own store, physical stores or B2B. The current English help center calls them sales channels, while the Spanish version still uses políticas comerciales.

Shopify spreads those jobs across several features, so review each trade policy on its own and decide where it lands.

The marketplace is the part that needs the most analysis. If external sellers publish their catalog and receive orders through VTEX, decide before you start whether that model continues, how sellers will get their orders and who collects payment. On Shopify you will have to choose and test a specific solution, app or custom build, and validate it before the migration scope is closed.

  • Countries, currencies and languages: Markets. Each market groups countries or regions and supports local-currency prices, percentage adjustments or fixed prices by country or region.
  • Companies with their own assortment and prices: Shopify B2B, with companies and catalogs. It is available on Basic, Grow, Advanced and Plus; outside Plus there is a cap of 3 active catalog assignments across B2B markets.
  • Brands or countries that need a separate store with its own settings and storefront: Shopify Plus expansion stores, up to ten stores per organization at no extra cost, including the main one.
  • Promotions: rebuilt as Shopify discounts; very specific conditions may call for an app or custom work.

Customers, accounts and order history

The Shopify Help Center lists three ways to migrate customers: the customer CSV, a migration app or the Customer API. From Master Data, join every CL profile to its AD addresses by userId and carry over marketing consent per channel exactly as it was, so anyone who unsubscribed on VTEX arrives in Shopify without consent.

Passwords cannot be migrated by CSV. With current Shopify customer accounts they are not needed either: customers enter their email and receive a one-time 6-digit verification code. Email them before and after the switch so nobody thinks their account is gone.

For historical orders, the Help Center points to migration apps and the Order and Transaction APIs rather than CSV. Turn off staff new-order notifications before importing, because every imported order triggers an email.

Decide first what the history is for. If customers need to see past purchases in their account, import it. If it is only needed for accounting, returns or support, archiving the VTEX export where the team can reach it is enough.

Redirecting VTEX /p URLs without losing rankings

On VTEX a product page URL is the store domain plus the textLink field of the product plus /p, so a product with the textLink polo-shirt sits at store.com/polo-shirt/p. On Shopify, product pages live under /products/ followed by the handle, and collections under /collections/. No VTEX product URL matches its Shopify counterpart, so every one with traffic or backlinks needs a 301 redirect.

The base rule is store.com/{textLink}/p to store.com/products/{handle}. Reuse the textLink as the handle and the map comes almost straight out of the products spreadsheet, which has the URL slug in its own column. Watch for products whose textLink was changed in the Admin or through the Catalog API, where the field is called LinkId: the URL Google has indexed may not be the current one. Build the real list from Search Console and a crawl, not from the spreadsheet alone.

Department and category pages have their own paths; map each one to its collection. Do not send internal search pages or filtered URLs to the home page in bulk; if one has traffic of its own, point it to the closest collection.

Shopify redirects are created one by one in URL redirects or imported from a CSV, up to 100,000 per store and 20 million on Plus. They only fire from broken URLs: if the old address still loads a page, the redirect does nothing. Paths starting with /apps, /cart, /orders or /shop cannot be redirected. Our guide to 301 redirects for a Shopify migration covers loading and testing them.

Carry over the page title and meta description of each product, which the VTEX spreadsheet exports in their own columns. Shopify generates sitemap.xml automatically; submit it in Search Console on launch day.

Theme, payments, domain and launch day

The VTEX storefront, Store Framework or FastStore, cannot be moved to Shopify. The theme is rebuilt on Online Store 2.0, starting from a Theme Store theme or built to measure; our guide on custom theme versus template helps you choose. It is a good moment to redesign the product page around the specifications you turned into metafields.

Payments, shipping and taxes are set up from scratch. Run complete test orders with every payment method and every shipping option before opening.

The new store is built in parallel on its .myshopify.com domain while VTEX keeps selling. On launch day, run a final export of customers and orders, point the domain DNS to Shopify, submit the sitemap and watch 404 errors in Search Console over the following weeks to add any missing redirects.

Weblineo has worked only with Shopify since 2016 and is a Shopify Plus Partner. If you are planning to leave VTEX, our Shopify migration service covers extraction, catalog mapping and redirects; if your channels or volume call for Plus, we scope it with our Shopify Plus service.

Frequently asked questions

Does the VTEX product export include images and prices?

No. The products and SKUs spreadsheet has no price or inventory fields, and images have their own export in the same Catalog section. Prices come from the Price List and inventory from the warehouses, each in a separate file.

What happens to product URLs ending in /p?

They stop existing. On VTEX a product URL is domain, textLink and /p; on Shopify it is /products/ plus the handle. Every URL with traffic needs a 301 to its product, and reusing the textLink as the handle makes the map almost direct.

How many variants can a Shopify product have?

Up to 2,048 for every merchant since October 2025; the 100-variant limit still quoted in many places is out of date. Make sure your catalog apps use the in-support GraphQL product APIs, as apps that do not may break above 100 variants.

Do I need Shopify Plus to leave VTEX?

It depends on what your trade policies do today. B2B is available from the Basic plan, with a cap of 3 active catalog assignments outside Plus. You need Plus for expansion stores, for more than 100,000 redirects or to lift that catalog cap.

Will my customers have to sign up again?

No. Their data is imported, although passwords cannot be migrated. With current Shopify customer accounts they sign in with their email and a one-time code, no password needed.

Tell us what your store needs

Tell us about your project in a few minutes. If it’s a fit, you book a 30-minute call with a developer and we send you a fixed-price proposal.

Tell us about your projectWe reply within 24 hours