Start Your VTEX to Magento Migration Today!
Move your store from VTEX to Magento with a secure, guided migration tailored to your business.
Thu, 29 Oct 2026 - 21:23
To establish the connection, enter the URL and API credentials for the VTEX store you are migrating from.
Enter the URL of the Magento store you are migrating to. Then download the KitConnect package, unzip it, and upload it to that store’s website.
VTEX
MagentoVTEXMagento
These four data types are used to estimate the price. Other supported data, including categories, coupons, and reviews, is also migrated at no extra charge.
You can increase your plan’s data limit, upgrade your service, or add custom work while your license is valid.
You only pay the price difference, and your license expiry date stays the same. Custom work is reviewed and quoted separately.
Learn about upgrades (Opens in a new tab)No. In Magento 2 Open Source, existing variants become simple products linked to a configurable product. Ordinary options remain custom options, with their supported choices and price adjustments; they do not automatically become separately stocked variants. Include all linked products when migrating Magento to Magento. Check requirements for separate SKUs, inventory or extension-specific choices before migration.
No such total is calculated in the built-in source conversion. The main product quantity comes from the first returned stock balance for its first SKU. Verify stock by SKU and warehouse separately before treating that value as the destination's available stock.
For Magento 2 Open Source, Next-Cart writes supplied related products, cross-sells and up-sells as their corresponding link types, using the imported product IDs. Include every referenced product so the links can be rebuilt. This answer does not cover Adobe Commerce or every Magento extension.
Yes. For supported products, Next-Cart copies the supplied main image and gallery to Magento. Keep the original image links accessible and allow files to be written to the destination until you have checked the gallery. Images from extensions must be included in the source data. Images inside descriptions need the separate copying option, where available; check them before removing the old hosting.
Not in the built-in source setup. Standalone customer migration is disabled, even though order and product data have their own paths. If customer accounts are part of your project, establish a separate source and destination plan for them before migration.
If customer accounts are included in your migration, confirm the source platform, versions and Magento edition. Importing accounts alone does not guarantee that existing passwords will work. For supported Magento 2 Open Source routes, check compatibility of the matching Customer Password Plugin and test sign-in on the intended Magento website. Plan password resets or activation where credentials are unavailable or incompatible. Magento 1 and Adobe Commerce need separate confirmation.
No. The displayed order number, or Increment ID, is separate from the internal Entity ID: imported orders receive destination IDs and are linked through migration mappings. For imports from other platforms, the order-number preservation option uses the supplied order number, falling back to the source ID, and limits it to 32 characters; without that option, a new number is generated. Check existing destination numbers for conflicts before preserving them.
Available services depend on your migration path. Standard Migration lets you use the tool yourself with technical support. With Managed Migration, our technicians carry out the agreed migration. Custom Migration covers tailored requirements, with the migration carried out by you or our team as agreed. Data types must be supported by both connections; choosing expert handling does not by itself add unsupported data.
Where a self-service Demo Migration is available for your migration path, you can try it for free before purchasing. It transfers a small sample of supported data so you can check the result. Add-ons and custom work are not included in the self-service demo. For a file-based, custom or technician-assisted evaluation, contact us first to agree the test scope and any applicable cost.
Your data types and quantities determine the Entity Points total and the plan you need. The cost also depends on your chosen service, add-ons, and any custom work. Use the pricing calculator for an estimate; custom work is reviewed and quoted separately.
If you are migrating from a live store, it can normally keep taking orders while Next-Cart copies its data. The migration does not delete or change the source data. Plan the final update and the switch to the new store separately so recent orders and other changes are included. For file-based migrations, changes made after an export require a fresh export; an uploaded file is not a live connection to the store.
Yes. Your license allows repeat runs for the same store and migration path for 12 months from purchase, within your plan’s data limit. Continuing the previous migration can add eligible new records without importing the same mapped records again.
Changing records already migrated is separate: the paid Data Update add-on can update selected fields where your source, target version and those fields are supported. Keep the existing migration links and leave target-data clearing off. It does not automatically update every field or provide continuous synchronization.
Yes. While your license is valid, you can increase your plan’s data limit and upgrade to a higher service where it is available for your migration path. You can move from Standard Migration to Managed Migration or Custom Migration, or from Managed Migration to Custom Migration.
If you already use Custom Migration, you can add custom work after a review and quote. You pay only the additional amount, and your license expiry date stays the same.
Move your store from VTEX to Magento with a secure, guided migration tailored to your business.
