How much of my Shopware 5 theme has to be rebuilt for Shopware 6?
None of your Shopware 5 theme code carries over to Shopware 6. Every template, stylesheet and script gets rewritten, because the new version runs on a different frontend stack. The parts you keep are your brand design and your image assets.
Quick Answer
Plan to rebuild all of the theme code. Since Shopware 6.5, the Storefront runs on Twig, SCSS, Bootstrap 5 and vanilla ES6 JavaScript, so no Smarty template, LESS file or jQuery plugin ports over. Brand styling, fonts and images carry over unchanged. Most teams extend the default Shopware 6 theme, so the effort depends on how far the old design departed from it.
Why the old theme code can’t be reused
Shopware rebuilt its architecture on new technologies for version 6. The Shopware 6 upgrade guide states that, as a result, old templates can’t be reused or migrated.
The Migration Assistant handles data such as products, customers and categories. Theme files sit outside its scope entirely.
Moving a Shopware 5 theme to Shopware 6: what carries over
| Theme layer | Shopware 5 | Shopware 6 | Carries over? |
|---|---|---|---|
| Templates | Smarty (.tpl) | Twig with block inheritance | No. Every template is rewritten. |
| Styles | LESS | SCSS on Bootstrap 5 (as of 6.5) | Values only. Colors, breakpoints and spacing get copied by hand. |
| JavaScript | jQuery plugins | Vanilla ES6 Storefront plugins built with webpack | No. Behavior is rewritten. |
| Theme settings | Theme.php config fields | theme.json and Administration theme config | No. Settings are redefined. |
| Landing and content pages | Shopping Worlds | Shopping Experiences | No. Pages are recreated. |
| Brand assets | Logos, fonts, icons, product imagery | Same files | Yes |
JavaScript is often the single largest job. With the Bootstrap 5 update in Shopware 6.5, Shopware stopped shipping jQuery as a dependency. Its 6.5 upgrade notes recommend moving jQuery code to vanilla JavaScript. Old Shopware 5 scripts therefore need a rewrite before they run on the new Storefront.
How big your theme rebuild will be
Shopware 6 themes normally extend the default Storefront theme. Shopware’s theme documentation describes how a theme inherits from another and overrides only what differs. So sizing comes down to one measurement: how far your design sits from the Shopware 6 default.
| Factor | Smaller rebuild | Bigger rebuild |
|---|---|---|
| Starting point | Old theme extended Responsive with color, font and logo changes | Old theme replaced most Responsive templates |
| Page layouts | Product and category pages follow a conventional layout | Custom configurators, bundles or checkout steps built in Smarty blocks |
| JavaScript | Little custom script beyond the Responsive defaults | jQuery drives filtering, sliders or cart behavior |
| Plugins | Storefront plugins have Shopware 6 versions with their own templates | Plugins with no Shopware 6 version injected markup into the theme |
| Shops | One storefront | Several subshops running different theme variants |
If your plugins land in the right-hand column, work through finding Shopware 6 replacements for Shopware 5 plugins before scoping the theme. Subshops add work because the migration turns each one into its own sales channel, and each sales channel needs a theme assigned.
For budgeting, [INSERT: typical hours or cost range for a Shopware 6 theme rebuild, split by lightly customized versus heavily customized Shopware 5 themes, from Stagebit project data].
Plan Shopping Worlds separately
According to the Shopware 6 upgrade guide, Shopping Worlds data can’t be transferred, because Shopping Experiences use a different technical structure. Every landing page and content-heavy category has to be recreated under Content > Shopping Experiences. These pages sit outside the theme and often get missed, so list them before scoping. For the full data picture, see what the Shopware Migration Assistant carries over.
Scoping the rebuild before you start
Take screenshots of every page type your store uses: home, listing, product, cart, checkout, account and content pages. Mark each one as close to the Shopware 6 default or custom. The custom pages are where the Twig and JavaScript hours go.
Timing matters as well. Shopware’s migration documentation advises validating migrated data on a clean install before configuring the shop’s look. Theme work therefore usually follows the first data migration. Our walkthrough on how to migrate from Shopware 5 to Shopware 6 shows where the theme rebuild fits in the project order.
If you’d rather hand off the audit and the Twig rebuild, that work sits within our Shopware development services.
Related Answers
Was this answer helpful?
Your feedback helps us improve our answers.
Still need help?
Talk to our Shopware experts
Send us your Shopware 5 store, and we'll map which templates need a Twig rebuild and which design work carries straight over.