One Shopware store can serve several markets, storefronts, and customer experiences. Your Shopify migration needs to account for all of them.
Whether you're on Shopware 5 or 6, we review your sales channels, languages, currencies, navigation, and business rules before planning the move. We then map these to Shopify and test the storefronts, product visibility, and SEO URLs to make sure everything works as expected.
or call 888-711-2347
Includes 60 days of free support after launch, so you’re not left on your own once the move is done.
Official Shopify Partner
Since 2015 · Shopify store migration, design and development. View profile ↗
Illustrative workflow, not a live project
Attention: 6 items need attention.
Is your store still on a version that no longer gets official updates?
Shopware’s own documentation says version 5 reached end of life in July 2024. No new features are coming, and the company points merchants to Shopware 6. You can buy third-party security cover from an independent initiative, but Shopware doesn’t provide it.
Staying on version 5 isn’t really a plan, so any way forward is a rebuild, either on Shopware 6 or on another platform. Price both. Going to Shopware 6 is a migration too.
Is the release calendar dictating your upgrade schedule?
Shopware publishes a release policy with several states, including maintained, extended support, security fixes only and end of life. Agency write-ups say older 6.x lines drop to security-only fixes through a plugin, and that dates can move because transitions follow major releases.
Find out which 6.x line you’re on and what’s next for it. Regular upgrades come with running a platform yourself, and every one means retesting your plugins and theme.
Is hosting getting more expensive as the store grows?
Agencies call Shopware 6 resource-hungry and say cheap shared hosting usually won’t cope, so they steer merchants toward specialised or managed hosting. Vendors set their own prices and the range is wide.
Put your full hosting and server upkeep next to the subscription for a managed platform. Shopware sells managed cloud options as well, so find out what your current setup already covers.
Do simple edits end up waiting on an agency or developer?
Shopware-focused agencies say most professional stores work with a development partner, since custom work falls outside the manufacturer’s support. Reviewers add that edits to core code make later updates harder.
Ask yourself how much of the daily work your own team can handle. Heavy customisation gives you power, but it brings partner fees and upgrade testing along with it.
Do plugins, hosting and developer time add up to more than the licence?
Agency cost guides say hosting, plugins, development and maintenance can pile up well past the licence fee, depending on your edition and how much you’ve customised. Those guides come from firms that sell services, so read the figures as estimates.
Work out your own yearly total covering licence or plan, hosting, plugins and partner hours. Then set it against a Shopify plan, apps and whatever development you’d still need.
Does every update mean fixing plugins and your theme?
Merchants and agencies describe retesting plugins and custom themes after each Shopware update, particularly after big changes within a release line. The effort depends on how many extensions and customisations you run.
List your extensions and mark which ones are maintained for current versions. For any that aren’t, ask whether a Shopify app or a built-in feature could take over.
Are support tickets slower than you’d like?
One review-focused write-up says many negative reviews are about slow support tickets and not the software itself, and that smaller merchants sometimes expect something simpler out of the box. Experiences vary.
Think about who you call when something breaks. It could be Shopware, your host, a plugin author or your agency. Having one contact for all of it may matter to you.
Pet supplies
Advance Pet Mart started on WooCommerce, but plugin and hosting problems kept getting in the way. We moved the store to Shopify, and they are very happy with the move. We also worked with them on design, SEO, AI SEO and marketing.
Visit the live store
Electronics & gaming retail
We moved City of Games from a broken OpenCart store to Shopify in four weeks, kept its look, rebuilt the features it had lost and protected its search rankings with 301 redirects.
Read the case study
We moved Contours Rx from BigCommerce to Shopify and redesigned the website with a sleek, user-friendly interface and enhanced product pages.
Visit the live storeData moved and storefront rebuilt. Right for stores that need both done on Shopify.
Priced after a free store review
A complex business moved with a proper plan. Built for large or heavily customized stores and the systems connected to them.
Quoted after discovery
Every migration includes redirects for your old URLs, your titles and descriptions carried over, and 60 days of free support after launch. Your Shopify plan, apps and other third-party costs aren’t part of the quote.
Variants and what they override
Options, metafields and filters
Menus and product listings
Behavior agreed up front
Layouts, files and pages
Content in each language
Accounts and company records
Imported or archived
Outcomes rebuilt
Flows rebuilt, then tested
Scoped on its own
A redirect map we test
How each item is handled and what we check before launch.
| Shopware | Where it goes in Shopify | What we check |
|---|---|---|
| Products & variants | Imported. The agreed products, variants, SKUs, stock and identifiers. | Inheritance, overrides, stock levels and valid combinations. |
| Properties & custom fields | Imported. Suitable options, metafields, metaobjects and filter inputs. | Clear labels, values and relationships, with no orphaned UUIDs. |
| Categories & dynamic groups | Rebuilt. The agreed navigation, collections and merchandising. | Static membership against the rule behavior you’ll want later. |
| Shopware | Where it goes in Shopify | What we check |
|---|---|---|
| Content, media & translations | Rebuilt. The agreed pages, sections, files and translated content. | CMS assignments, files, links and any missing translations. |
| Customers & B2B records | Imported. The agreed customer, company and location records. | Duplicates, addresses, permissions and separate proof of consent. |
| Shopware | Where it goes in Shopify | What we check |
|---|---|---|
| Orders & documents | Imported or archived. A supported historical import, or an archive you can reach. | Totals, items, links between records and no unintended actions. |
| Subscriptions & balances | Scoped separately. A planned transition, or the process stays where it is. | What your payment provider allows, and what is still owed. |
| Shopware | Where it goes in Shopify | What we check |
|---|---|---|
| Prices, rules & workflows | Rebuilt. The agreed behavior, using features, apps or development. | Customer eligibility, order totals and how events are handled. |
| SEO & channel URLs | Rebuilt. A destination map based on relevance, plus tested redirects. | Domains, language paths, canonicals and old redirects. |
Customer passwords, payment credentials, original payment transactions, identical order or invoice numbering and identical reports can’t be assumed to move across. Where it helps, source references can be kept through a supported method.
Some records are imported, some features rebuilt, some kept in an archive and some scoped separately. Your proposal says which is which.
How many storefronts, languages, currencies and markets.
Variant sets, properties, media and page layouts.
Advanced prices, Rule Builder and Flow Builder setups.
Company accounts, approvals, catalogs and quotes.
ERP, PIM, fulfillment and marketing connections.
The cut-off, domains, open obligations and reconciliation.
Your proposal keeps our project fee apart from the Shopify subscription, apps, themes, integrations and other outside costs. Price and schedule are confirmed once the review is done.
FreeA store review and quote before you hire us
60 daysFree migration support after launch, included in the project
Tell us what you run today and what you’d like to fix. We look at your channels, catalog and business rules first, then explain what moves, what gets rebuilt and what the project costs.
You don’t need technical knowledge, or even to know your version. There’s nothing to export and no logins to hand over at the start. We set up secure access later.
Every route means a rebuild
Whether the platform still fits
These are dates for particular versions. Shopware itself isn’t shutting down.
Last checked October 20, 2026 against Shopware’s Shopware 5 migration page ↗ and Shopware’s cloud documentation ↗.
Plenty of Shopware stores aren’t self-hosted. Shopware comes self-hosted, as SaaS or as PaaS, and each one divides up responsibility for servers, updates and security in its own way. How much upkeep you could save depends on your setup, your contract and the systems you keep.
Some storefronts can share records. Others need their own content, team or operations. We sort out which is which.
Translations, fallback content, localized navigation and assets. We list what exists for each locale and don’t assume it’s all there.
Currencies, customer groups, payment methods, shipping choices and the way each audience really buys.
Shopify Markets, B2B catalogs, sales channels or separate stores, judged one source channel at a time.
| Shopware channel | Proposed destination | Status |
|---|---|---|
| Main storefront · German · EUR | Primary market, main store | Agreed |
| Austria domain · German · EUR | Same market or its own domain | Review |
| Swiss storefront · CHF | Own market with its own prices | Review |
| Trade portal · net prices | B2B catalog or a separate store | Decide |
| Second brand · own catalog | Separate Shopify store | Assess |
| Headless or API channel | Not assumed to transfer | Scope first |
Shopify Markets, B2B catalogs, sales channels and separate stores each do different jobs, and none replaces a Shopware sales channel one for one. Your proposal names the destination for every source channel and says which system owns each record.
| In your Shopware store | What we review | How we decide the Shopify setup |
|---|---|---|
| Products & variants | Which combinations are valid, plus SKUs, stock and the values each variant inherits from its parent or overrides. | Products and variants that match what you actually sell, with each variant’s inherited and overridden values settled. |
| Properties & options | Which values a customer picks at purchase, and which only describe the product or power filters. | Choices a customer buys become options. Descriptive values become metafields and filter inputs, never extra variants. |
| Custom fields & related records | Each custom field, its label and the source UUIDs linking records to one another. | Metafields or metaobjects with relationships that mean something, instead of copied UUIDs pointing nowhere. |
| Media & related items | Images, downloads and the cross-selling links you want to hold onto. | Files and links attached to the right records in Shopify, then checked against the source. |
| Complex configurations | Personalization, component or bundle products and any other unusual buying requirement. | A native feature, an app or scoped development, picked for each requirement. |
The example on the right is made up for illustration and isn’t a client result. Your mapping comes from your own products and properties.
| Parent product inherited text & images | Merino Hoodie |
|---|---|
| Variant option purchasable | Size: S / M / L |
| Property filter only | Material: Merino |
| Variant override size L | €84.00 |
| Product | Merino Hoodie |
|---|---|
| Option | Size: S / M / L |
| Metafield & filter | Material: Merino |
| Variant L | €84.00 |
Material stays a filter and doesn’t become a second option, and size L keeps its own price.
Shopify currently supports up to 2,048 variants and three options per product (checked October 2026). We still test your chosen theme, apps and import route, since each handles large variant sets in its own way. A customer input field, like engraving text, doesn’t create a stocked variant or add a charge by itself.
We go through the layouts, content and custom elements, then agree with you what gets recreated.
Custom elements are listed first.CMS layouts, dynamic values and where they’re assigned across categories, products and landing pages.
Each assignment checked page by page.Menu entries, content pages and product listings are pulled apart so each ends up in the right part of Shopify.
Hierarchy that works is kept.The conditions behind each group, and every place it shows up, from categories to feeds.
Future behavior is agreed.An export is only a snapshot. Exporting the products in a dynamic group today saves today’s list and none of the automatic updates. We agree how each group should behave from now on, across collections, content and feeds.
Customer context, quantities, currencies and promotion priorities, tested against sample order totals.
The conditions that change prices, payment, delivery, eligibility or access, and what each one is meant to produce.
Triggers, conditions, actions, priorities and connected services, with event timing and permissions tested in Shopify.
What your source prices mean, net or gross display, currencies, rounding and the tax settings you’ve approved.
| Shopware behavior | Shopify approach | Status |
|---|---|---|
| Trade group: net prices from 10 units | B2B catalog or app, by plan | Review |
| Promotion: 10% over €100, priority 2 | Shopify discount, combinations tested | Test |
| Rule: invoice payment for approved buyers only | Payment customization, app or development | Review |
| Flow: order paid → tag & ERP export | Shopify Flow or the integration | Test |
| Historical orders re-running flows | Prevented in the import | Not allowed |
Old orders and records are imported as history and aren’t treated as live activity. We plan and test the import so it can’t create shipments, send customer notifications, take charges or grant new entitlements by accident.
Tax behavior follows what you’ve confirmed. We set up and test the agreed price display and tax settings for each market and customer group, working from your requirements and your advisor’s input. A migration isn’t legal or tax advice, and we don’t promise compliance.
How your trade customers place orders
Driven by the behavior you need
Each one gets an agreed path, whether that’s native functionality, an app, development, a system you keep or retirement.
Listed before building starts.Which system owns products, stock, prices and orders, with identifiers, updates and reconciliation all tested.
Tested from start to finish.Customer access, consent, open orders, refunds, credits, recurring billing and digital entitlements.
Someone owns each item.Analytics, consent tools, product feeds and advertising destinations get reconnected and checked.
Rechecked after launch.Importing records doesn’t move payment tokens or recurring payment permissions. Subscriptions, saved payment methods and balances need a review with your specific provider, and we hold on to the source records and access you need until open obligations are settled.
Branded layouts, product templates, navigation and editable sections to stand in for your Shopping Worlds or Shopping Experiences.
Explore theme & design →Custom connections and functions for the rule or workflow that no existing app covers.
Explore app development →The agreed migration checks for channel URLs, languages and metadata. Ongoing optimization is a separate service.
Explore Shopify SEO →Google Ads, Meta Ads, email and other channels that fit, to help you grow after launch.
Explore ecommerce marketing →The migration is priced by itself. Redesign, extra development and ongoing marketing come in only if you ask for them, each with its own scope and price.
These connections don’t travel with the catalog. After launch we check the agreed feeds, tracking and consent settings.
Shopify has its own URL structure and redirect limits, so we test sample URLs and any special cases. Old URLs with no relevant match don’t get dumped on the homepage, and we can’t promise identical paths or unchanged rankings.
These are sample paths. We work from your real channels, domains, languages and redirects.
Connecting a domain to Shopify and transferring its registration are two separate things. A domain you own can usually connect without a change of registrar. We review DNS for every channel domain first.
Shopify doesn’t host email inboxes. Your DNS changes have to preserve the records that your mailboxes and sending services rely on, so we plan them before anything is touched.
Self-hosted or on a Shopware cloud plan, we keep the agreed backups and access in place until the dependencies are sorted. You then choose when to close it.
We always arrange access to your Shopware admin, server or database securely, and never through the public enquiry form.
Migration tools can move common Shopware records, and some providers also offer assisted or managed services with human support. Where a tool suits your data, we can use it as part of the project. We take responsibility for the agreed project around it, covering source review, mapping, storefront, rules, integrations, testing and launch.
| Your question | Self-service migration tool | Migration managed by WEP |
|---|---|---|
| Who looks at the source? | You pick from the records the tool supports. | We work out your version, deployment, channels, extensions and custom fields, and write down what moves. |
| How are variants and properties handled? | Supported fields move the way they’re stored. | We work through inheritance and overrides and keep filters apart from options customers buy. |
| And the rules and flows? | Stored values may come across, but working behavior usually doesn’t. | We write down the intended outcome, then rebuild and test the agreed rules and automations. |
| Who builds the new storefront? | Usually a separate job for you or someone else. | Theme setup or customization, planned alongside the data and content. |
| Who handles launch day? | Your team organizes the cut-off, domains, redirects and checks. | We run the cut-off, domains, redirects and late-order checks, then give you 60 days of free support. |
The online store migration was seamless without having 0 downtime. The staff is properly trained, well communicated and proactive Highly recommended
Web commerce pros created a really lovely design for our website. They also changed the layout for our images and updated/resized images so that the site is overall much more attractive. We have been receiving a lot of positive feedback from customers on the ease of use and the overall look of our site. In addition, we are very grateful to Roy for coming up with a creative solution for allowing customers to easily create their own quotes, which has been very helpful to both our operations and our customers.
Arfat and team were proficient with BigCommerce Page Builder and Shogun to create and modify pages. We successfully completed the migration with their assistance and were happy with their work. We would hire again soon for our next project.
We pin down your version, deployment, channels, data access, content, rules and connected systems, then agree where each one ends up.
We build the Shopify store on its own, test sample records and buying journeys, and ask for your approval against the acceptance checks we agreed.
We keep catalog edits under control, confirm which system owns stock and set the cut-off for the changing records that get one last update.
We handle domains, integrations and redirect checks, reconcile late orders and deliver the agreed training and support.
This shows the kind of checks we agree with you. It isn’t a completed client case study.
That way the switch is planned in advance.
The migration runs around a defined cut-off, and there’s no ongoing two-way synchronization between Shopware and Shopify. We work to keep risk low, but we can’t promise zero downtime or uninterrupted trading.
Yes, we can plan a move from either one. Migration tools list support for both, and we confirm your exact version and extensions in the free store review.
Shopware 5 has reached end of life, so both routes mean a rebuild. Shopware 6 keeps you in the same ecosystem, and Shopify shifts hosting and updates to the provider. We go over what to weigh in the free store review, and we don’t claim one choice suits everyone.
That depends on catalog size, customisations, and how many sales channels and languages you run. After the free store review we give you a timeline, since a fixed promise wouldn’t mean much.
Our team does the data transfer, theme build, app setup, redirects and testing. From you we need access, content decisions and final sign-off.
Shopware 6 has an Import/Export module that works with CSV profiles for products, variants, categories and customers, and orders can be exported too. Some data, such as reviews, coupons and CMS pages, may need API access or a migration tool. We check what applies to you during the review.
Manufacturers, Rule Builder pricing, layouts built in the Shopping Experiences editor and some tax or invoice handling all work differently in Shopify. We rebuild them with tags, metafields, apps or theme sections, and we list the gaps for your store.
Usually they map to Shopify options and variants, with metafields for extra attributes. Shopify caps options and variants per product, so large variant sets may need restructuring. We test this against your catalog.
Generally yes, though migrated orders show up as imported records and get new IDs. The exact detail depends on the tool, so we confirm it in the review.
Shopify documents that passwords can’t be carried over through CSV import. With newer Shopify customer accounts, customers sign in by email with a one-time code, while legacy accounts need an invite to set a new password. We plan the customer message with you.
Shopware customer groups and B2B rules don’t map one to one. Depending on your Shopify plan and needs, we use tags, catalogs, company profiles or apps, and we confirm the right fit in the review.
Customer records and addresses can normally be imported, and we tie migrated orders to customers by email where we can. Customer IDs are new in Shopify. The matching approach gets confirmed in the free store review.
Many URLs will change, since Shopify uses fixed paths such as /products/ and /collections/. We set up 301 redirects and carry over titles and descriptions, but we can’t promise rankings will hold steady. Some temporary movement can happen.
Your Shopware store keeps selling while we build the new one. We schedule the switch for a quiet time and aim to keep any gap short, but we don’t promise zero downtime.
No. Shopware themes and layouts can’t be installed on Shopify. We rebuild or adapt the design in a Shopify theme and go through it with you before launch.
Yes, the domain can point to Shopify at launch. Email normally carries on as it is, and we check DNS records so nothing gets disrupted.
That depends on catalog size, customisations, languages and design work. We quote after the free store review so the price fits your store.
Often a few, because not every plugin has an exact match. Many apps charge monthly fees, so the review lists the apps we recommend and how each is priced.
We quote after reviewing your channels, data, content, rules and integrations. The proposal lists outside running costs, the schedule and the agreed support terms, and there’s no universal fixed price or timeframe. Every migration includes 60 days of free post-launch migration support within the agreed scope.
Tell us what you run now and what you’d like to be better. We’ll go through your channels, catalog and business rules before we propose the move, the scope and a quote.
Or call 888-711-2347
60 days of free migration support after launch, within the agreed scope.
