Migrating from PrestaShop to Shoptet

Shoptet removes server administration, PHP upgrades and module compatibility work. Invoicing, VAT handling, Zásilkovna, PPL, GoPay, Comgate, Heureka and Zboží.cz are native, which often replaces a dozen PrestaShop modules. What you give up is unrestricted customisation: PrestaShop lets you change anything with a module or override, while Shoptet exposes a fixed set of fields, templates and add-ons. Functionality that lives in custom PrestaShop modules must be re-evaluated rather than copied.

PrestaShop combinations (attribute sets such as size and colour) map to Shoptet variants; each combination becomes a variant row with its own code, price and stock. PrestaShop features, used for filtering, become Shoptet parameters that are created before import. Multiple category assignment is supported in both systems, but the default category in PrestaShop needs to be chosen explicitly as the primary category in Shoptet. Product images, descriptions, meta titles and descriptions transfer through the import; specific-price rules and customer-group pricing need a review, because Shoptet models discounts differently.

Customers with addresses and group membership are imported; passwords cannot be moved, so a reset flow is part of launch communication. Orders are imported as history for reporting. PrestaShop URLs depend on the friendly-URL settings and often include IDs; Shoptet uses its own path patterns, so we generate a full 301 map from the PrestaShop sitemap and analytics data and verify it before the DNS switch. Redirects protect URL continuity and reduce risk; rankings are never guaranteed.

We list every active PrestaShop module and decide: native in Shoptet, available as an add-on, custom integration, or dropped. Marketplace feeds are regenerated from Shoptet. The launch itself is a test import, a sample check of prices, VAT and stock, then DNS switch with PrestaShop kept read-only for a short overlap while the redirect map is confirmed in Google Search Console.