Blog article

Changing your website developer? What to collect before the handover

Changing your website developer? Use this website handover checklist to review access, files, backups, email, enquiries and support before the transition.

Original conceptual WebBuild illustration of a ring holding two keys and an access tag, representing access and responsibility during a website handover.
Original conceptual illustration; not a client's accounts, credentials or handover record.

The short answer

Identify the accounts and material the incoming developer needs, agree who supplies and checks each item, and verify publishing, recovery and important customer tasks before closing the previous arrangement. Keep domain, hosting, email and connected services distinct. Use the assessment to decide what can stay and what work needs a separate scope.

You want a new developer to look after your business website. Perhaps some work is unfinished, your requirements have changed, or you need a different support arrangement. Before agreeing what happens next, establish what the incoming team can access and what they will be responsible for.

A website handover should leave the business with usable access, the agreed project material and a record of how important tasks work. The new developer needs enough information to assess the existing website before recommending routine support, repairs or a wider rebuild.

Start the handover while the current provider is available. Keep the request factual: what needs to be supplied, who will receive it and how each item will be checked. Changing providers can be a practical transition without turning the conversation into a dispute.

Separate the handover from a rebuild decision

Changing the person maintaining a website and replacing the website are separate decisions. A new developer may be able to maintain the current setup, finish a defined piece of work or fix a specific problem. Some systems need more investigation before anyone can responsibly quote for ongoing support.

Ask for an initial assessment covering the platform, available access, important functions and known problems. List the changes you want and the parts that already work well. A replacement proposal should explain which requirement justifies it and what the business will need to operate afterward.

If the main difficulty is an unfinished AI-assisted draft, our Lovable completion guide explains how to compare continuing on the platform with developer help. For an established website, the redesign or targeted improvements guide helps frame the scope.

Confirm the domain, hosting and editing access

Write down the provider and responsible account for each service. Your domain registration, website hosting and business email may be handled by different companies, even if one agency sends the invoices.

For the domain, identify the registrar, registrant details, renewal arrangements and who can manage its settings. ICANN's registrant guidance explains that paying a third party to register a domain does not establish whose details are recorded as the registrant. Check the record with the registrar rather than relying only on an invoice.

Confirm who can manage hosting, the website editor and any separate deployment account. Ask whether the business has its own account, delegated access or a managed service under the provider's account. Those arrangements have different handover requirements. Record what can be transferred and what needs a replacement account or a continuing agreement.

Use separate named user access where the service supports it. Arrange private access through an agreed secure channel, including the recovery process and multi-factor authentication where relevant. Keep passwords, access tokens and recovery codes out of a public brief or general handover spreadsheet.

Changing your developer does not automatically require changing your domain registrar. A hosting move also needs its own arrangements; ICANN distinguishes web hosting changes from registration issues. Ask the incoming team to explain which account or service actually needs to move and why.

Collect material that someone else can use

Request the project material included in the agreed handover. Depending on the website, that may include source files, database and media exports, approved design files, content, configuration instructions and a list of connected services. Ask which version matches the live website.

For a custom build, the developer should explain how the files become the running website, what software or services it depends on and how changes are released. Receiving a folder does not demonstrate that the next team can build, deploy or maintain it. Arrange a suitable demonstration on a separate environment.

Where a source repository is involved, agree the appropriate business account and permissions. GitHub's transfer documentation notes that collaborators and connected items can persist through a transfer. Ask the technical team to review the remaining access and deployment connections; a transfer is not automatically a complete offboarding process.

Record the owner, billing contact and renewal date for paid themes, plugins, fonts and connected services. Ask which licences or assets can continue under the new arrangement and which require a separate purchase or permission. Keep those decisions in the scope so a working feature does not become an unexpected renewal or replacement job.

A backup needs a recovery check. For WordPress, the official backup guidance explains that a typical full restoration needs both database and files. Other platforms have their own recovery requirements. Agree what will be restored, where it will be tested and who records the result. Our website backup checklist covers that assessment in more detail.

Protect business email and the enquiry route

Identify the email provider before changing hosting or domain settings. Ask which mailboxes, aliases and website-sending services the business uses, and who is responsible for keeping them working.

DNS settings can direct different services for the same domain. For incoming email, MX records identify the mail destination, as Google's email setup guidance explains. A website hosting change does not establish that email has moved or that its settings should be replaced. Follow the instructions for the business's actual providers.

One domain, separate services

Check both destinations before changing the website.

Domain and DNS
Identify who can manage the domain settings and which services depend on them.
Website destination
Confirm the website host and the arrangements for any agreed website move.
Incoming email destination
Confirm the email provider and preserve or deliberately update its records with the responsible administrator.
Conceptual service map using reserved example addresses, not a client's DNS configuration. Labelled lines show separate service dependencies, not automatic transfers. Website-form delivery needs its own receiving-system check.

Document the enquiry route separately. A website form may store submissions, send an email, create a CRM record or do several of these. Record the destination, notification recipient and person who follows up. Include any booking, payment or account function the business relies on.

Agree a test that follows a submission from the website through to the receiving record. Then confirm the staff notification and normal follow-up process. A success message on the page is only one observation. Our lead capture guide explains the checks beyond the visible form.

If new records arrive while a move is taking place, agree how they will be retained and reconciled. Restoring an older website copy does not automatically include activity received by a replacement system. Keep that responsibility explicit in the release and recovery plan.

Retain search and measurement access

Include the existing page addresses, redirects and sitemap in the handover record. Record which analytics and search accounts the business uses and whether the incoming provider has the appropriate access. Changing the maintainer should not accidentally replace useful page addresses or lose the team's ability to review search data.

Google distinguishes verified owners, delegated owners and users in Search Console's permissions guidance. Confirm the business has suitable ownership access before changing the previous provider's permissions. Google also explains that verification tokens can affect continuing access and may be used by other services. Have the responsible administrator review these dependencies before removal.

If the handover includes new hosting, plan and test that move separately. Google's hosting-change guidance covers a move where public URLs remain the same. A provider should describe the checks and monitoring without promising unchanged rankings. Our redesign and SEO guide covers the broader case where content or addresses also change.

Agree what counts as a completed handover

For each important item, name the person supplying it, the person checking it and the observation that will confirm it works. An account invitation might be received today while the publishing check remains open. Keep those states distinct.

Useful acceptance checks include:

  • A business representative can access the relevant account and knows the recovery route.
  • An editor makes an agreed change, publishes it and verifies the public result.
  • The incoming developer can use the supplied material in a suitable test environment.
  • A backup is restored in an agreed exercise, with limitations recorded.
  • A test enquiry reaches the receiving system and the responsible person.
  • Continuing licences, renewals and support responsibilities are documented.

Use our blank website handover record to track the items, responsible people, checks and unresolved gaps. It contains no client information. Record account references rather than credentials, and store the completed record privately.

Keep old services available for the agreed transition period. Close or change access after the required checks and business authorization, taking account of dependencies. Where the provider cannot supply an item, record the gap and ask what it means for the proposed work. Missing access may change the scope, cost or feasibility; a new developer cannot promise recovery before reviewing the situation.

Compare the work and ongoing costs

Ask the incoming provider to separate the handover assessment, immediate fixes, any migration work and ongoing support. Clarify the material or access you must supply, exclusions and the process for approving additional work.

Recurring costs may include hosting, domain renewals, email, licences and connected services. Identify who pays each bill, the renewal terms and what happens if a subscription ends. A low monthly support figure is difficult to compare without knowing the tasks and response arrangements included.

The support proposal should explain routine updates, backups, release checks and how problems are reported. Include how your staff will request content changes and what needs a separate estimate. Those details help you compare the full arrangement with keeping the existing provider or commissioning a limited repair.

Ask WebBuild to assess the handover

Share your public website address, what you want to change and the access or documentation you already know is available. Tell us which functions must keep working and any planned end date for the current support arrangement. We can discuss an assessment of the existing website, the handover gaps and the next work to scope.

Arrange private access separately after the review scope is agreed. An initial enquiry does not need account passwords, customer records or a full database copy.

Discuss website maintenance and handover with WebBuild, or explore technical consulting if you need help comparing the options before choosing a new development arrangement.

A WebBuild project offer

Could your website be doing more for your business?

Share your website and request a complimentary initial assessment of its design, usability, performance and enquiry experience.

10%OFF

Quoted WebBuild service fees

Up to US$300 per project, or the equivalent confirmed in your quote.

Complimentary Initial Website Assessment

Terms & conditions apply

Tell us about your project

Start with your details. We’ll discuss the right next step.

Which describes your project?

Security check

Preparing the security check…

This form uses Cloudflare Turnstile to prevent spam. If the check does not load, email your request or call +91 968 502 1028.

We use your details to respond; this does not subscribe you to marketing. Privacy Policy · Terms & conditions apply.

Preparing the security check…

Questions covered in this guide

Do we need a new website when changing developer?

Not necessarily. Ask for an assessment of the current setup, available access, problems and support requirements. Maintaining the existing website, targeted repairs and a rebuild are different scopes to compare.

Is receiving the account details enough to complete the handover?

Verify that the agreed people can use their access and complete the necessary tasks. Record publishing, recovery and enquiry-delivery checks separately from receiving an invitation or a file.

Will moving the website also move our business email?

Do not assume that it will. Confirm the email provider, relevant domain settings and continuity arrangements separately. The website and incoming mail can have different destinations and account responsibilities.

What if the previous developer cannot supply something?

Record the missing access or material and ask the incoming team to assess the consequence. It may affect the scope, price or feasibility of the work. Agree the available provider-recovery or replacement options before promising a completed takeover.

Sources and project context

Turn the question into a clear next step.

Tell us about your current setup, the people using it and what needs to improve.

Keep exploring

Related reading

Chat with us