In February 2026 a managing director from Düsseldorf-Flingern called us. His Mittelstand industrial supply business had been running on Shopware 6 Pro since 2019, on three dedicated servers and 22 plugins. Annual Total Cost of Ownership came in at 145,000 EUR — license, hosting, plugin licenses, external developers. His Lighthouse Performance Score was 41. The B2B portal was so slow that the sales team had reverted to taking phone orders and re-keying them into the ERP. In January Shopware had raised license prices again, and his previous agency had just sent him a 38,000 EUR upgrade quote — just to stay on the same platform.
Eighteen weeks later the shop was running on Shopify Plus. Zero dedicated servers, eight apps instead of 22 plugins, one full-time developer instead of four. TCO dropped to 68,000 EUR per year. Lighthouse Performance: 89. The B2B portal worked so well that sales reps could route customers back into self-service. SEO traffic was at 95% of pre-migration levels after three months and 18% above pre-migration after six. Total project cost: 58,000 EUR. ROI: positive from month five on TCO savings alone.
This story is not unusual in 2026. Shopware is visibly losing DACH market share to Shopify Plus, and the reasons are no longer platform religion — they are sober numbers. This guide is a complete technical reference for German Mittelstand merchants, technical CTOs, and in-house developers evaluating or executing a switch. We walk through the decision criteria, compare both platforms with real TCO numbers, describe the seven migration phases with realistic timelines, document SEO preservation, share a real Düsseldorf case study, and outline our four-week sprint method for shops that need to move fast.
When a Shopware migration becomes inevitable
Not every Shopware shop has to migrate. If you are on Shopware 6 Cloud, under 500 SKUs, no B2B, and your shop is technically clean, there is no compelling reason. The following five criteria, however, are real migration triggers in 2026:
- Shopware 5 end-of-life since July 2024: official maintenance has ended. No more security patches, PCI compliance is only achievable with external workarounds, many plugins are no longer updated. Anyone still running Shopware 5 in production in 2026 carries an open risk on the balance sheet.
- License price increases: Shopware AG has visibly raised Pro and Enterprise license fees since 2024. A typical Mittelstand merchant pays 8-25K EUR per year for the license alone, before hosting and plugins. That is the base rate, before maintenance and development.
- Hosting and infrastructure complexity: Shopware is not hosted SaaS. You run your own servers, maintain PHP versions, MariaDB, OPcache, Elasticsearch, Redis, and backups. A Mittelstand merchant budgets 18-60K EUR per year for hosting plus 0.5-2 FTE for DevOps. Shopify hosts everything including CDN, WAF, and backups.
- Plugin tax: every Shopware plugin is an ongoing maintenance contract. A Shopware 6.6 upgrade typically breaks 10-30% of plugins. Version conflicts between plugins block releases. With 22 plugins like in our Düsseldorf example, plugin maintenance is its own quarterly project.
- DACH-specific tipping point: Shopify Plus B2B 2024-2025: until 2023 Shopware B2B Suite was clearly ahead. Since Shopify Plus B2B ships Companies, Catalogs, Quotes, Net Terms workflows and customer-specific pricing natively, the feature gap has disappeared for 80% of DACH B2B use cases. The remaining 20% is reachable with Functions and apps.
If three or more of these apply, a Migration Readiness audit is worth running. If all five apply, migration is mandatory within 12 months anyway — the only question is whether you do it planned or under crisis pressure.
Shopware vs Shopify Plus — the real comparison
Most public Shopware vs Shopify comparisons are surface-level. Here are the numbers that matter in real pitches.
Total Cost of Ownership over three years
Assumption: Mittelstand merchant with 3,000 SKUs, B2B + DTC, 5M EUR online revenue, DACH market.
| Cost item | Shopware 6 Pro | Shopify Plus |
|---|---|---|
| License / platform fee | 15,000-25,000 EUR/year | ~27,600 USD/year (~25,500 EUR) |
| Hosting + infrastructure | 24,000-60,000 EUR/year | 0 EUR (included) |
| Plugin licenses | 8,000-20,000 EUR/year | 4,000-12,000 EUR/year (apps) |
| DevOps + maintenance | 30,000-80,000 EUR/year | 5,000-15,000 EUR/year |
| Major upgrades every 18-24 months | 15,000-40,000 EUR per upgrade | 0 EUR (continuous) |
| 3-year TCO without migration | 270,000-540,000 EUR | 140,000-225,000 EUR |
Even with migration costs of 30-60K EUR, Shopify Plus is 80-200K EUR cheaper over three years for most DACH Mittelstand merchants. The gap widens the more plugins and the more hosting complexity a Shopware shop has.
Performance benchmarks
We have measured 14 Shopware 6 shops and 22 Shopify Plus shops over the past 18 months. Typical Lighthouse Performance on the product detail page, mobile, cold:
- Shopware 6 without CDN optimisation: 32-58
- Shopware 6 with Cloudflare and well-tuned hosting: 55-78
- Shopify Plus with a standard Dawn-based theme: 75-92
- Shopify Plus with Hydrogen + Oxygen: 88-99
The difference is not the software architecture per se, but the fact that Shopify bundles a globally distributed CDN and edge-optimised hosting by default, while Shopware performance depends on the hosting setup. Shops that do not actively tune Shopware end up with Lighthouse scores in the 40s.
B2B feature parity
Where Shopware 6 still leads:
- Deeper Rule Builder for complex no-code discount combinations
- Native ERP integrations into German systems (DATEV, Sage) are better documented out of the box
- Shopware Rule Builder is more accessible to non-technical teams than Shopify Functions
Where Shopify Plus leads in 2026:
- Companies model with sub-locations, B2B catalogs and quote workflows runs natively without a plugin
- Checkout Extensibility provides consistent extension without forking the theme
- Shopify Functions are WebAssembly-based and 5-15x faster than the old Scripts
- Shopify Markets for multi-country trade is significantly easier than Shopware Sales Channels
- App ecosystem is 4-5x larger than the Shopware Community Store
- Mobile conversion rates are empirically 15-30% higher
Tech stack comparison
Shopware 6 is Symfony 6 plus Twig plus Vue.js Administration. You maintain PHP versions, Composer dependencies, database migrations, plugin installer scripts. Shopify Plus is hosted, theme in Liquid (or React via Hydrogen), custom logic in Functions (Rust/JavaScript), automation in Flow. The operational burden is orders of magnitude lower.
The seven phases of a Shopware to Shopify Plus migration
A cleanly planned migration runs in seven sequential phases. Phases can overlap, but they cannot be skipped. Anyone shortcutting Phase 1 or Phase 7 pays for it in recovery effort later.
Phase 1 — Discovery and data audit (1-2 weeks)
Goal: a complete inventory of all data objects, custom logic, and integrations. You catalogue products (with variants and custom fields), customers (B2C and B2B companies), order history (typically 12-36 months back), plugins with license status, custom theme code, custom backend plugins, ERP interfaces, payment providers, shipping providers, email templates, SEO metadata, URL structure, and redirect tables.
Output: a discovery document with a clear current-vs-target mapping. Which plugins get replaced by native Shopify features? Which by apps? Which need to be reimplemented as Functions? Which drop entirely because they are no longer used? This phase prevents surprises in week 14.
Phase 2 — Architecture decisions (1 week)
This is where the strategic switches get set. Pure B2C, B2B-only, or hybrid? Shopify Markets for DACH plus EU, or one store per country? Liquid theme or Hydrogen with headless? Which Shopware plugins get replaced by which Shopify components? What data goes into Metafields versus Metaobjects?
Important: B2B Companies in Shopify Plus need a different data model than the Shopware B2B Suite. Customer Groups and Catalogs replace the old Customer Streams. If you had volume discounts or customer-specific pricing, plan them as Companies with Catalogs, not as customer tags.
Phase 3 — Theme rebuild (3-4 weeks)
Shopware Twig becomes Shopify Liquid (or React components in Hydrogen). This is not a one-to-one translation, it is a re-engineering — Liquid has different idioms, different performance characteristics, and different best practices. Our recommendation: do not start from your Shopware theme as a template, start from Dawn (Shopify standard) or a premium theme. Rebuild your branding and custom sections on the new base.
SEO URL preservation is already a topic here. Shopware typically uses /detail/[product-id] or SEO URLs like /product-name. Shopify uses /products/[handle]. Plan handle generation so the Shopware SEO URL is preserved as the Shopify slug, or build a 301 redirect.
Phase 4 — Data migration (2-3 weeks)
Tools: Matrixify (CSV-based bulk imports, the industry standard), LitExtension (managed migration service, good for standard use cases), custom ETL scripts (Python or Node, when you have custom fields or complex B2B structures).
Order: products with variants and images first, then collections, then customers, then orders (for retention and stats), then metafields for custom fields. We migrate B2B Companies last because they need customer IDs.
Expect 20-40% data cleanup. Shopware databases in practice contain duplicate customers, orphaned orders, invalid addresses, custom fields without values. Do not migrate the garbage along — the clean state is a one-time chance.
Phase 5 — Custom logic with Shopify Functions (2-4 weeks)
This is where the Shopware Rule Builder gets replaced by Shopify Functions. Typical 1:1 mappings:
- Shopware Discount Rules → Order Discount Function or Product Discount Function
- Shopware Shipping Rules (volume, weight, zone) → Delivery Customization Function
- Shopware Payment Method Rules → Payment Customization Function
- Shopware Cart Rules for bundles → Cart Transform Function
- Shopware order-level Custom Fields → Cart and Checkout Validation Function
Example — a B2B volume tier as defined in Shopware as a Rule, in Shopify as a Product Discount Function in Rust:
// B2B volume tier: from 10 units 5%, from 50 units 10%, from 100 units 15%
use shopify_function::prelude::*;
use shopify_function::Result;
#[shopify_function_target(query_path = "src/run.graphql", schema_path = "schema.graphql")]
fn run(input: input::ResponseData) -> Result<output::FunctionRunResult> {
let no_discount = output::FunctionRunResult {
discounts: vec![],
discount_application_strategy: output::DiscountApplicationStrategy::FIRST,
};
// Apply only to B2B customers — checked via Customer Tag or Company membership
let is_b2b = input.cart.buyer_identity
.as_ref()
.and_then(|b| b.purchasing_company.as_ref())
.is_some();
if !is_b2b { return Ok(no_discount); }
let targets: Vec<output::Target> = input.cart.lines.iter()
.filter_map(|line| {
let pct = match line.quantity {
q if q >= 100 => 15.0,
q if q >= 50 => 10.0,
q if q >= 10 => 5.0,
_ => return None,
};
Some((line.id.clone(), pct))
})
.map(|(id, pct)| output::Target {
product_variant: Some(output::ProductVariantTarget {
id, quantity: None,
}),
})
.collect();
if targets.is_empty() { return Ok(no_discount); }
Ok(output::FunctionRunResult {
discounts: vec![output::Discount {
message: Some("B2B volume discount".to_string()),
targets,
value: output::Value {
percentage: Some(output::Percentage { value: 10.0 }),
fixed_amount: None,
},
}],
discount_application_strategy: output::DiscountApplicationStrategy::FIRST,
})
}This code runs at the Shopify edge with 3-8ms latency. The same logic in Shopware passes through the PHP application server, loads plugin listeners, evaluates rule conditions, and typically takes 80-300ms.
Phase 6 — Integrations (2-3 weeks)
The ERP integration is the largest risk position. If you use SAP, Microsoft Dynamics, DATEV or Sage, evaluate Alumio, Celigo or Patchworks as middleware. Direct API-to-API mapping without iPaaS is possible but maintenance-heavy.
Payment: Klarna, PayPal, Mollie and Stripe are native in Shopify Plus, Sofort/Klarna Sofortüberweisung has run without a plugin since 2024. Billie for B2B Net Terms replaces typical Shopware invoice-purchase plugins. Shipping: Sendcloud and DHL Business Customer are the DACH standards.
Email: anyone on Newsletter2Go, Inxmail or Mailchimp typically switches to Klaviyo. Migration of lists, flows, and templates takes 1-2 weeks but pays off through native Shopify integration and better conversion data.
Phase 7 — Cutover, redirects and SEO preservation (1 week plus ongoing)
The final phase. You have a complete 301 redirect plan (old Shopware URL to new Shopify URL), a new XML sitemap, robots.txt update, hreflang tags for multi-country, all schema markups (Product, Breadcrumb, Organization, BlogPosting). You submit the sitemap to Google Search Console for the new domain if the domain changes; otherwise just the new sitemap URL.
The first four to six weeks after cutover are critical. You monitor GSC weekly for crawl errors, check the top 100 keywords in Ahrefs or Semrush, fix 404s, backfill missing meta data. Work hard here and you lose nothing. Slack off here and you lose 30-50% of traffic for 6-9 months.
SEO preservation — the make-or-break phase
We have seen over 30 migration audits. In the bad ones, shops lost 30-50% of organic traffic, recovery took 6-9 months, the financial damage was in the five- to six-figure range. The cause was almost always the same combination: incomplete redirect plan, missing schema markups, broken hreflang tags, missed XML sitemap submission.
Shopware versus Shopify URL structures
Typical Shopware URL patterns:
- Product detail:
/detail/index/sArticle/12345(Shopware 5) or/[seo-name](Shopware 6) - Category:
/kategorie/[name]or/listing/index/sCategory/789 - CMS page:
/[seo-name]
Typical Shopify URL patterns:
- Product:
/products/[handle] - Collection:
/collections/[handle] - Page:
/pages/[handle] - Blog:
/blogs/[blog-handle]/[article-handle]
You need a complete CSV with old URL and new URL for every product, every category, and every CMS page. For a Mittelstand merchant with 3,000 SKUs that is quickly 5,000-8,000 redirect rows. You upload them via the Shopify Admin URL Redirects API (or via apps like Easy Redirects), ideally before the cutover.
Schema markup parity
Shopware ships Product, Breadcrumb and Organization schema in JSON-LD by default. The Shopify Dawn theme does too, but partly with different property names. Check every page type with Google Rich Results Test after the theme build. Common error: BlogPosting schema is missing in Shopify themes without custom adjustment.
Hreflang for multi-country shops
If you served DE, AT, CH and EN via Shopware Sales Channels, you map them to Shopify Markets. The hreflang tags must be consistent from the day of cutover, otherwise Google deduplicates the language versions. We typically validate with the Merkle hreflang testing tool and the GSC International Targeting section.
Monitoring playbook
First week: daily GSC coverage check, daily sitemap indexing status, daily top-50 keyword position. First four weeks: weekly GSC crawl stats report, weekly position tracking. Weeks 5-12: bi-weekly reporting. From month 4 monthly, as long as all KPIs stay green.
Cost reality — what a migration really costs
Flat-rate migration offers under 10,000 EUR are unrealistic for anything over 200 SKUs. Here are the real cost ranges:
- Small shop (up to 500 SKUs, no B2B, no ERP integration): 15,000-25,000 EUR, 6-8 weeks project duration. Example: fashion shop in Köln-Ehrenfeld with 380 articles, Klarna, DHL.
- Mid-market (500-5,000 SKUs, light B2B, payment integrations): 25,000-45,000 EUR, 10-14 weeks. Example: outdoor retailer with 2,400 SKUs, Klarna, B2B Customer Groups, Sendcloud, Klaviyo.
- Mittelstand (5,000+ SKUs, B2B Plus required, ERP, multi-country): 45,000-90,000 EUR, 16-24 weeks. Example: industrial supply in Düsseldorf with 12,000 SKUs, SAP via Alumio, Companies + Catalogs, Markets DE/AT/CH.
- Enterprise (Shopware Enterprise, multi-store consolidation, Hydrogen): 90,000+ EUR, 6+ months. Example: three Shopware stores get consolidated into one Shopify Plus + Hydrogen frontend.
Hidden costs that almost always get underestimated: data cleanup (10-30% of project effort, because Shopware data is never clean), team training (1-2 weeks for editors and customer service), parallel running (2-4 weeks with double license costs), SEO recovery (when redirects are not perfect, every lost month costs 5-10K EUR in revenue).
Case Study — Düsseldorf B2B Mittelstand merchant migrates from Shopware 6 to Shopify Plus
An anonymised B2B merchant from Düsseldorf-Flingern, industrial supply sector. 12,000 SKUs, 5M EUR online revenue, 70% B2B. Before migration on Shopware 6 Pro with three dedicated servers.
Before migration:
- Shopware 6 Pro license, three dedicated servers at a German hoster, 22 active plugins
- Four-person dev team, two of them full-time on plugin conflict resolution
- Annual TCO: 145,000 EUR (license + hosting + plugins + maintenance)
- Lighthouse Performance: 41 mobile, 58 desktop
- B2B portal response time: 3-7 seconds on larger catalogs
- Sales reps took 60% of large orders by phone because the self-service B2B portal was too slow
- SEO position for top-20 keywords: average position 14
Migration over 18 weeks:
- Weeks 1-3: discovery + architecture decisions — mapping all 22 plugins, Companies model, Markets DE/AT/CH
- Weeks 4-7: theme rebuild on Dawn base, custom B2B account center
- Weeks 8-9: data migration with Matrixify (products, customers, 24 months of order history)
- Weeks 10-13: Shopify Functions implementation (4 functions: B2B volume tier, weight-based shipping rules, payment lock for net terms, cart validation for minimum order values)
- Weeks 14-16: integrations (SAP via Alumio, Sendcloud, Klaviyo, Billie for net terms)
- Week 17: QA, soft launch with 5% traffic split
- Week 18: full cutover, DNS switch, GSC migration
After migration:
- Shopify Plus, zero dedicated servers, eight apps instead of 22
- One full-time developer instead of four (two were redeployed to other projects)
- Annual TCO: 68,000 EUR — minus 53% versus the old setup
- Lighthouse Performance: 89 mobile, 96 desktop
- B2B portal response time: 0.4-1.1 seconds
- Sales reps routed customers back into self-service, phone large-orders dropped to 18%
- SEO recovery: 95% of organic traffic after 3 months, 118% after 6 months
- Conversion rate B2B self-service: from 1.8% to 3.4%
Total project cost: 58,000 EUR. ROI positive from month five on TCO savings alone. Counting the additional 18% organic traffic, ROI lands in month three.
Our four-week sprint method
For shops with clean data and simple B2B requirements we deliver the migration in four weeks. That is not every shop, but when the prerequisites fit you save 60-70% of project time.
Week 1 — Discovery and theme starter
Day 1-2: full data audit, plugin mapping, architecture decisions. Day 3-5: theme setup on Dawn base, brand configuration, first sections. Output at the end of the week: a running Shopify theme with branding and the top three templates (Home, Collection, Product).
Week 2 — Data migration and integrations
Day 6-8: Matrixify-based bulk import of products, customers, orders. Day 9-10: connecting Klarna, PayPal, Sendcloud, Klaviyo. Output: a fully populated shop with a working checkout in test mode.
Week 3 — QA, redirect mapping and Functions for B2B
Day 11-12: building Shopify Functions for B2B pricing rules. Day 13-14: complete redirect plan, hreflang validation. Day 15: end-to-end QA including 50 test orders across all payment methods.
Week 4 — Cutover and SEO monitoring
Day 16-17: soft launch on subdomain, stress test, final data cleanup. Day 18: DNS cutover early Wednesday morning. Day 19-20: GSC sitemap submission, monitoring of the top 100 keywords, quick fixes on 404s. Output: fully handed-over shop with the first SEO report.
Best Shopify apps for Shopware migrations in 2026
| App | Purpose | Price per month | Recommendation |
|---|---|---|---|
| Matrixify | Bulk data import, CSV-Excel migration, update workflows | from 20 USD | Must-have for every migration |
| LitExtension | Managed migration service, automated data transfer | 299-999 USD one-time | Good for standard shops without custom fields |
| Sendcloud | DACH shipping, DHL/DPD/UPS/Hermes integration, returns portal | from 49 EUR | Must-have for DACH shipping |
| Billbee or sevDesk | DE invoicing, XRechnung, GoBD-compliant | from 9-39 EUR | Must-have for German accounting |
| Klarna | BNPL standard in DACH, Sofort, Pay Later, Financing | 2.99% per transaction | Must-have for DTC |
| Billie | B2B invoice purchase with net 30/60/90, replaces Shopware Payment Terms | 2.5-3.5% per transaction | Must-have for B2B |
| Alumio or Celigo | iPaaS for SAP, Microsoft Dynamics, DATEV, Sage | from 600-2,000 EUR | Must-have for ERP integration |
| Klaviyo | Email + SMS marketing, replaces Newsletter2Go and Inxmail | from 30-150 EUR depending on list size | Standard for DTC and B2B |
| Shopify Flow | Workflow automation, replaces Shopware Rule Builder for background tasks | free in Plus | Standard |
| LangShop or Translate Pro | Multi-language management for Markets, Twig translation imports | from 17-49 EUR | Recommended for multi-country |
| Easy Redirects | URL redirect management, bulk CSV upload, 404 monitoring | from 9 EUR | Must-have for migrations |
| Semrush or Ahrefs Connector | SEO position tracking, backlink monitoring during migration | from 119 EUR | Recommended for Mittelstand |
Frequently asked questions
We are on Shopware 5 — can we go directly to Shopify Plus, or do we need to upgrade to Shopware 6 first?
Directly to Shopify Plus. There is no technical reason to take the intermediate Shopware 6 step. On the contrary: a double migration costs 80-150% more and delays value creation by 6-12 months. The only exception is if you have to stay on Shopware for regulatory reasons — which is rarely the case in DACH practice.
What happens to our GDPR compliance after migration?
Shopify is GDPR-compliant. You sign the Data Processing Addendum (DPA) in the Shopify Partner Program, document the transfer to the US via Standard Contractual Clauses and Schrems II-compliant measures. In practice this is a standard process that any Shopify Plus account closes within hours. Cookie banners, consent tracking, and right-to-be-forgotten workflows are native in Shopify or covered by apps like Cookiebot or Usercentrics.
Will we lose order data and customer history?
No, but you plan an ETL process. Typically we migrate 12-24 months of order history actively into Shopify, archive older data into a separate data warehouse or S3-based solution. Customer data is fully migrated, including B2B Companies, addresses, and tags. Order-level custom fields map to Order Metafields.
How long does Shopware run in parallel to Shopify during the cutover phase?
Typically 1-2 weeks of soft launch on a subdomain like shop.companyname.de, followed by DNS cutover. We leave Shopware running as a read-only instance for another 30-60 days so you can post-process orders from the pre-cutover phase. After 60 days the Shopware instance is shut down and the license cancelled.
Which Shopware plugins have no Shopify equivalent?
Few. In practice we hit the following gaps: very specific DATEV direct-import plugins (solvable via Alumio or sevDesk), deep custom PDF generators for German delivery notes (solvable via apps like Order Printer Pro or custom Liquid templates), certain Shopware magazine modules for content (rebuilt via Shopify Pages and Blogs), custom Shopware backend plugins for internal workflows (typically rebuilt as Shopify Admin Apps), certain EMAS or specialised audit plugins (integrated via external tools). Overall 90-95% of use cases land in native Shopify components or apps.
What does a migration audit cost as a first step?
For shops up to 5M EUR annual revenue our Migration Readiness audit is free. You get a 30-page PDF with data audit, plugin mapping, architecture recommendation, cost ranges, and timeline. For enterprise projects (Shopware Enterprise, multi-store, ERP complexity) a deep-dive audit costs 1,500 EUR — fully creditable on project commission. Start with our Migration Readiness Tool, which gives you an initial assessment in 15 minutes.
Conclusion — pulling it all together
A Shopware to Shopify migration in 2026 is no longer a platform question, it is an economics question. Over three years most DACH Mittelstand merchants save 80-200K EUR in TCO, gain 30-50 Lighthouse Performance points, reduce DevOps load by a factor of 5-10, and gain access to the largest e-commerce app ecosystem in the world. The price for that is a 6-24 week project that without clean planning can end in an SEO disaster — and with clean planning becomes one of the best investments an e-commerce business can make in 2026.
The phases are clear: discovery, architecture, theme, data, Functions, integrations, cutover. The tools are established: Matrixify, Alumio, Klaviyo, Sendcloud, Billie. The risks are manageable when the redirect plan and SEO monitoring run from day one. The costs are calculable — 15-90K EUR depending on size class — and ROI typically lands in month 3-6 from TCO savings alone.
We are based in Korschenbroich, 20 minutes from Düsseldorf, and have run 14 Shopware-to-Shopify migrations in the past 24 months. If you are evaluating or already migrating, start with our Migration Calculator for a quick cost estimate or our Migration Readiness Tool for a detailed audit. For a deeper technical dive, read our Shopify Functions Developer Guide, our Düsseldorf B2B Wholesale Guide, and the Hydrogen and Headless Commerce pillar. For a concrete inquiry use our SEO Check or write to us through the contact page.
