Services / Changing agency
Taking your shop over without rebuilding it
Changing your service provider is not a relaunch. We take an existing Shopware shop over while it keeps running: first understand what is there, then take responsibility for it.
At a glance
- First conversation
- free of charge
- Handover check
- one to two weeks
- Operation
- keeps running during the handover
- Support
- Best Support Rating Award 2024
Typical occasions
Four reasons customers move to us
-
Answers take too long
A bug in the checkout costs revenue every day. Waiting is the most common reason for a change.
-
The provider has shifted focus
Shopware has become a side track there, and your shop with it.
-
Nobody knows what is in the shop any more
Changes without documentation, access in the hands of individuals, no traceable state.
-
Every request ends in a quote for a relaunch
You want to develop the shop further, not replace it.
What we take on
Five fields of work
-
01
Access and responsibility
Taking over hosting, repository, Shopware account and domains in an orderly way - documented instead of in one person’s head.
-
02
Taking stock
Recording and assessing plugins, custom development, theme and interfaces.
-
03
Stabilising
Open bugs, missing updates and security gaps come first.
-
04
Running the shop
A fixed contact, agreed response times and a channel that is reachable during an incident too.
-
05
Development
After that step by step, in stages with a visible result.
Where we stand
A change of provider is no reason for a relaunch. The shop that earns money today has a claim to keep running.
A rebuild is the comfortable route for a provider: own code, own decisions, none of somebody else’s history. For you it means months without visible progress and a new risk on top. We would rather work our way into what is there and replace only what can no longer be kept.
What we need for the handover
Three things, no more
Usually all of it is there. If something is missing, we reconstruct it from the running system.
-
Access
Hosting, database, repository, Shopware account and domain management.
-
Code and history
The repository with its history, or at least the current state including custom development.
-
Knowledge
What was changed last and which points are open. A conversation is often enough for that.
How it runs
From the first conversation to running the shop
-
01
Getting to know each other
The starting point, the annoyances and the expectations - openly and without a contract.
-
02
Handover check
Technical findings with risks, immediate measures and effort.
-
03
Handover
Sorting out access, code and documentation, settling responsibility in writing.
-
04
Operation
A fixed contact, agreed response times, development you can plan with.
FAQ
Frequent questions
A change of provider raises the same questions whatever the shop looks like. Here are our answers.
Do we have to talk to our old agency for this?
Will our shop be rebuilt in the process?
How long does the handover take?
Do you take over the hosting as well?
Let us talk about your shop
The first conversation costs nothing and commits you to nothing. If a change does not make sense in your case, we say so.
Talk about a handover View references
or straight to us: info@premsoft.de