Start Your Magento to PrestaShop Migration Today!
Move your store from Magento to PrestaShop with a secure, guided migration tailored to your business.
Thu, 29 Oct 2026 - 21:23
Enter the URL of the Magento store you are migrating from. Then download the KitConnect package, unzip it, and upload it to that store’s website.
Enter the URL of the PrestaShop store you are migrating to. Then download the KitConnect package, unzip it, and upload it to that store’s website.
Magento
PrestaShopMagentoPrestaShop
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)For PrestaShop 1.5–8, set both the shop mapping and the language mapping before migration. Magento 2 supplies product text by store view, using default values where view-specific values are empty. PrestaShop writes that text to the mapped shops and languages; missing shop mappings can fall back to the first mapping or default shop. Check products in every intended shop and language. This answer does not cover the separate PrestaShop 9 connection.
Magento 2 product text is read by store view, with default-scope values used when a store-view value is empty. Map the required store views and destination languages before migration; do not assume that websites, stores and languages are interchangeable. The destination determines which translated fields and store assignments it can retain.
In the PrestaShop 1.5–8 connection, product shop assignments use the configured shop mapping, with a first-mapping or default-shop fallback. Translated product content is written using the language and shop mappings. Set these up together and verify products in each intended shop and language. PrestaShop 9 has a separate connection and is not covered by this version-specific description.
In PrestaShop 1.5–8 and 9, existing variants become product combinations with their supplied stock. Prices are stored as adjustments to the main product price. If only separate choices are supplied, Next-Cart creates up to 3,000 combinations; above that count, none are created. This generation limit does not apply to variants already supplied. Check references, final prices, stock and valid combinations. Conditional options or customization modules need separate handling.
Next-Cart reads bundle options and links to the component products, but these are not ordinary product variants. Include the bundle and its components in the migration. Before moving to another platform, confirm the final product type, component quantities and pricing. Transferring the product record alone does not mean the bundle can be purchased in the same way.
Check the actual download files, not just the product records. The default import creates downloadable-product metadata, including the filename, access duration and download limit, but that alone does not establish that the protected file has been copied to the destination. Confirm a real customer download before retiring the source.
For the PrestaShop 1.7/8 connection, supplied related-product links become accessories; up-sell links are used as a fallback where applicable. Links are skipped when the referenced product has no destination mapping. Include the linked products and review the resulting accessories. This does not establish identical behavior for PrestaShop 9 or every recommendation module.
In PrestaShop 1.7, 8 and 9, Next-Cart copies the product gallery and generates image sizes using the new store’s settings. Each combination can be linked to its supplied main image, but its entire original image set is not recreated. Check color-specific galleries and any additional image requirements. Images inside descriptions need the separate copying option, where supported.
Check the source's password format, the exact PrestaShop version and compatibility of the required Customer Password Plugin. Importing customer records does not by itself make their old passwords usable. On supported routes to PrestaShop 1.7 and newer, usable source credentials and a compatible module are required; versions 1.5/1.6 need separate validation. Review the answer for your exact migration pair and test sign-in before launch. Plan password resets or activation when credentials cannot be retained.
Customers can keep their passwords if Magento supplies compatible stored login data and the matching Customer Password Plugin supports both platform versions.
This covers the PrestaShop 1.7-and-newer import path. Versions 1.5/1.6 shorten stored credentials and need separate validation. Confirm module compatibility for the actual target version. Choose the correct Magento source version; Adobe Commerce is a separate connection. Install the compatible plugin and test migrated accounts before customers sign in. Accounts without compatible login data need a password reset or activation.
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 Magento to PrestaShop with a secure, guided migration tailored to your business.
