Skip to main content
Store takeover

Taking over an existing Magento 2 store: what should be checked before estimating the work?

Your Magento store works, but fixes are piling up, an improvement is blocked or the team that built it is no longer available. Before asking for a price to take everything over, you need to understand what exists, what is wrong and what must keep working. Here is the information I would look to gather before a first intervention.

MagentoBy Julien BaillyText updated on 4 min estimated read

Illustration of a modular store with one element lifted to examine dependencies before an intervention

Key takeaway

Start with a concrete objective, an access inventory and a map of functions and integrations. A clearly scoped diagnosis separates identifiable fixes, areas needing analysis and risks that still prevent a reliable estimate.

Describe an observable problem rather than an entire redesign

“The website is slow” and “everything needs rebuilding” do not offer the same starting point. Choose a few specific situations: an import that stalls, an incorrectly calculated discount or an order that never reaches the ERP. Record the steps, expected result and actual behaviour. A reproducible example helps separate a local defect from a wider issue.

Add the business constraints: peak trading periods, the team available for testing and changes already underway. I prefer to start with a priority need and check its dependencies before proposing a wider project. The first deliverable may be a documented assessment and action plan rather than an immediate change to the store.

Locate access, code and a test environment

The Magento admin panel is not enough to understand an entire platform. You need to identify where the code, media, database, backups and deployment procedure are held. Who can grant access, restore a copy or work on the hosting? This list helps identify dependencies on an agency, provider or external service.

Permissions are granted according to the actions required. For an integration, Magento lets you choose authorised API resources; this choice should be checked during a takeover. Credentials should not be collected in a commercial brief: we agree on an appropriate way to transfer them after scoping the work.

  • The code repository and the version currently deployed
  • A test environment and its known differences from production
  • The people responsible for access, backups and external services

Map the functions and integrations that keep the store running

A store may be connected to an ERP, a PIM, a logistics tool or a marketplace. For each exchange, you need to know what comes in, what goes out, when it happens and who handles failures. A correct catalogue in the admin panel can conceal an incomplete import, a specific rule or data later changed by another tool.

I recommend a simple map: source system, data involved, processing, destination and owner. Connect it to real uses: displaying a price, accepting an order, reserving stock, dispatching goods. It helps anticipate the effects of a fix and organise checks with the right people.

Inventory versions, modules and custom developments

The Magento edition, hosting components, theme and extensions form a whole. An installed module is not necessarily still in use; an essential behaviour may also depend on project-specific development. The inventory should connect these components to their functions and upgrade options.

If an upgrade is planned, compatibility must be assessed against the target version. Adobe recommends examining backward-incompatible changes and custom modules in particular. This may reveal adaptations absent from the initial request. An analysis tool provides clues but does not replace checking functions and user journeys.

Plan how to test, deploy and roll back

Before touching the website, ask how a test copy can be prepared and which data must be protected. Backup, restoration and deployment are three distinct topics. An old or incomplete copy may allow code inspection without being sufficient to reproduce a production issue.

Acceptance testing should match the change: basket, checkout, pricing rules, test payments, imports or transmission to another system. Adobe provides for validation before launch and monitoring after deployment. The intervention window and rollback conditions are agreed with the people operating the store.

Separate what can already be estimated from what needs further examination

A well-defined, reproducible request can sometimes be estimated quickly. A takeover without available code, history or with several failing integrations contains more unknowns. The quote should make these differences visible: established facts, assumptions, included items and conditions that would require reassessment.

An initial analysis can be scoped as an intervention in its own right, with questions to resolve and a report. Its terms are agreed before starting. Its purpose is to prepare a decision: fix a specific issue, plan several work packages or consider a broader change to the platform.

Prepare a short brief to start the discussion

You do not need to reconstruct the project's entire technical history. A useful brief describes the main problem, the people involved and the information already available. Unknowns can be identified as such: they are part of the work to organise.

Here is a structure to adapt to your store. It helps prepare an initial discussion without promising a budget or date based on an incomplete understanding of the existing setup.

  • Objective: what needs to work or become possible
  • Example: steps, expected result and observed problem
  • Existing setup: edition, hosting provider, agency or team, connected tools
  • Access: what is available and who can provide it
  • Constraints: deadline, availability for testing and operations to preserve

Sources and references

Documentation consulted when writing this guide. Advice and procedures should be adapted to your own context.

Related projects