To the home page
Contact

Services / Shopware update

Onto the current Shopware version, without standing still

A major update rarely concerns Shopware alone. It concerns every plugin, every adaptation and the theme. We take stock, plan the order of work and carry the update out - with a test run before the go-live.

Request an update check View references

At a glance

Target version
Shopware 6.7
Checked
plugins, theme, adaptations
Run
on a copy first, then live
Way back
planned, not improvised

When an update is due

Four situations we meet regularly

  • The version is running out of support

    Security fixes stop reaching old releases at some point.

  • Extensions need a newer base

    New plugin versions require the current Shopware version.

  • An attempt has already failed

    An update that was broken off leaves a shop nobody wants to touch.

  • Nobody knows what is in there

    Shops that grew over years contain changes nobody can explain any more.

What we do

Five steps to the new version

  1. 01

    Taking stock

    Every plugin, every theme adaptation and every custom development is recorded and assessed.

  2. 02

    Settle compatibility

    For each extension it is then clear: a current version exists, work is needed, or a replacement has to be found.

  3. 03

    A test run on a copy

    The update runs on a copy of the shop first, including data and interfaces.

  4. 04

    Catch up the adaptations

    Lifting your own extensions and theme changes onto the new version.

  5. 05

    Go live with a way back

    A fixed date, a short maintenance window, a tested route back.

Where we stand

The risk of an update rarely sits in Shopware. It sits in what grew up beside it over the years.

The core can be updated. It gets difficult with changes built around the core, with plugins that have no successor, and with themes whose origin nobody remembers. That is why we start with taking stock and not with a date.

How it runs

From the findings to the go-live

  1. 01

    Update check

    Taking stock, with findings per extension and an estimate of the effort.

  2. 02

    Plan

    Order of work, date, maintenance window and responsibilities in writing.

  3. 03

    Test run

    The update on the copy, with a functional test of the whole purchase path.

  4. 04

    Go-live

    The switch inside the agreed window, with a tested route back.

  5. 05

    Follow-up

    Watching the first days, correcting and handing over.

FAQ

Frequent questions

What an update costs is decided by what is installed. The check answers that before you commission anything.

How long is the shop offline?
The maintenance window is usually one to two hours and is placed in a quiet period. The actual work happens beforehand on a copy. If something is wrong at the go-live, we take the prepared route back instead of repairing under pressure.
What happens to plugins that no longer exist?
For every extension without a current version there are three routes: an equivalent plugin from the Store, a development of our own, or dropping it if nobody uses the function any more. The update check names the proposal and the effort for each affected extension.
Can we keep working during the update?
Yes. Orders, editing and support carry on while the update is being tested on the copy. Things are frozen only shortly before the go-live, so that no change is lost between the copy and the original. We agree that point together.
What does an update cost?
The price depends almost entirely on what is installed, not on Shopware. A shop with a standard theme and a few Store plugins is up to date within days. A shop that grew over years, with its own extensions and interfaces, needs more. The update check gives you the number before you commit.

Which version is your shop running?

The update check names the state, the effort and the order of work for every extension - before you commit to a date.

Request an update check View references

or straight to us: info@premsoft.de