Magento to Shoptet migration

The typical case is a mid-sized store that chose Magento years ago for flexibility and now pays for hosting, security patches, extension licences and agency hours it no longer uses. Magento 1 stores have had no official Adobe support since 30 June 2020, and the developers who built them are often gone. Shoptet replaces that with a monthly plan, a managed environment and a market-specific ecosystem: Czech and Slovak carriers, payment gateways, comparison-site feeds such as Heureka and Zboží.cz, and accounting and ERP connections, available natively or through the Shoptet add-on marketplace.

The trade-off is depth. Shoptet has no attribute sets, no website and store-view hierarchy and no way to install arbitrary code. If your business depends on B2B workflows, complex pricing logic or large custom modules, the assessment says so before any work starts, and sometimes the better answer is Shopify, BigCommerce or staying on an upgraded Magento 2.

Shoptet's help centre publishes step-by-step transfer guides for several source platforms, but a Magento store is normally prepared as custom import files. We read Magento 1 stores directly from the database; Magento 2 and Adobe Commerce stores through export, API and database checks together, because standard exports leave out attribute sets, URL rewrites and extension data. On Adobe Commerce, content staging stores EAV values per row_id, so extraction takes only the currently active version. The data is then transformed into Shoptet's CSV and XML import formats.

Magento groups attributes into sets per product type; Shoptet works with one shared list of parameters. Overlapping attributes from different sets (for example three different colour attributes) must be merged, renamed consistently and cleaned of duplicate values before import. We also decide which attributes become filtering parameters on category pages, which become variant parameters, and which only belong in the description or a specification table.

Configurable products become Shoptet products with variants: the configurable attributes become variant parameters, and each simple child becomes a variant with its own code, price, stock and image. Simple children that were also sold separately need a decision, because a variant is not a standalone product. Bundle and grouped products have no direct equivalent and are rebuilt as separate products, related products or a set sold with an add-on, depending on how stock and price should behave. Magento custom options with surcharges are the hardest case and are assessed one by one.

Magento prices are exported with the tax class of each product, and we check VAT rates, price rounding and prices including VAT in the trial import, because a wrong VAT mapping is one of the most common errors on this route.

Magento's category tree transfers into Shoptet categories, including products assigned to several categories. Anchor categories and Magento layered navigation are replaced by Shoptet categories with parameter filters, which usually means removing categories that only existed to simulate a filter. Manufacturers stored as a Magento attribute become Shoptet brands. Category descriptions and SEO texts are moved with their HTML cleaned of Magento widget and Page Builder markup.

Magento store views are often used for a Czech and a Slovak version, or for separate brands. Shoptet can run language and currency versions of one store, depending on plan and setup, but not independent websites under one administration. Each store view therefore gets a decision: merge into one Shoptet store, run separate Shoptet stores, or retire.

Customers, addresses, company details (IČO, DIČ) and newsletter consent are imported. Customer groups map to Shoptet customer groups and price lists where the plan supports them. Passwords are handled as a reset: customers set a new password on first login, and we prepare the announcement with you. Order history is imported for reference and customer accounts, not as live orders to be fulfilled or invoiced again.

Magento URLs come from the url_rewrite table (core_url_rewrite on Magento 1) and often end in .html or include the category path. Shoptet generates its own URL format, so most Magento URLs change. We collect every URL that matters from the rewrite table, a crawl of the live store, Search Console and backlink data, map each one to its Shoptet product, category, brand or article, and load the 301 redirects into Shoptet before the DNS switch.

After launch we crawl the old URL list against Shoptet, check status codes, resubmit the sitemap and regenerate product feeds for Heureka, Zboží.cz and Google Merchant Center, since feed URLs and product codes must match the new store. Redirects protect URL continuity and reduce risk; no migration can guarantee rankings.

Magento modules and themes do not migrate. Each active module is listed and matched to a Shoptet built-in feature, an add-on from the Shoptet marketplace, a custom integration through the Shoptet API where your plan provides it, or retirement. Typical items are carrier and payment modules, feed generators, ERP and accounting connectors, reviews, loyalty and B2B pricing. Supplier feeds that updated Magento stock and prices are reconnected to Shoptet. The design is rebuilt on a Shoptet template, with custom styling within what the template allows.

Audit, mapping, trial import, sign-off, freeze and delta migration, launch, post-launch QA. The audit covers data volume, attributes, store views, modules, integrations and indexed URLs. The mapping sheet records where each Magento field and entity goes in Shoptet. The trial import loads the full catalog into a Shoptet test store, and your team checks prices, VAT, stock, variants and parameters. Automated comparison flags differences in counts and values; a person decides what is correct. At launch we freeze Magento briefly, import new orders, customers and stock changes, switch the domain, activate redirects and run post-launch QA.