The Adobe Commerce to Shopify Plus migration is a real and increasingly common move. The motivations vary, faster development cadence, lower operational burden, alignment with internal team capability, or strategic preference, but the work to execute it does not. A successful migration requires three parallel workstreams: data migration, catalog and merchandising migration, and SEO preservation. Skip any of them and the launch is messy. Run all three with discipline and the migration is mostly mechanical.
This piece walks through the playbook Bemeir uses when supporting Adobe Commerce merchants moving to Shopify Plus. The framework below is the version that consistently produces clean migrations on multi-million-dollar B2B and B2C stores; the patterns are not novel, but the discipline to apply them is what determines outcomes.
Why this migration is different from M1 to Adobe Commerce
The Magento 1 to Adobe Commerce migration is supported by Adobe’s Data Migration Tool, which handles most of the structured data transfer mechanically. There is no equivalent first-party tool for Adobe Commerce to Shopify Plus. The work has to be done with custom scripts, the Shopify Admin API, and a discipline-driven approach to data transformation.
The data models are also more different than they look. Adobe Commerce uses EAV (Entity-Attribute-Value) for products with arbitrary custom attributes. Shopify uses a fixed product schema with metafields for additional attributes. Adobe Commerce supports complex configurable products with sometimes hundreds of variants; Shopify supports up to 100 variants per product with the standard plan and a higher cap on Plus. Adobe Commerce supports customer groups with arbitrary group hierarchies; Shopify Plus B2B uses companies. Every one of these differences requires deliberate mapping.
Workstream 1: Data migration
The data migration covers customers, orders, and any persistent state. The execution sequence:
Customer migration. Export customer records from Adobe Commerce (admin export or direct database query). Map to Shopify customer schema. Import via Shopify Admin API. The mapping is straightforward for standard fields (email, name, addresses); custom attributes need to be mapped to customer metafields.
Password handling. Adobe Commerce password hashes do not transfer to Shopify. Customers will need to reset passwords on first login to the new store. Plan a re-engagement email campaign timed with launch to walk customers through the reset.
Order history. Order history migration is optional but valuable for customer-facing order lookup. Two approaches: import historic orders into Shopify (preserves customer-facing order history but increases Shopify data load) or maintain a read-only archive of the Adobe Commerce orders accessible from the customer account section. The decision depends on the volume and the customer expectation.
Customer groups and tier mappings. Adobe Commerce customer groups map to Shopify Plus B2B companies. Each Adobe Commerce customer group becomes either a Shopify B2B company (for B2B stores) or a Shopify customer tag with associated price list (for stores not using full B2B). The mapping is opinionated and requires merchant input on how each group should land.
Subscription data. If the Adobe Commerce store uses subscriptions (ReCharge, Bold Subscriptions, custom modules), the subscription state migration is its own project. Most subscription extensions on Shopify can import customer subscription data; the format varies and the work is often manual.
Workstream 2: Catalog and merchandising
The catalog migration is where the biggest schema differences live.
Product schema mapping. Adobe Commerce products have arbitrary attribute sets. Shopify products have a fixed set of fields plus metafields for additional data. Build a mapping document:
| Adobe Commerce concept | Shopify equivalent | Notes |
|---|---|---|
| Simple product | Product (single variant) | Direct mapping |
| Configurable product | Product with variants | 100 variant cap; very large configurables need splitting |
| Bundle product | Product with bundling app | Shopify does not have native bundles |
| Grouped product | Product collection or custom build | Different model entirely |
| Virtual product | Product (no shipping) | Direct mapping |
| Downloadable product | Digital download app | Native Shopify support is limited |
| Gift card | Gift card (native) | Direct mapping |
| EAV custom attribute | Metafield or tag | Decision per attribute |
| Category | Collection | Direct mapping conceptually |
| Tier prices | Price list per company | B2B feature |
Custom attribute mapping. Every Adobe Commerce custom attribute becomes either a Shopify metafield, a tag, a collection rule, or it is dropped. The decision depends on how the attribute is used:
- Used for filtering on storefront: Shopify metafield with filtering enabled
- Used for merchandising rules: Tag or collection rule
- Used for admin reference only: Metafield (lower priority)
- Used for nothing: Drop
The audit of which attributes are actually used is essential. Migrating 200 attributes that nobody uses is wasted work.
Image and media migration. Adobe Commerce media files (product images, category images, CMS media) need to be uploaded to Shopify. The Admin API supports image upload; the practical approach is a script that reads the Adobe Commerce media library and posts each image to the corresponding Shopify product. Image dimensions, alt text, and ordering need to be preserved.
Inventory and stock. Adobe Commerce inventory (with or without MSI) maps to Shopify inventory at the location level. For single-location merchants, this is straightforward. For multi-location or multi-warehouse merchants, the Shopify location model needs to be set up first, then inventory mapped per location.
Pricing. Standard pricing maps directly. Tier pricing on Adobe Commerce maps to Shopify Plus price lists per B2B company. Custom pricing logic (per-customer pricing, contract pricing) requires Shopify Plus B2B features and possibly custom Shopify Functions for complex cases.
Workstream 3: SEO preservation
The Adobe Commerce to Shopify Plus migration carries the same SEO risk as any replatform: URL changes, metadata changes, and structural shifts can leak organic traffic. The preservation discipline:
URL preservation strategy. Adobe Commerce default URLs (with `.html` suffix and category-path inclusion) differ from Shopify default URLs (path-based without suffix). The merchant has two options:
- Preserve Adobe Commerce URL patterns on Shopify via app or custom redirects. Shopify supports URL aliases and custom redirects via apps.
- Adopt Shopify default URLs and build comprehensive 301 redirects from old to new.
The second option is cleaner long-term; the first option is lower-risk for the launch window.
Redirect map. For every URL on the Adobe Commerce site, a corresponding redirect to the new Shopify URL. Build the redirect map during migration scoping; verify completeness with a pre-migration crawl. Implement redirects in Shopify via the URL Redirects feature (supports up to 100,000+ on Plus) or via a redirect app for high volume.
Metadata migration. Title tags, meta descriptions, canonical configuration, and structured data should be preserved or deliberately improved. Shopify metafields can hold product-level SEO metadata that should map from Adobe Commerce’s equivalent fields.
Internal linking. The information architecture of the new Shopify site should preserve the link patterns that gave the old site ranking signal. Header navigation, footer links, breadcrumbs, related products, and category linking all need consideration.
Structured data. Shopify themes typically ship with structured data for products and breadcrumbs; verify the Hydrogen build (if using Hydrogen) implements this correctly. Custom Adobe Commerce structured data (FAQ schema, review schema beyond what Shopify provides natively) needs to be reimplemented in the Shopify theme.
Sitemap and robots.txt. Submit the new Shopify sitemap to Google Search Console at launch. The robots.txt rules should be configured to match the Adobe Commerce baseline.
Pre-launch crawl, post-launch validation. Same as any migration: crawl Adobe Commerce comprehensively before the migration, crawl Shopify comprehensively after, compare URL by URL.
Launch sequencing
The clean launch sequence:
- Migration build complete on Shopify staging. All data imported, all flows tested.
- Comprehensive QA: every major page type loads, checkout completes, customer login works, search returns results, product variants display correctly.
- SEO preservation verified: redirects in place, metadata mapped, structured data validated.
- DNS cutover planned and announced.
- Final data sync (orders, customers, inventory between Adobe Commerce and Shopify in the launch window).
- DNS cutover during low-traffic period.
- Post-launch monitoring: every metric watched in real-time for the first 48 hours.
- Adobe Commerce kept in read-only archive mode for 90 days minimum for any rollback contingency or data verification needs.
The discipline to do this sequence in order is more important than any specific technical detail. The migrations that go badly are the ones where steps are compressed or skipped.
What this is worth
Adobe Commerce to Shopify Plus is not the right move for every merchant, but for the merchants who fit Shopify Plus B2B’s profile or who want lower operational burden, the migration can deliver meaningful ongoing savings: reduced engineering staffing, simpler hosting model, less time on platform operations. The migration cost is real (12-24 weeks for a typical mid-market store) but the post-migration economics often justify it.
The migration that goes well is the one that respects the data, catalog, and SEO workstreams as parallel disciplines, each with its own deliverables and its own sign-off criteria. The migration that goes badly is the one that treats SEO as a downstream consequence of the catalog work, or data integrity as an assumption rather than a verified state. Bemeir’s approach is to staff each workstream explicitly because the alternative consistently produces worse outcomes. The Shopify Plus migration documentation and the Shopify Admin API cover the technical machinery; the framework above is what bridges the machinery to a clean launch. The work is well-understood; the discipline to execute it is the only variable.
