Magento 2 update and store takeover
We update Magento 2 stores and take them over from other vendors. We start with an audit, work on a separate copy and switch production over with a ready procedure to roll back to the previous version. Along the way, we remove the modules the new Magento no longer needs.
Every postponed Magento update costs more
Magento and PHP have a defined support period. When it ends, the store stops receiving security patches, while vulnerabilities in old versions are publicly documented.
The longer a store waits, the bigger the version jump and the more modules have to be adapted or replaced. Every module vendor has its own schedule, and the previous vendor's code often has no documentation. That's why we start every update by checking what the store actually uses.
The longer a store waits, the bigger the version jump and the more modules have to be adapted or replaced. Every module vendor has its own schedule, and the previous vendor's code often has no documentation. That's why we start every update by checking what the store actually uses.
How a Magento store update works
Six steps. A simple store takes 1-2 months, a large one up to 3 months. We work on a separate copy the whole time.
1. Audit
We check versions, modules, integrations and what the store actually uses. Without that, you don't know what to update in the first place.2. Update plan
We set the target Magento and PHP versions. Every module gets a decision: update it, replace it with a native feature or remove it.3. Update on a copy
We upgrade the core, modules and integrations with ERP or PIM, and install security patches. All on a separate copy of the store, while production runs as usual.4. Testing
We test the purchase path from product page to payment and the data exchange with external systems before anything reaches production.5. Production switchover
We agree the date with you. The switchover comes with a ready procedure to roll back to the previous version if something goes wrong.6. Care after the update
We fine-tune performance and fix whatever comes up after launch. With our maintenance service, ongoing monitoring is included.A Magento 2 update is a good moment to clean up
The cheapest module to update is the one that's gone
Every module has to be checked, adapted to the new version and tested during an update. So before we raise the version, we check what can be removed:
During the update, we can also replace an old theme with Breeze. Breeze stays on Luma and its modules, so the front end doesn't have to be rewritten for every module. We've implemented it in two Magento stores.
- modules that patched bugs already fixed in newer Magento,
- paid packages the store uses one feature of, which a native option can replace,
- modules with no data in the database and no configuration.
During the update, we can also replace an old theme with Breeze. Breeze stays on Luma and its modules, so the front end doesn't have to be rewritten for every module. We've implemented it in two Magento stores.
Case: updating a large Magento store
From 2.4.3 to 2.4.8, with less code along the way
A large store developed over many years: Magento 2.4.3 and PHP 7.4 without security support, a Luma-based theme, a dozen or so unused modules and an extra login system (SSO) that was no longer needed after years of changes. The documentation no longer matched the store.
- We split the work into 8 stages, each with a clear definition of done.
- Before removing a module, we checked its data in the database, and after each stage we ran a test purchase.
- We removed dead modules and the unnecessary login system, and moved custom modules to PHP 8.4.
- We prepared and tested the store on Magento 2.4.8 on a separate copy.
- The new Breeze theme, with the UX kept intact, is already in production.
Magento store takeover from another vendor
Access and knowledge first, development second
We've taken over more than ten projects built by other teams. Getting into someone else's code, up to normal development, takes us 1-2 months. Along the way we:
- take over access: repository, server, admin panel, integrations and license keys,
- run an audit and write down what actually works and what it's for,
- check integrations with ERP, payments and carriers,
- agree a plan with you: what to fix right away and what can wait.
See the results
Explore selected projects and read case studies in a concise format.
References that speak for themselves
Dynamics, changing circumstances, and our approach to work - our clients will tell you themselves. See what it's like to work with us.
Magento update and takeover FAQ
How long does a Magento update take?
We update a simple store in 1-2 months and a large store in up to 3 months. The time depends mainly on the number of modules and integrations and on how big the version jump is.
Does a Magento update require taking the store offline?
All the work happens on a separate copy, so the store runs as usual. We plan the production switchover with you, at the time least disruptive to sales, and we have a ready procedure to roll back to the previous version.
What happens to modules during a Magento 2 update?
We check every module before the update. We update the ones the store uses, replace those duplicated by the new Magento with native options, and remove dead ones. Every removed module is one thing less to handle in future updates.
How does a Magento store takeover work?
We start by taking over access (repository, server, admin panel, integrations, licenses) and running an audit. Then we check the integrations and agree a plan: what to fix right away and what later. Normal development starts after 1-2 months.
When does a store takeover not make sense?
When bringing the old store into shape would cost more than rebuilding it. That was the case with an electronics store where about 18 of 88 modules were needed (Magento audit case). Then we show both options with a maintenance comparison.
How much does a Magento update cost?
We set the price after we analyze the scope together. The cost depends on the version jump, the number of modules and integrations, the quality of the existing code and whether we replace the theme along the way.
Which companies do Magento updates?
Magento updates are done by agencies and software houses that build and maintain stores on this platform. ecom.house has been in ecommerce for almost 10 years, builds stores on Magento Open Source and has taken over more than ten projects built by other teams. When choosing a company, ask whether they update on a separate copy and whether they have a rollback procedure.
Will you look after the store after the update?
Yes, if you want. With our maintenance service, monitoring after the update is included and we install further security patches as they come out. More: Magento 2 maintenance and hosting.

















