How do I find Shopware 6 replacements for my Shopware 5 plugins?
Finding Shopware 6 plugin replacements means working through your Shopware 5 plugin list line by line and deciding what each plugin becomes. Shopware 5 plugins are not compatible with Shopware 6, and there is no automatic conversion. Shopware rebuilt the platform from the ground up, so each plugin needs a new home before you go live. Most of the list resolves quickly. A few custom or niche plugins usually take the real effort.
Quick Answer
Every Shopware 5 plugin needs a Shopware 6 replacement, because the old plugin code does not carry over. Export your installed plugin list, drop what you no longer use, and test whether Shopware 6 covers the rest in core. Then ask each vendor about a Shopware 6 version and search the Shopware Store with the Shopware 6 toggle on. Scope a custom build for anything with no match.
Which parts of a Shopware 5 shop need replacing
Shopware 5 lost official support at the end of July 2024, according to Shopware’s end-of-life notice. Some of your shop moves across with official tooling. Other parts need a rebuild. For the full data breakdown, see what the Shopware Migration Assistant carries over.
| Item | Carries over? | Source |
|---|---|---|
| Plugin code | No. Each plugin needs a Shopware 6 equivalent. | Follows from the platform redesign in Shopware’s upgrade guide |
| Themes and templates | No. You rebuild on the Shopware 6 default theme. | Shopware upgrade guide |
| Shopping Worlds | No. You recreate them in Shopping Experiences. | Shopware upgrade guide |
| Products, manufacturers, customers | Yes, through the Migration Assistant. | Migration Assistant listing |
| Free text fields | Yes, as custom fields. | Shopware migration process docs |
| Third-party plugin data | Sometimes. It depends on the plugin and vendor. | Shopware migration tutorial |
Steps to find Shopware 6 plugin replacements
Step 1: Export a complete plugin inventory
Run this command on the Shopware 5 server to list every installed plugin:
bin/console sw:plugin:listThe Shopware 5 CLI documentation covers this command. Add columns for vendor, version, active status, and what the plugin actually does. Names can mislead. A plugin called “Custom” might only adjust invoice PDFs.
Step 2: Cut what you no longer need
Inactive plugins and features nobody uses can go now. Each deletion saves you a round of sourcing, testing, and licensing later.
Step 3: Test Shopware 6 core first
Shopware 6 ships features that used to need extensions. One example is the Rule Builder, which you find under Settings > Automation > Rule Builder. Before buying anything, try the core feature on a staging install with your real use case.
Step 4: Ask the original vendor
Many vendors built a Shopware 6 version of their Shopware 5 plugin. Some shipped it under a new name. Put three questions to each vendor:
- Does a Shopware 6 version exist, and what is it called?
- Do they provide a migration profile for the plugin’s stored data?
- Does your current licence transfer, or do you buy again?
Step 5: Search the Shopware Store by function
The store has a switch for Shopware 6 and Shopware 5 results, which the Shopware Store FAQ describes. Set it to Shopware 6. Search for the job the plugin does rather than its old name. On each candidate’s page, check the compatible version range against your target Shopware 6 version.
Step 6: Scope custom builds for the gaps
Heavily customised in-house plugins rarely have a store equivalent. Shopware 6 offers two extension types, plugins and apps. Shopware’s developer documentation states that plugins cannot run in Cloud shops. A cloud-hosted store therefore needs an app. Scope these builds early, since they usually set the migration timeline. Stagebit’s Shopware development team builds these extensions.
Check before you switch
Installing a replacement plugin does nothing for the data your old plugin stored. Plugin-specific records, such as custom order attributes or saved configuration, need their own migration path. That path exists only if the Migration Assistant lists them as “Plugin data” or the vendor supplies its own migration profile. Confirm it for every plugin that holds data. Then run a full test migration on staging before you commit to the replacement.
What to do next
Your inventory becomes the migration plan. Once every row has a destination, you can price the project and set a realistic timeline. Resolve checkout, payment, and ERP sync plugins first, because a gap there blocks launch. For the wider process, see how to migrate from Shopware 5 to Shopware 6.
Related Answers
Was this answer helpful?
Your feedback helps us improve our answers.
Still need help?
Stuck on a Shopware 5 plugin with no match?
Send us your plugin list, and our Shopware engineers will flag which ones need a custom build.