What an SAP Commerce migration plan covers
We start with what your SAP Commerce setup actually does: base sites and catalogues, base and variant products, classification attributes, price rows, B2B units, promotions, CMS pages and the extensions your team built. Each part gets a decision: move it, rebuild it on Shopify, replace it with an app, leave it in SAP or retire it. Then follow the URL map and redirects, the migration of products, customers and orders, the S/4HANA connection, tracking and feeds, and QA on real processes, from checkout to invoice.
PROVEN
RESULTS
TOTAL SALES VS. PREVIOUS PERIOD
What moves from SAP Commerce, and how
SAP Commerce and Shopify structure a shop differently. We map every part to its Shopify counterpart before anything is imported:
Base products with variant products, such as style and size variants, move as one product with variants. Shopify allows three options and 2,048 variants per product, so deeper variant trees are split or flattened.
Classification attributes become metafields, with the storefront filters rebuilt on top of them. We export from the Online catalogue version, not the Staged one.
Price rows per currency and price group become market prices or B2B catalogues.
Customer accounts, addresses and order history move. Passwords cannot be imported, so we plan activation emails or passwordless login. Orders go in through the Admin API, because Shopify has no CSV import for orders.
CMS pages and components from SmartEdit are rebuilt as Shopify sections and metaobjects.
We have used the same method for migrations from other platforms, such as Malelions, which moved from Lightspeed with more than 180,000 customers, and brands such as OGÉR, Mason Garments and NØORDCODE.
For every step in detail, read our guide SAP Commerce to Shopify migration.
Extensions, B2B and the SAP S/4HANA link
An SAP Commerce shop is a set of extensions: custom ones from your team, Accelerator add-ons, search on Solr and the promotion engine. Each one gets a decision: covered by Shopify itself, replaced by an app, rebuilt with Shopify Functions or a custom app, or retired. Modules that come with the SAP Commerce licence, such as Data Hub and the Integration Extension Pack, stop when you leave, so their work needs a new home.
B2B units become Shopify companies with locations, and customer-specific prices become B2B catalogues with payment terms, quantity rules and volume pricing. Budgets per cost centre and multi-step approvals are not standard Shopify objects; we solve them with an app or custom work, or leave them in SAP. See Shopify B2B.
SAP S/4HANA or SAP Business One stays the source of truth for prices, stock and invoices. For each data flow we define the owner, direction, frequency and error handling, and test it before launch. See Shopify ERP integration.
Shopify or Shopify Plus: which plan fits follows from the scan, not from your current licence. See what Shopify Plus adds for larger brands.
SAP Commerce URLs and SEO
Accelerator storefronts use URLs that end in /p/ plus a product code and /c/ plus a category code, often behind a language and currency prefix such as /en/EUR/. Composable Storefront, formerly Spartacus, uses /product/{code}/{name} and /category/{code} by default. On Shopify these become /products/ and /collections/, which makes the redirect map the most important SEO deliverable of the project:
We crawl every indexable URL, including category pages, brand pages, content pages and every language and currency prefix.
Because the old URLs contain the product and category code, we generate most redirects by rule from code to new handle, and check the URLs with the most traffic by hand.
Each old URL goes to its closest new page, never to the homepage by default.
Language and country versions move to Shopify Markets, with hreflang per market.
After launch we compare per template and folder, so a drop is found where it starts.
Shopify allows up to 100,000 redirects on its standard plans and 20 million on Plus, and only from URLs that return a 404, so the redirect map is built and tested before launch.
Approach
We work in fixed phases, so you know at every point what has been decided and what is still open:
Migration audit: data, extensions, B2B setup, CMS content, URLs, the S/4HANA link and processes, with scope and risks per decision.
Solution design: Shopify or Shopify Plus, data model, markets, B2B and the role of apps versus custom work.
Design and build, delivered in reviewable parts.
Trial migrations with real data, to measure completeness and duration.
QA on real processes: orders, payments, ERP sync, B2B ordering, returns and tracking.
Cutover with data freeze, final sync and redirects, followed by monitoring after launch.
Plan backwards from your peak. To sell on Shopify on Black Friday 2027 (26 November), we count six weeks for the scan, four for scope, about twenty for build, migration and testing, and six for launch and hypercare, followed by a code freeze from early November. In practice: the decision has to be made in February 2027.
We migrate in three runs, never one: a dry run in a development store to find fields that arrive empty, a dress rehearsal with the full data set to time the import, and a delta run after the freeze. After launch our hypercare runs 90 days, starting with daily checks of orders per hour, checkout conversion, failed payments per method, 404s and support tickets.
Brands we moved to Shopify Plus
Planning to leave SAP Commerce?
Tell us which SAP Commerce version and storefront you run, whether you sell B2B, how the shop connects to S/4HANA or another ERP, and your timing. We reply with a first view on scope, risks and the route to Shopify, and suggest a short call to walk through it.
