← All insights
Business Systems & Operations

If we part ways with our web developer, what do we need from them so we're not locked in?

Changing web developer doesn't have to mean a falling-out, a migration or a new website. Most of the time, what matters is knowing which accounts and files the business should control, and asking for the few that are missing. Here is a practical handover and ownership checklist, plus a polite way to ask.

An old brass key resting on folded papers beside an open wooden box on a slate table

Whatever the reason, the worry is usually the same: if they stopped answering tomorrow, could we still run our website and email? This article helps you answer that calmly. It is not about rebuilding anything. In many cases you'll find you already own most of what matters, and you only need two or three things handed over.

A quick word of reassurance first. Most developers hand over willingly and professionally. Being "locked in" is far more often the result of things never being written down than of anyone holding on deliberately.

Start by checking what you already control

You can do most of this quietly, without raising it with your developer at all. The aim is simply to build a picture.

  1. Look for logins you already have. Search your inbox for emails from your domain registrar, hosting company, Google and any website platform. Welcome emails and renewal reminders tell you which accounts exist and which email address they're registered to.
  2. Check whose name is on the bills. If renewals for the domain or hosting are charged to the developer and re-invoiced to you, the account is probably in their name.
  3. Try logging in. For each account you find, try signing in with your business email. A password reset is a perfectly normal way to test whether an account really belongs to you.
  4. Note the gaps. Anything you can't access, or that's registered to a personal or developer email address, goes on your list.

Keep the results in one simple document. That document becomes the start of your handover record, whatever happens next.

The handover and ownership checklist

Not every item will apply to every business. Work through the list and mark each one as "we control this", "developer controls this" or "not sure".

1. Domain name registrar account

Your domain name (yourbusiness.co.uk) is renewed through a registrar. This is the single most important item. Ideally the registrar account is in the business's name, using a business email address you control. If the developer registered it for you, ask for it to be transferred into an account of your own. Registrars have their own transfer process, so check their help pages for the current steps.

2. DNS access

DNS is the set of instructions that tells the internet where your website and email live. It is often managed at the registrar, but sometimes elsewhere, such as with the host or a separate service. You need to know where it is managed and be able to log in, because changing website host or email provider later means editing these settings.

3. Hosting account and billing

The hosting account is where the website actually runs. Find out who the account belongs to and who pays for it. Shared arrangements, where a developer hosts several clients on one account, are common and not a problem in themselves. But you should know it's happening and what would be needed to move the site if you chose to.

4. Website admin logins

You should have your own administrator login to the website itself, not a shared one and not one belonging to the developer. If your site runs on a website builder or content management system, check that your user has full administrator rights rather than editor-only access.

5. Code, theme files and backups

Ask where the website's files and backups are stored, how often backups run and how you would get a copy. For a custom-built site, ask whether the code is kept in a repository and whether you can be given access. Who owns the code, theme or design is a contractual question; check your own contract, and take advice if it's unclear.

6. Licences for plugins, fonts and images

Paid plugins, premium themes, fonts and stock photos are all licensed, and the licence may be registered to the developer rather than to you. Ask for a list of anything paid-for, whose name the licence is in and when it renews. Some licences can be transferred and some can't, so this is worth knowing before you need it.

7. Email and its DNS records

If your business email uses your domain, a few DNS records keep it working. In plain terms:

  • MX records tell the internet which service receives your email.
  • SPF is a list of services allowed to send email on behalf of your domain.
  • DKIM adds a digital signature to outgoing email so receiving servers can check it's genuine.

You don't need to understand the detail. You need two things: a copy of the current records (a screenshot of the DNS settings is fine), and confidence that nobody will change them without checking. Accidentally altering these during a website move is one of the more common ways a business loses email for a day.

8. Analytics, Search Console and Google Business Profile

These accounts hold your visitor history, search performance and local listing. Google lets accounts have several users with different permission levels, so the business should be an owner or administrator, and the developer can simply be added as a user. Google's own guidance explains the roles in Search Console and Google Analytics. Your Google Business Profile works on a similar owner and manager basis, so check that a business account owns it.

9. Form destinations and connected tools

Find out where each website form sends its enquiries: which email addresses, and whether anything flows into a CRM, mailing list or booking tool. An enquiry form still pointing at a developer's inbox is easy to miss and costly to discover late. If you're not sure what's connected, our article on what should connect to your website is a useful companion.

Forms also collect personal data, so it's sensible to know where that data goes and who can see it. The ICO's guidance for organisations is the place to check your responsibilities; this article isn't legal advice.

10. Documentation

Finally, ask for a short written note covering anything unusual: custom features, scheduled tasks, third-party services, renewal dates. It doesn't need to be long. A page of notes can save a new developer hours.

How to ask, politely

The tone matters. You want cooperation, and most developers are glad to provide it. A short, specific request works far better than a broad "send us everything". For example:

"We're getting our records in order and want to make sure the business holds its own accounts. Could you help us with the following? [list only the items you're missing]. Happy to do it at a time that suits you, and we'd be glad to keep you as a user on anything you still need."

A few practical points:

  • Ask for transfers, not just passwords. Being added as owner is better than borrowing someone else's login.
  • Expect some work to be chargeable. Transferring accounts and writing documentation takes time. Ask for a quote if it isn't covered by your agreement.
  • Change passwords afterwards on anything that was shared, once the handover is complete.
  • If there's a disagreement about ownership of code, design or content, refer to your contract and take proper advice rather than escalating by email.

Hypothetical example

This is a hypothetical example, not a real client.

A family-run joinery firm in Dorset has used the same freelance developer for eight years. He's winding down his business and lets them know with plenty of notice. The owner runs through the checklist and finds:

  • The domain is in the business's name, but the renewal emails go to the developer.
  • Hosting sits on the developer's shared account.
  • The enquiry form sends to two addresses, one of them the developer's.
  • Analytics is owned by the developer's Google account.

Nothing here calls for a new website. The owner asks for four things: update the registrar contact email, add the business as Analytics administrator, remove the developer's address from the form, and write a page of notes on the hosting with a quote for moving it. The developer is happy to help. The hosting move can then be planned calmly, rather than in a hurry.

When you need more than a checklist

For most businesses, the checklist is enough. A bigger piece of work makes sense when the site can't realistically be moved, when key licences or code can't be transferred, or when the handover shows the site no longer fits how the business works. Even then, weigh it carefully; our guide to whether to refresh or rebuild a website sets out how to decide. And if you're collecting proposals from new developers, comparing website quotes explains what to look for, including who will own what.

Your next step

Westward Digital builds websites with connected lead systems for established businesses across Somerset, Devon, Dorset, Bristol and Bath & North East Somerset, with projects from £4,500. Marcus plans the work directly. If you've run the checklist and aren't sure what the gaps mean for your business, get in touch for a straightforward conversation about what, if anything, needs doing.

Working through something similar?

We can help you work out what to address first.

Start a conversation