Taking Over From a Previous Developer

Agency relationships end, freelancers move on, and in-house developers leave. When that happens with a business-critical website, the business is often left without anyone who properly understands the system. Decisions made during the original build, bespoke functionality that was never documented, integrations that nobody outside the original developer knows how to maintain: these become problems quickly when something needs fixing or the platform needs updating.

Expression 37 regularly takes over ExpressionEngine and Craft CMS sites that have been left without adequate support. The process starts with understanding what exists, not making changes, and builds from there into a stable, properly supported arrangement.

How a Transition Typically Works

• An initial review of the site, its codebase, installed plugins and add-ons, hosting setup, and any integrations
• A written assessment covering the current state of the site, any issues or risks identified, and recommendations for what needs addressing
• A clear conversation about what ongoing support looks like before any commitment is made
• Where access credentials or documentation are incomplete, a structured process to piece together what exists
• Gradual assumption of full responsibility for the site, with any pressing issues addressed first

Common questions:

Can you take over a site you had no involvement in building?

Yes. This is one of the most common starting points for new clients. Every site has its own history and its own accumulated complexity, and understanding that properly before touching anything is the only responsible way to proceed. The audit phase at the start of a new engagement exists specifically to build that understanding.

We do not have complete documentation or access credentials. Is that a problem?

It is common. Many sites that come to us after an agency relationship ends are missing proper documentation, and access credentials are sometimes incomplete or out of date. We work methodically through what is available and flag anything that needs to be resolved. It adds some time to the initial assessment phase, but it does not prevent us from taking over.

The previous developer left on difficult terms and we are concerned about what was done to the site. Can you assess it?

Yes. Where there is any concern about the state of the site, a proper security and code review is the right starting point. We can assess the codebase for any obvious issues, check access logs where available, and advise on what, if anything, needs to be addressed. A clear-eyed assessment is more useful than either reassurance or alarm.

How quickly can you take over?

That depends on the complexity of the site and what access and documentation are available. Simple sites with clear codebases can often be taken over and stabilised within a week or two. Larger or more complex sites, or those with significant gaps in documentation, take longer to assess properly. We give a realistic timeline after the initial review.

Will we need to move hosting as part of the transition?

Not necessarily. We assess the current hosting as part of the initial review and advise on whether it is adequate. Where a move would benefit the site, that is flagged and can be planned separately. Where the existing hosting is fine, there is no reason to move it.

Get in Touch

To discuss taking over your ExpressionEngine or Craft CMS site, call Karl directly on 01924 501 813 or 07771 656 606, or use the contact form.