Drupal site handover
A CMS is a complex piece of software. The hosting and development processes can be involved and it is important to have those key aspects documented so that the client's team is able to work effectively on the site.
Morpht provides handover documentation including:
- Content model
- Functional specification
- Handover documentation covering key systems and build processes.
Frequently asked questions
A thorough handover includes documentation of the content model, custom functionality and integrations, admin/editor training if it wasn't already delivered, a clear picture of hosting and support arrangements, and ideally a warranty or transition period where the outgoing team is available to answer questions. Incomplete handovers are a major source of operational risk when an agency changes providers or brings work in-house.
Confirm all code, configuration and content are genuinely in your organisation's control (not locked to the agency's infrastructure or accounts), that documentation exists for anything custom-built, that there's no vendor lock-in preventing a future provider from taking over, and that credentials/access have been properly transferred rather than shared.
Yes. The same documentation and knowledge-transfer needs apply whether you're moving to a new external partner or building internal capability; the risk of tribal knowledge walking out the door with an outgoing team is the same either way.
Related content
