Migration and Takeover of Existing Projects
Taking over existing shops and websites from another provider or from internal management is one of our most common entry points. The following questions address the handover process and common concerns.
In short and in plain language
On this page you will find questions and answers on the topic “Migration and Takeover of Existing Projects”.
Each question has its own page with the answer. Below the question you see the start of the answer. Click on a question. Then you can read the whole answer.
At the bottom, a link takes you back to all questions.
- Can you take over a shop built by another agency? Yes, taking over existing projects is one of our most common entry points. You need neither rebuild the shop nor switch to us as your developer to get professional maintenance. We…
- What happens during onboarding of an existing project? Onboarding follows a fixed sequence: a technical audit for the inventory, cleanup of critical issues, setup of staging environment and monitoring, creation of system documentation…
- Do I need the source code or access from my previous agency? Ideally yes. For a clean takeover, we need access to the server (SSH), the database, the hosting panel and the CMS backend. If your previous agency developed custom plugins or…
- What happens if my shop already has security issues? Then cleanup takes priority. In this case, onboarding begins with prioritized resolution of the acute security issues via our emergency support before we think about regular…
- Can I keep my hosting provider? In most cases yes. We work with common hosting providers and adapt our maintenance processes to the respective server environment instead of making a migration a condition. For…
- How long does taking over an existing project take? Complete onboarding typically takes two to four weeks. During this time we run the audit, clean up critical points, set up staging and monitoring and create the system…