How to update Shopware 6 safely (staging, backups, rollback)?
Quick Answer
The safest way to update Shopware 6 is to use a staging environment, full database and file backups, and a tested rollback plan before touching production. Most failed updates happen because stores skip extension compatibility checks or update directly on live infrastructure. The process below covers how to prepare staging, test extensions, back up correctly, deploy updates safely, and roll back fast if something breaks.
Before You Start
- ✦ SSH and server access — you’ll need command-line access for Composer updates, cache handling, and rollback work.
- ✦ A proper staging environment — staging should mirror production versions, PHP settings, Redis, Elasticsearch, and plugins.
- ✦ Verified backups — a backup that cannot be restored is not a backup.
Audit extensions first
Before updating anything, check every installed extension against the target Shopware version. This is where most update failures start. One abandoned plugin can block administration access, break checkout flows, or trigger migration errors. Pay extra attention to custom plugins and older storefront overrides because these usually fail after major platform changes.
- Review plugin compatibility in the Shopware Store
- Identify plugins without recent maintenance updates
- Document custom code overrides and decorators
Clone production to staging
Your staging store should behave like production. That means matching PHP versions, database engines, Redis configuration, Elasticsearch versions, cron jobs, and CDN handling. Using a stripped-down staging setup gives false confidence because performance and indexing issues often appear only on production-like infrastructure.
- Copy the live database into staging
- Sync uploaded media and theme assets
- Disable outgoing emails and payment captures
Create verified backups
You need backups of both the database and the full Shopware file system. That includes media, custom plugins, environment files, themes, and Composer dependencies. Stores often back up only the database and then discover during rollback that plugin versions no longer match.
- Export a fresh production database dump
- Archive the complete Shopware project directory
- Test restoring the backup on a temporary environment
Run updates in staging
Apply the exact update process in staging before touching production. Watch migration output carefully because database schema failures often appear here first. After updating, clear caches, rebuild themes, reindex data, and run through critical customer journeys manually.
- Run Composer updates in staging
- Execute database migrations and plugin updates
- Test checkout, login, search, and admin workflows
composer update
php bin/console system:update:prepare
php bin/console system:update:finish
php bin/console cache:clear
php bin/console theme:compilePrepare rollback procedures
A rollback plan should exist before deployment starts. Do not improvise under pressure after checkout breaks. Your rollback process should define who restores backups, how DNS or load balancers are handled, and how long the recovery should take. Time matters because failed updates during peak traffic can become revenue incidents very quickly.
- Document rollback commands and restore paths
- Assign technical owners for deployment and rollback
- Define acceptable downtime windows before launch
Deploy during low traffic
Once staging passes, repeat the exact tested deployment process on production. Avoid changing deployment steps mid-update because panic-driven fixes usually create more damage. Put the store into maintenance mode briefly if needed, monitor logs during deployment, and keep your rollback team available until post-update validation finishes.
- Deploy during off-peak order hours
- Monitor server logs and failed jobs live
- Validate checkout and payment providers immediately
Shopware Update Checklist
0 of 8 completeMistakes Most Developers Make
! Updating directly on production
What happens: Small plugin conflicts turn into live checkout outages.
Fix: Always test the exact deployment flow in staging before production rollout.
! Skipping rollback testing
What happens: Teams lose hours during incidents trying to rebuild old releases manually.
Fix: Restore backups once before deployment so you know recovery actually works.
! Forgetting payment provider testing
What happens: Orders appear successful while payment captures silently fail.
Fix: Run real end-to-end payment tests after every Shopware core update.
Key Takeaway
The short version: safe Shopware 6 updates depend on preparation more than the update command itself. Clone production into staging, verify plugin compatibility, test backups, and validate rollback before touching the live store. Most update disasters happen because teams skip realistic staging tests or rely on unverified backups. Keep deployments predictable, repeat the exact same process from staging to production, and monitor checkout immediately after launch. Start with Step 1—that one alone handles most of it.
Related Answers
Was this answer helpful?
Your feedback helps us improve our answers.
Still need help?
Talk to our Shopware experts
We've handled GDPR/CCPA compliance for dozens of EU & US Shopware stores.