How do you switch Magento agencies?

Clarify what needs to change in the working relationship

Start with observable difficulties: requests without follow-up, recurring incidents, unpredictable deployments or a lack of visibility over work. Gather examples, their impact and your teams' expectations. This helps define the criteria for the future working relationship.

Distinguish the quality of follow-up from the store's technical condition. A new agency does not make an incompatible module or an unreliable ERP connection disappear. The handover must identify these issues to avoid promising immediate improvement without a diagnosis.

Prepare an inventory of access rights and assets

Check which accounts belong to your company and who can authorise their transfer or sharing. Information must be transferred through appropriate channels, with permissions limited to what is needed. Once the handover is complete, old access rights are reviewed with the people responsible.

The code repository alone is not always enough to rebuild an environment. The required settings, dependencies and deployment procedures must also be known. Third-party licences and services require a review of their transfer conditions.

• Code repository, branches in use and production version.
• Hosting, domain, DNS and test environments.
• Modules, licences, payment and shipping services.
• ERP, CRM or PIM connections and associated technical accounts.
• Backups, logs, documentation and open tickets.

Plan a handover with the current providers

The handover must cover completed work, work still in progress and known defects. Ask for a description of the latest deployment, routine operations and sensitive areas. The obligations and deadlines in your current contract must be considered when organising the transfer.

During an overlap period, clarify who is authorised to modify production and how interventions are announced. Two teams must not independently deploy incompatible changes. A shared schedule and a designated lead reduce this risk.

Validate the store before resuming development

The new team must be able to understand the installation and, within the agreed scope, reproduce its operation in a test environment. The review covers versions, extensions, customisations and essential business workflows.

A single test order is not enough if your business uses several payment methods, customer-specific prices or special shipping rules. Select representative scenarios with your sales and operations teams. Any discrepancies become a list of work to prioritise.

Separate stabilisation from new development

Start by making interventions manageable: reliable access, an understood deployment procedure, identified backups and a review of priority incidents. New features can then be planned on this basis.

The maintenance arrangement specifies contacts, request qualification, agreed support hours and acceptance conditions. Commitments are defined according to your business. A potential redesign is decided after analysis; switching agencies does not automatically require one.

Prepare the handover with AXELITES

Tell us about your store, the reasons for the change and important deadlines. We can start by reviewing the available information, then define the prerequisites, handover scope and necessary discussions with your providers.

AXELITES offers competitive prices for Magento handover and maintenance. Contact us for more details and a proposal tailored to your situation.