Ecom house logo

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.

Magento 2 update and store takeover - copy, tests, switchover with rollback

Every postponed Magento update costs more

Checking the state of a Magento store before an update
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.

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

Removing unnecessary Magento modules during an update

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:
  • 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.
In one pre-update audit, about 18 of 88 modules were actually needed (see the audit case).

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

Update plan for a large Magento store from 2.4.3 to 2.4.8

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.
The whole project took about 3 months. In the same store, we patched an actively exploited remote code execution (RCE) vulnerability within a week.

Magento store takeover from another vendor

Magento store takeover from the previous 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.
Sometimes it turns out that bringing the old store into shape would cost more than rebuilding it. Then we say so plainly and show you both options. We've been working with some clients for more than 5 years.

See the results

Explore selected projects and read case studies in a concise format.

Case study JKB/FairyTrees - Magento 2 ecommerce store with ERP integration, UX/UI design, multistore solution with custom functionalities

JKB / FairyTrees

Magento 2ERP IntegrationUX/UI designMultistoreCustom Functionalities
Read more
Case study Bielenda/MiyaCosmetics - PWA store with Magento 2, headless architecture with microservices, ecommerce migration

Bielenda / MiyaCosmetics

PWAMagento 2MicroservicesHeadless architectureecommerce Migration
Read more
Case study Bioderma/Esthederm - interactive PWA product catalog for POS, omnichannel solution with product quiz

Bioderma / Esthederm

PWAPOSOmnichannelProduct CatalogProduct Quiz
Read more
Case study LaMania - PWA ecommerce platform with Magento 2, microservices architecture, DevOps/SLA, pre-implementation analysis

LaMania

PWAMagento 2MicroservicesDevOps / SLAPre-implementation Analysis
Read more

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.

The e-com.house Team helped us with a comprehensive implementation of the ecommerce business model. Despite the difficult conditions related to the coronavirus pandemic, as well as the number of parties involved and the complexity of the project, within a few months we managed to add a strong online presence to our current business. E-com.house was a real support for us in the entire process and in various areas – from technology, through UX, to growth marketing.

Daniel Biegaj

Ecommerce & Marketing Director w Benefit Systems

sklep.yes2move.com

We've been working with e-com.house on all things ecommerce since may 2018. Apart from being 100 percent professional and reliable, they are also really nice people 🙂 Their expertise allows us to make decisions quicker while helping us to avoid mistakes that are easy to make when you're getting started with your own ecommerce business. e-com.house also acts as our technological partner as their team supports and adjusts our entire IT infrastructure to the demands of our quickly developing online store.

Alina Sztoch

Co-founder Kubota Store

KubotaStore.pl

What sets the e-com.house team apart from the competition is their focus on the client and their ability to see a bigger picture when analyzing client's needs. At the same time they pay great attention to detail. Thanks to their comprehensive knowledge, the team can not only help you in creating your digital strategy, but also make it easy for you to implement and execute it. They have a holistic approach to the digital brand building process - they appreciate both the importance of content and the need to monetize it. Working with them has been a great pleasure.

Hanna Rydlewska

Digital Director 'Vogue Polska'

Vogue.pl

E-com.house took over the maintenance and development of our online bookstore Literia.pl in November 2018. During that time their team has proven to be very competent in using Magento - the engine that our store has been built on. Moreover, our cooperation runs in a relaxed atmosphere – the e-com.house team members I've met are simply very nice and helpful people.

Piotr Kubiszewski

Product Owner Literia.pl, Grupa Onet-RASP

Literia.pl

We've been working with e-com.house for over 2 years. During that time we've successfully migrated 6 of our online stores from Magento 1 to Magento 2, while refreshing their UX/UI with the mobile device users in mind. This has improved the overall efficiency and security of our online stores. Merging 6 separate platforms into 1 multistore has also lowered our costs. Overall, our conversion rate has increasd by 47%!

Izabela Pańkowska

UK Market Manager

LiveOutside.co.uk

E-com.house supported us during the entire process of developing and implementing our new online store. Their continuous support, regular status updates and consultations allowed us to efficiently solve current issues and ensure that the platform is compliant with the rest of our IT ecosystem. In practice, we have become one team that works together to achieve the set goal.

Daria Leśniewska

Sales & Communications Director

RISKmadeinWarsaw.com

Having cooperated with a number of companies, we were looking for a business partner and not an inflexible contractor. E-com.house has proved to be such a partner. They helped us create an online store that meets all our requirements. Their enormous knowledge, professionalism and a very high level of culture made our cooperation a very interesting experience. The product they delivered has been equipped with many features that exceed our expectations.

Piotr Jóźwik

Kierownik działu ecommerce w PCE

PartnerElectronic.eu

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.

Contact us

We could write at length about how we work day to day. The simplest way, though, is to talk and swap questions and expectations - both ways. Drop us a message through the form or book a meeting in the calendar right away.

+48

We reply within 24 hours on business days.

We'll use the data from this form to reply to your message. The data controller is Ecomhouse sp. z o.o. Details and your rights: Privacy and cookie policy