Skip to content

Migration route

Migrating from Magento (Adobe Commerce) to Shoptet

Magento and Adobe Commerce are built for complex catalogs, multiple store views and heavy customisation, at the cost of expensive hosting and development. Shoptet is a hosted platform for Czech and Slovak merchants with a simpler, fixed data model and local integrations built in. The migration is mostly a consolidation exercise: reduce Magento's attribute sets, configurable products, store views and custom modules to what Shoptet can represent, move customers and order history, and protect the URLs that bring organic traffic.

Who moves from Magento to Shoptet and why

Merchants make this move when the Magento setup has become disproportionate to the business: a mid-sized Czech or Slovak store paying for Magento hosting, security patches, extension licences and agency hours it no longer needs. Shoptet replaces that with a monthly plan, native Zásilkovna, PPL, GoPay, Comgate, Heureka and Zboží.cz integrations and a managed environment. The trade-off is depth: no attribute sets, no multi-website hierarchy, no free-form extensions. If your business relies on those, the assessment will say so before any work starts.

Attribute sets, configurable products and categories

Magento attribute sets become a single flat set of Shoptet parameters, so overlapping attributes from different sets must be merged and renamed consistently. Configurable products map to Shoptet products with variants; the simple children become variant rows with their own codes, prices and stock. Bundle and grouped products have no direct equivalent and are rebuilt as separate products or product sets. Category trees transfer, but Magento's anchor categories and layered navigation are replaced by Shoptet categories and parameter filters, which usually means flattening the hierarchy.

Store views, customers and orders

Magento store views are often used for languages or brands. Shoptet supports language mutations per store but not independent websites, so each store view needs a decision: merge into one Shoptet store, run several Shoptet stores, or drop. Customers and addresses are imported, customer groups map to Shoptet price levels, and passwords are reset on the new store. Order history is imported for reporting. Custom modules, ERP connectors and B2B features are listed one by one and matched to native features, add-ons or a custom integration.

Redirects and cutover

Magento URL rewrites and category paths in product URLs differ from Shoptet's patterns, so we export all indexed URLs, build a complete 301 map and load it into Shoptet before the DNS switch. A test import of the full catalog is checked for prices, VAT, stock and variants, then feeds are regenerated and the sitemap is resubmitted. Redirects protect URL continuity and reduce risk; rankings are not guaranteed by any migration.

Frequently asked questions

Can Magento configurable products be migrated to Shoptet?

Yes. Each configurable product becomes a Shoptet product with variants, and the simple child products become variant rows with their own code, price and stock.

What happens to Magento attribute sets?

Shoptet has one flat parameter list, so attribute sets are merged. Duplicate or conflicting attribute names are cleaned and renamed before import.

How are Magento store views handled?

Each store view is decided separately: merge into one Shoptet store, run several Shoptet stores, or drop. Shoptet supports language mutations but not independent websites.

Do I keep customers and order history?

Customers, addresses and group pricing are imported; passwords are reset. Orders are imported as history for reporting, not as editable live orders.

Prevedshop.com

Moving your store? Let’s find out what needs to come with you.

Tell us where the store is now and where it is going. We’ll come back with the useful questions—not a generic sales pitch.

Show me the migration plan