Magento handover: what a clean project close contains

1. Why the Magento handover is so often neglected

At the end of a project stands the go-live, and after that time presses. The client wants to sell, the team moves on to the next job. The Magento handover often falls by the wayside even though it makes the difference later. Without it, a shop arises that only one person understands, and every later change becomes more expensive.

A clean Magento handover has two recipients. The first is the client, who must know what they received and how to operate the shop. The second is a third party who maintains the shop later: your maintenance team, another developer or a new team. Both need different information, so the handover should cover both.

The handover is especially important when parts of the project were created externally. How to steer the cooperation is described in the guide Magento project management with an external developer.

2. What belongs to a Magento handover

A complete Magento handover consists of six building blocks. The table below shows what belongs in and in which form it is sensibly handed over.

Not every project needs every block in full depth. For a small shop a document of a few pages is enough. What matters is that no row of the table remains without an answer, because every gap costs time and money later.

3. Documentation: short, current and in the repository

For the Magento handover, findability counts, not volume. A long document nobody reads helps less than one page in the repository that describes what lies there and why. Proven are an overview of the custom modules with one sentence each on purpose, a list of specialties and deviations from the standard and notes on known weaknesses.

Above all, document the unexpected. Everything a new developer cannot guess belongs in: why was a module adapted, which cron jobs run, which configuration differs between test and live. The rest is in the code or in the Magento documentation.

Write the documentation during the project, not after. Whoever has to create it retroactively at the end forgets half. A short entry per larger task, as described in the guide Magento project management with an external developer, is often enough.

A simple structure has proven itself: a start page with the purpose of the shop, Magento version and environments, a page on the custom modules, a page on deployment and operations and a list of open points. Every page has a date and an owner. With these four pages a new developer can understand within a few hours how the shop is built and does not have to search the code for days.

4. Access, rights and licenses

In the Magento handover, access is the most delicate part. At the end the client should have access to everything needed for operation: repository, server, admin, domain and license accounts. At the same time, access that applied only to the project should be blocked.

For extension licenses the client should be the owner or ownership should be clearly settled. If a module is licensed to your agency account, the client gets no updates as soon as the cooperation ends. Check this before go-live, not after.

5. Training and acceptance protocol

A Magento handover includes training of the people who use the shop daily. These are usually editors who maintain products, categories and content, and administrators who manage orders, user rights and settings. One hour in a video call with practical examples often replaces a long manual.

The acceptance protocol closes the project. It records which scope was delivered, which defects are known and by when they are fixed, and that the client accepts the shop. Acceptance usually starts the warranty period. Formulate the details with your partner so that deadlines towards the client and the partner match.

If an external partner works in the background, an intermediate step is added to the Magento handover. The partner hands over to you, and you hand over to the client. If the partner worked in your repository, the most important part is already done because the code is with you. The partner should deliver the documentation in your format and under your name.

Clarify in advance who carries out the training. It is usual for the agency to lead it and for the partner to support technical questions in the background. After the Magento handover the partner can take over maintenance if you wish. Available packages are listed under maintenance packages.

6. Checklist: seven points for the Magento handover

If you can tick off these points, the Magento handover is complete for most projects. Who takes over maintenance afterwards should be in the quote. How to calculate that is described in the guide Calculating a Magento quote.

7. Common misconceptions about the Magento handover

The first misconception: if the shop runs, the project is finished. Without documentation and regulated access it is only finished as long as the same people are available. The second misconception: a handover causes extra costs the client does not want to pay. In fact the cost of the Magento handover is small compared with the cost of a later clean-up.

The third misconception: the client does not need technical details. They do not need them in daily life, but they need the certainty that they exist. Whoever works with a new provider saves time and money when a handover exists. This applies even if you get the job again later yourself.

8. How we shape the Magento handover for agencies

We are a web agency in which fixed freelancers work together, all remotely from home offices. The Magento handover is part of the project with us: the code lives in your repository, documentation is created during the work, and on request we support the training in the background. The hourly rate is 30 euros net, and there is no minimum order.

You find the cooperation at a glance on the page White label for agencies, and requests go through Partnership and cooperation. This article is general orientation and not legal advice.

9. Summary

A clean Magento handover consists of documentation, access, licenses, operating guide, training and acceptance protocol. It protects client and agency when people or providers change.

Note: This article offers general information and does not replace legal advice in individual cases.

10. FAQ: Magento handover