VirtueMart to PrestaShop Migration

Choose Your VirtueMart to PrestaShop Migration Method

Start with the data your business needs in PrestaShop and compare each method against that scope. A product file alone does not transfer the full catalog, customer profiles, historical orders, discounts, reviews, and relationships together.

PrestaShop’s native importer changes its available fields by entity. Its manual file-mapping workflow is separate from LitExtension Automated Migration. Choose the method that fits the records and relationships you need, rather than assuming a catalog import completes the entire move.

Prepare Both Stores and Define Scope

Back up the VirtueMart database, files, and important assets. Record counts for selected entities and retain representative examples: products with variants and custom fields, sale prices, customer profiles, orders with different statuses, coupon restrictions, reviews, and translated records.

Prepare PrestaShop and identify existing products, customers, and orders that must remain. Save a target backup before enabling Clear Target Data. Keep a record of custom VirtueMart extensions and describe any data they generate before starting.

If PrestaShop uses multistore, identify the intended shop and review associations, customer sharing, and module configuration. Target multistore support does not automatically establish migration of every VirtueMart storefront, store assignment, or shared-customer rule.

Prepare the PrestaShop theme, modules, payments, carriers, tax configuration, notifications, and checkout separately. Data migration does not convert VirtueMart extension code or storefront design into their PrestaShop equivalents.

Connect VirtueMart and PrestaShop

Sign in to the LitExtension app and create a migration. Select VirtueMart as Source Cart and PrestaShop as Target Cart. Enter the required store details and follow the connection instructions for your installed versions.

Complete the connector setup displayed for each store and keep required access available through transfer and validation. If a connection check fails, review the details and source/target setup, then share the error with support. Do not substitute native CSV-import instructions for the app’s connection workflow.

Select Products, Variants, and Categories

Products include names, SKUs, short/full descriptions, status, manufacturer, tax class, regular/special prices, quantities, related products, meta titles/descriptions, weight, width, height, variants, thumbnail images, and additional images.

Variants remains a parent group without extra subfield promises. VirtueMart’s official documentation distinguishes string fields, child variants, multivariants, and plugin-based custom fields. That source flexibility does not establish automatic conversion of every input, dependency, price modifier, or plugin behavior into PrestaShop combinations.

Include representative selectable products in the Demo and compare selections, prices, quantities, images, cart behavior, and related-product links. Separate Attributes, Manage Stock, product tags, EAN/GTIN, MNP, creation dates, and meta keywords are outside this shared scope. Source Length is not assumed equivalent to target Depth.

Categories include names, descriptions, sort order, images, and meta titles/descriptions. Parent and meta-keyword fields are not included. Review target category organization and product assignments, then configure navigation separately.

Select Customers and Prepare Account Access

Customers include first names, last names, emails, and billing addresses. Customer-profile shipping addresses, passwords, usernames, groups, status, creation dates, and display names are outside the listed scope. Joomla user accounts do not establish transfer of every authentication field.

Prepare account access and password setup or recovery communications for PrestaShop. Test representative customer records and billing addresses before launch. Billing and shipping addresses on historical orders are separate supported fields.

Select Historical Orders, Manufacturers, and Taxes

Orders include IDs, dates, statuses, items, subtotal, discount, tax, shipping price, total price, comments, customer names/emails, and billing/shipping addresses. Order Items and addresses remain parent groups without added detail-field promises.

Select Preserve Order IDs when staff need original VirtueMart references. Compare representative totals, statuses, comments, addresses, and customer relationships. Order tags, transactions, invoices, and tracking fields are outside this shared scope.

Manufacturers include names, descriptions, and images. Taxes include tax-class names and tax rates with country/rate information. Check tax records and product tax assignments, then test the configured target tax behavior; migrated records do not establish every country-specific tax or checkout setting.

Select Coupons, Reviews, and Languages

Coupons include titles, descriptions, codes, coupon dates, per-coupon usage limits, discount amounts/percentages, and start/end dates. Customer groups, per-customer limits, status, creation dates, and minimum spend are not included. Test remaining restrictions and eligibility separately in PrestaShop.

Reviews include creation dates, status, ratings, reviewer names, and comments. Reviewer user IDs are not equivalent to reviewer emails; neither field is included in this shared review scope. Review titles and product-code/name fields are also not included. Check target display behavior and prepare a display module where needed.

Multiple Languages covers product and category names/descriptions. Translated short descriptions, metadata, attributes, manufacturers, CMS pages, and blogs are not included. Prepare target languages and inspect representative translations before launch.

CMS Pages and Blogs are outside this route. VirtueMart runs within Joomla, but migrating store records does not recreate Joomla articles, menus, templates, user permissions, or extensions in PrestaShop. Keep required content and plan its preparation separately.

Configure Additional Options

Create 301 Redirects connects old VirtueMart URLs with corresponding PrestaShop destinations. LitExtension’s VirtueMart redirect guide calls for the free ReDJ plugin and preparation of the required redirects before selecting the option. Follow that workflow and test representative source URLs against the target. Preserve Order IDs retains original order references. Strip HTML Tags removes markup from product and category names. Review each option separately before the Demo.

Description Images transfers embedded images in supported product and category descriptions. Check these separately from product and category images. The option does not add blog or CMS-body migration.

Clear Target Data removes existing records for selected migration entities. Save a target backup and identify records that must remain before enabling it. Prepare target categories and navigation separately.

Review the Demo and Run Full Migration

Run a Free Demo and compare sample PrestaShop records with VirtueMart. Inspect descriptions, prices, quantities, variants, related-product links, images, category sorting, manufacturer records, customer billing records, orders, taxes, coupons, reviews, and translations.

Matching counts alone do not establish correctness. Save source and target examples for discrepancies and resolve them before Full Migration. Once started, the transfer runs on LitExtension’s servers, so you can close the browser and return to check progress.

VirtueMart can continue accepting orders during transfer. Validate completed records and relationships, then test product selection, account access, coupon eligibility, payments, carriers, taxes, notifications, and checkout on desktop and mobile.

Prepare URLs, Final Updates, and Launch

Review migrated product/category metadata, test important old links and redirects, update internal links, and check target navigation. Original product/category URL keys are not listed; redirects do not guarantee unchanged rankings. Review any custom SEO extensions separately.

Track new and changed VirtueMart records during migration. Recent Migration transfers new records, Smart Update handles changes to existing data, and Re-migration reruns the transfer. These services are free for 60 days; review final updates before directing customers to PrestaShop. They do not create continuous synchronization.

Estimate Cost and Timing

Cost and timing depend on selected data volume, options, images, connections, and agreed custom work. Allow time for preparation, Demo feedback, Full Migration, validation, customer-access testing, and launch checks.

Use Estimate Migration Cost for an initial estimate. If you want specialists to manage the project, Schedule a Call to discuss All-in-One Migration.