Shoptet migration: moving to or from Shoptet

Shoptet is a hosted SaaS ecommerce platform built for Czechia and Slovakia, with Czech-language support, local payment and shipping integrations and a large partner network. Merchants move onto it from self-hosted WooCommerce, PrestaShop, OpenCart or Magento stores to stop running servers and plugins, and from smaller local platforms. Shoptet itself publishes "Převod dat z X do Shoptetu" help guides for many source platforms, which work well for simple catalogs.

Merchants leave Shoptet mostly for international expansion: several countries, languages and currencies, a larger app ecosystem, or marketplaces and integrations that are easier on Shopify or another platform. The typical route is Shoptet to Shopify.

When not to move: if you sell mainly in Czechia and Slovakia and Shoptet covers your needs, a move adds cost without clear benefit. We say so in the assessment.

There is no database access on Shoptet, so data comes from its exports and, where your plan and set-up allow it, the API. Products export as CSV or XML, including variants linked by a shared pair code, parameters, categories, images and SEO fields. Customers and orders have their own exports. Which fields are included, and whether API access is available, depends on your plan and add-ons, so we confirm it on your store before promising scope.

The pitfalls: variants and parameters that look similar in the admin but export differently, filtering parameters versus informative parameters, images referenced by URL that must be downloaded before the old store closes, order exports that show totals but not every line-level discount, and data held by add-ons that is not in the standard exports. We check a full sample export before writing the mapping.

Shoptet imports products from CSV or XML files in its own format. Each product has a code, and variants of one product share a pairCode, so a source catalog with variants has to be restructured into that shape. Categories, parameters, prices, stock and images are part of the product import; customers have their own import. Order history support is more limited, so we agree early whether historical orders are imported, kept in an archive or exported to your accounting system.

Shoptet's own guides and add-ons cover the basic transfer for common platforms. What they do not cover is the decisions: which source attributes become variants and which become parameters, how to handle products with more options than you want to show, what to do with customer-group prices, and how old URLs are redirected. That is where a managed migration adds value.

Into Shoptet: WooCommerce variations and PrestaShop combinations become Shoptet variants joined by pairCode; attributes and features become parameters, split into filtering and informative ones; nested categories are rebuilt in Shoptet's tree; HTML descriptions are cleaned of shortcodes and module markup.

Out of Shoptet: variants grouped by pairCode become products with variants on the target, which on Shopify means checking the option names and counts; parameters become metafields or filters; categories become collections; Czech and Slovak text, VAT settings and prices in CZK and EUR are mapped to markets. Heureka and Zboží.cz XML feeds are rebuilt on the target, because the feed configuration does not move with the data.

Shoptet stores rely on add-ons from the Shoptet add-on marketplace and on integrations for accounting (for example Pohoda or Money), carriers such as Zásilkovna or PPL, payment gateways, comparison-shopping feeds and marketing. Add-on data and settings do not move with the store. Leaving Shoptet, we check what each add-on stores and whether it can be exported; moving onto Shoptet, we choose add-ons and reconnect integrations after the core import.

Shoptet templates do not transfer to other platforms, and other platforms' themes do not transfer to Shoptet, so the storefront is rebuilt in both directions. Checkout, payments, shipping and VAT are configured on the target and tested with real test orders before launch.

Shoptet generates product and category URLs from slugs that you can edit, and many CZ/SK stores have years of organic traffic and comparison-feed links pointing at them. Moving onto Shoptet, the source URLs rarely match Shoptet's structure, so a redirect map is needed; Shoptet lets you manage redirects in the admin. Leaving Shoptet for Shopify, URLs gain fixed prefixes such as /products/ and /collections/, so every product and category URL changes.

We crawl the live store, combine it with the product export and Search Console data, and map every indexed product, category, article and page URL to its new address, per language and domain where there are several. After launch we re-crawl for 404s and redirect chains, and check that feeds point to live URLs. We do not promise rankings; we make sure old URLs land on the right new page.

Customer passwords: when moving onto Shoptet or off it to a hosted platform, plan for customers to set a new password by email; we confirm what is possible on your specific route. Stored payment methods stay with the payment provider. Order history into Shoptet is limited, so older orders may stay in an archive or accounting system.

What Shoptet exposes depends on plan and add-ons, and the platform changes over time, so we treat any Shoptet capability we have not seen on your store as something to assess. Multi-language and multi-country set-ups on Shoptet differ from markets on international platforms, and mapping them is decided per project.

We start with an audit: your plan, exports and API access, catalog with variants and parameters, add-ons and integrations, feeds, and current URLs. From that we write the data mapping and agree it with you. A trial migration loads the catalog, customers and agreed order history into the target, including the redirect map, and you review it on staging.

After sign-off we set a short catalog freeze, run the final migration plus a delta of new orders and customers, switch the domain, activate redirects and feeds, and run post-launch QA: test orders, redirect checks, feed checks and Search Console monitoring. One named lead owns the project, and we work in Czech or English.