A website handover should leave you knowing what you have, how to access it and who looks after it. These details are easier to agree before launch, while the scope and responsibilities are being discussed.
Make an account and access list
Record the domain registrar, hosting provider, content-management system, website repository where applicable, and connected services. Include who controls each account, who pays for it and how access is recovered if the usual contact is unavailable.
The website and business email may use separate services even when they share a domain. Before a move, identify which settings relate to each. A website launch should have a specific migration plan rather than a blanket change to everything attached to the domain.
Put ownership and licences in writing
Ask the proposal and contract to explain which deliverables you receive, when any agreed rights transfer and which elements depend on third-party licences. Discuss code, written content, photographs, fonts, themes and plugins separately where their terms differ.
Account access, copyright and permission to use a paid product are different questions. Do not assume that paying a build invoice answers all of them. Have any unclear contractual terms explained before agreeing them; this article is a planning checklist, not a determination of your legal rights.
Decide who makes everyday updates
Identify the changes you expect to make yourself: editing a service description, adding an article or updating a product. Ask to try those tasks during handover. Agree what training or written guidance is included, and which changes need developer involvement.
Keep the level of access appropriate to the task. The government's business account security guidance recommends reviewing access, using multi-factor authentication where available, keeping software updated and backing up important information. Decide who owns those tasks for your website.
Separate hosting from website care
Hosting provides the environment where the site runs. A care agreement may cover some combination of software updates, backups, monitoring, small content changes and support. The exact responsibilities depend on the chosen platform and agreement; hosting alone does not explain which of these services you are buying.
- What is backed up, how often, and how would restoration be checked?
- Who applies updates and tests the important journeys afterwards?
- How do you report a problem, and what response arrangements have been agreed?
- Which content changes are included, and how is extra work quoted?
- Who handles issues with a booking tool, payment provider or other connected service?
For applications and automation, also agree who monitors failed jobs, manages changing integrations and reviews provider usage costs. Support should have a defined scope rather than an assumption that every future change is included.
Leave with a usable handover
Request the agreed access, a renewal and subscription list, a guide to common updates and the support contact details. Record any remaining issues and how they will be handled. Discuss data export and the practical steps for changing supplier if that becomes necessary.
Digital Marvels can discuss website care, application support and automation maintenance alongside the initial project, with scope and costs agreed separately where relevant. Read about ongoing support or discuss your website.
Ready to discuss your requirements?
Tell us about the website or workflow you want to improve.