Short answer: taking over a Magento webshop from another agency is done in five steps. First, arrange all access and the ownership of code and data. Then, have the webshop technically audited. Next, set up your own test and deployment environment, transfer management in phases, and agree in advance on when the handover is complete. Your webshop remains online the entire time.
Switching usually happens for the same reasons: updates fall behind, the shop becomes slower, communication is difficult, or the agency stops with Magento. We regularly take over Magento webshops, so we are not neutral. This step-by-step plan also works if you continue with another agency.
Updated on November 4, 2026. Sources are listed at the bottom.
Step 1: arrange access and ownership
Start here, before terminating the collaboration with the old agency. Without full access, a new agency cannot assess anything and you run the risk of remaining dependent. Magento Open Source falls under the Open Software License 3.0. Custom code written for you generally belongs to your webshop, but check what your contract says about this.
What | Why you need it |
|---|---|
Git repository with full history | Without history, you cannot see who changed what and why. A zip file of the code is not enough. |
Server and SSH access or the hosting account | Needed to evaluate server setup, backups, and cron jobs, and to migrate them later. |
Magento admin with administrator privileges | For configuration, extensions, users, and payment methods. |
Composer keys and licenses for paid extensions | Without valid keys, you cannot update or reinstall extensions. |
Domain, DNS, and SSL | Ensure the domain is registered in the name of your own organization, not the agency's. |
API keys and documentation for integrations | ERP, PIM, payment provider, shipping, and marketing tools. Also ask who manages the integrations. |
Step 2: map out the technical baseline
With access, you can document what is actually running. This data determines how much work the takeover will be.
Magento version and patch level: are you running a version that still receives security updates?
Theme: Luma, Hyvä, or a custom frontend.
Extensions: which ones are present, who is the vendor, and are they still maintained?
Custom modules and core modifications: the more there are, the greater the risk during updates.
Deployment: is there a CI/CD pipeline, or is work done manually on the server?
Cron jobs, queues, and integrations: what is running in the background and what happens if it stops?
Step 3: have a technical audit performed
An audit translates that inventory into risks and priorities. A good audit looks beyond just the code.
Component | What we check |
|---|---|
Code | Quality of custom code, core modifications, outdated or duplicate extensions. |
Security | Pending security patches, admin security, user permissions, and two-factor authentication. |
Performance | Loading times, caching (Varnish, Redis), indexing, and Core Web Vitals. |
SEO | Redirects, canonicals, sitemap, and indexing, so you don't lose rankings during the transition. |
Integrations | Stability of ERP, PIM, and payment integrations, error handling, and logging. |
Data | Product data, customer data, and order history: quality and who has access. |
Hosting | Server configuration, backups, monitoring, and whether the environment fits your traffic. |
Are you running Adobe Commerce? Then Adobe's Upgrade Compatibility Tool helps identify which custom code causes issues during an upgrade. For Magento Open Source, we perform this analysis manually and using static code analysis.
Step 4: hand over via a staging environment
The live webshop remains running while the new agency takes over. This prevents customers from noticing anything.
Set up a copy of the webshop on your own staging environment, with anonymized customer data.
Configure deployment so that every change is tested first and then deployed live in a controlled manner.
Resolve the most urgent issues from the audit first, usually security vulnerabilities and broken integrations.
If necessary, migrate the hosting and test the new environment under realistic load.
Take over daily management: monitoring, backups, updates, and support.
Agree in advance on when the handover is complete. For example: all access is in the name of your own organization, the new deployment pipeline works, backups and monitoring are running, and the first updates have gone live without issues.
What do you deliver after the takeover?
An audit report with findings per component.
A prioritized action plan: what needs immediate attention, what can wait.
A working staging and deployment environment, with monitoring and backups.
A first sprint covering the most important improvements.
Common mistakes during a switch
Terminating the contract with the old agency before obtaining all access and documentation.
Only having the code transferred while forgetting the server setup, cron jobs, and integrations.
Making live changes directly without a staging environment.
Starting a major rebuild project before it is clear what is technically wrong.
Forgetting redirects and SEO settings during a hosting migration.
Frequently Asked Questions
How long does it take to take over a Magento webshop?
For a smaller webshop, the audit and handover are usually completed within a few weeks. For a large B2B webshop with ERP and PIM integrations, it often takes a few months, because each integration must be tested.
Will my webshop go offline during the takeover?
No. The work is done in a staging environment. Only during a hosting migration is there a brief, pre-planned window when traffic is switched to the new server.
Do I also need to switch hosting?
Not necessarily. We first assess whether the current hosting is properly configured and fits your traffic. Only if that is not the case will we recommend a migration.
What if the old agency refuses to cooperate?
First, check your contract to see what agreements exist regarding ownership and handover. Often, the admin, hosting account, and domain are already registered in your name, allowing you to proceed that way. If you are unsure about your rights, seek legal advice before ending the collaboration.
Do I have to switch to Hyvä if I change agencies?
No. A switch to Hyvä can be a logical next step if your frontend is slow or outdated. That will become clear from the audit.
Want to know the current status of your webshop? Request a free Magento health check. We evaluate the code, security, and hosting, and provide an honest assessment of what is needed.
