Handing your ExpressionEngine site over to a new developer is not simply a matter of sharing login credentials and moving on. Done without care, a developer transition can leave your site in a poorly documented state, expose vulnerabilities, or result in a new agency spending significant time trying to understand a platform they did not build. The questions worth asking before the process begins will determine how smoothly it goes.
What documentation exists?
The first question is about documentation. Does the current developer have records of what addons are installed and why, what custom templates do, where integrations connect to, and what the site depends on to function? If the answer is no, the handover process should begin with a structured audit before any credentials change hands. Documentation gaps discovered after the previous developer is no longer engaged are considerably more expensive to fill.
Who holds the credentials?
Access to the ExpressionEngine control panel, the server, the domain registrar, and any third-party services connected to the site should all be verified before the transition. It is common for credentials to be held by the outgoing agency rather than the business, and discovering that after the relationship has ended can cause real operational problems.
What is the current technical state?
Before accepting responsibility for an ExpressionEngine site, a new developer should understand its current condition: the EE version, the PHP version, the state of addons, and whether there are any known issues or deferred maintenance. A site audit at the point of handover protects both the business and the incoming developer. It establishes a clear baseline and avoids the incoming developer being held responsible for problems that predate their involvement.
What ongoing commitments exist?
Addon licences, hosting contracts, third-party service subscriptions, and SSL certificate renewals all have renewal dates. Understanding what ongoing commitments the site has, and when they fall, is part of a proper handover. Missing a renewal can cause service interruption or loss of access to tools the site depends on.
The right way to approach the transition
The cleanest handovers happen when the outgoing developer is still engaged and willing to participate. Wherever possible, a structured period of overlap, during which the incoming developer can ask questions and get direct answers, will save time and reduce risk. If the outgoing agency is no longer reachable, a specialist ExpressionEngine developer conducting a thorough audit of the site before taking it on is the next best approach.