Migrating to Shopify from SAP Commerce Cloud

Baseline scope covers the product catalog and variants, classification attributes, categories mapped to collections, media, price rows, customer records, a prioritized window of order history, CMS content, navigation and available SEO metadata. Exact item types, field mappings and record counts are confirmed during Discovery and documented in the SOW.

We export through ImpEx, Backoffice exports and the Commerce Cloud APIs, working against the online catalog version rather than staged so the dataset matches what customers actually see. Where hotfolders or Data Hub feed the platform from an upstream system, we usually source directly from that system instead, since it produces cleaner data than re-exporting from Commerce.

Classification classes and classification attributes become Shopify metafields and metaobjects with defined types, so faceted filtering and spec tables survive. Variant product types map to Shopify variants where the axis count allows; beyond Shopify’s variant ceiling we model the family as a metaobject-driven product group so selection and inventory still behave correctly.

Base price rows migrate as Shopify prices with customer-specific pricing moved into Shopify Plus B2B catalogs and price lists. SAP’s rule-based promotion engine has no one-to-one equivalent, so we inventory active rules in Discovery and rebuild them with Shopify Functions, native discounts or Scripts, and flag any rule that can’t be reproduced before you commit to scope.

Content catalogs, content slots and CMS components are mapped to Shopify pages, sections and metaobjects so marketing keeps modular, editable layouts. Editors move from SmartEdit to the Shopify theme editor, which is a meaningful simplification. Most teams stop needing a developer for routine content changes.

It changes the front end more than the data. A Spartacus storefront can be replaced with a Shopify Online Store 2.0 theme, or you can stay headless on Hydrogen and the Storefront API if you have a real reason to. We document the tradeoffs on performance, editorial control and ongoing developer cost in Discovery rather than assuming headless carries over.

SAP B2B unit hierarchies, cost centers, budgets and approval flows map to Shopify Plus B2B Companies, Locations, Catalogs and payment terms, with approval gates implemented through Shopify Flow or a custom app where native primitives stop short. We document required wholesale behavior in Discovery and only commit to what Shopify can actually enforce.

Quote-to-cart flows are common in SAP B2B and are not native to Shopify. We scope them explicitly, usually as a vetted B2B quoting app, a Shopify Plus draft order workflow, or a custom app that writes back to your ERP or CPQ system of record.

We build a full URL map and 301 redirect plan for product, category and content URLs, including SAP’s product-code-based paths and any legacy patterns still earning traffic. Metadata migrates where available, and we run pre-launch and post-launch crawls to remediate 404s, confirm canonicals and verify hreflang for multi-locale sites.

Customer records migrate. Password hashes do not port between platforms, so we migrate accounts and trigger a secure password reset or login invitation flow. For B2B, contact-to-company assignment is migrated so buyers land in the right company account on first login.

Yes, scoped in Discovery. Most clients choose a rolling 12–24 month window. We plan for order number preservation, tax and accounting reconciliation, and returns mapping so finance and support aren’t left with a gap on day one.

Existing IDoc, CPI and Data Hub flows are re-pointed at Shopify through middleware or a lightweight proxy app that normalizes payloads, manages rate limits and provides logging and reconciliation. Inventory, pricing, order and customer sync responsibilities are defined explicitly in the SOW, including who owns error handling.

Shopify Search & Discovery covers standard faceting and synonyms using the metafields we migrate. Catalogs with heavy attribute-driven filtering or large SKU counts typically warrant a dedicated search app, which we benchmark against your current Solr behavior during Discovery rather than after launch.

Shopify’s checkout is SaaS-managed with defined extension points. Branding, supported configuration and Checkout Extensibility work are included; deep server-side checkout logic is scoped separately and implemented only where Shopify Plus allows it. We identify anything unsupported in Discovery so it doesn’t surface at UAT.

It removes SAP licensing, the CCv2 infrastructure line and most of the Java development overhead that biannual SAP releases require. Shopify Plus platform fees, apps and any custom app maintenance replace them. We build a side-by-side TCO comparison during Discovery so the comparison is yours, not ours.

Timeline depends on catalog complexity, integration count and B2B requirements. Most enterprise engagements target 6 months, with heavily integrated or multi-market programs running 6–9 months. Discovery produces a firm schedule.

Phased delivery: Discovery, Design and Development, QA and UAT, Launch, and hypercare. Launch readiness criteria, cutover steps and rollback contingencies are defined in the SOW, and hypercare plus operational training are included so your team can run the storefront without us.

Java extension code that can’t reasonably be replicated, unsupported checkout engine modifications, fully custom theme builds without separate agreement, large-scale BI or data warehouse replacement, and ongoing SAP maintenance. Anything out of scope is documented and handled via Change Order.

Contact Fyresite to begin Discovery. Discovery inventories your item types, extensions, integrations and B2B rules, confirms export feasibility and acceptance criteria, and delivers a firm scope, timeline and commercial proposal.