# Website Handover Checklist For Northern Ireland Businesses Changing Developer

URL: https://www.starien.com/blog/website-handover-checklist-for-northern-ireland-businesses
Published: 2026-11-05
Author: Geoffrey Moffett
Topics: website handover, web developers, website ownership, Northern Ireland, checklist

> Changing web developer in Northern Ireland? Use this website handover checklist to collect logins, code, domains, licences and documentation before anyone walks away.

## Quick answer

A good website handover gives you full admin access to the domain, DNS, hosting, website and every connected tool, plus a recent backup, the code, licence details and short documentation. Collect everything in a business-owned password manager before the old developer steps away, then check each login works and change passwords once the new team is in place.

## Key takeaways

- Gather every login before the relationship ends, not after.
- The domain and DNS are the most important things to control.
- Ask for a full backup, the code and a list of premium licences and integrations.
- Change passwords and remove old access once the handover is confirmed.

Changing web developer happens for all sorts of reasons. Someone retires, an agency closes, prices go up or you simply want a fresh pair of hands. Whatever the reason, a messy handover can leave you locked out of your own website. This website handover checklist for Northern Ireland businesses walks you through everything to collect, in the order that matters.

## Why Handovers Go Wrong

Most handover headaches aren't about bad intentions. They're about nobody writing anything down. The domain was registered years ago on someone's personal email. The hosting runs on the agency's account. A premium plugin licence is in the developer's name. Everything worked fine, until the people changed.

The fix is simple: collect it all while everyone's still on speaking terms.

## Website Handover Checklist For Northern Ireland Businesses

Work through these in order. The first items are the ones that would hurt most to lose.

### 1. Domain Name

- Registrar name (the company where the domain is registered).
- Login to the registrar account, or confirmation the domain has been moved to an account in your business's name.
- Renewal date and whether auto-renew is on.
- Confirmation the registrant contact is your business, not the developer.

### 2. DNS

- Where DNS is managed (sometimes the registrar, sometimes the host, sometimes a separate service).
- A copy of all DNS records, including email records. Getting this wrong is how businesses lose their email during a move.

### 3. Hosting

- Hosting provider and plan.
- Login, or a plan to move the site to a hosting account you control.
- Server details your new developer will need.

### 4. Website Admin

- An administrator account in your name, not a shared login.
- A list of all user accounts and who they belong to.

### 5. Backups And Code

- A full, recent backup of files and database, stored somewhere you control.
- Theme and custom code, ideally in a version control repository you have access to.
- Any build steps or tools needed to work on the code.

### 6. Licences And Subscriptions

- Premium themes and plugins: licence keys, renewal dates and whose account they're on.
- Fonts, stock images and other paid assets.
- Third-party services the site uses, such as forms, maps, booking or email marketing.

### 7. Integrations And Keys

- Which tools connect to the website, and how.
- API keys and where they're stored. These should be moved to accounts your business owns.

### 8. Analytics And Search

- Admin access to analytics and Google Search Console.
- Google Business Profile access if the developer managed it.
- Tag manager or tracking accounts.

### 9. Email

- Where business email is hosted, and admin access.
- Email authentication records (SPF, DKIM and DMARC) noted down.

### 10. Documentation

- A short note on how the site is set up, anything unusual, and known issues.
- Any outstanding jobs or bugs.

## How To Ask For It Politely

Send one clear, friendly email listing what you need, with a reasonable deadline. Thank them for their work. Most developers are happy to help a smooth exit, especially when it's organised. Keep the conversation in writing, so there's a record of what was agreed.

If you're mid-contract, check the terms first. Some agreements cover handover fees or notice periods.

## After The Handover

1. **Test every login.** Before the old developer steps away entirely.
2. **Take your own backup.** Store it separately.
3. **Bring the new developer in.** Let them review everything and flag gaps.
4. **Change passwords.** Once everything's confirmed working.
5. **Remove old access.** Admin accounts, hosting users and API keys belonging to the previous team.
6. **Store everything in a password manager** owned by the business, with at least two people having access.

## What A Good Handover Document Looks Like

You don't need a technical manual. One or two pages is plenty, written so a new developer can get their bearings in an hour rather than a week. Ask for something like this:

- **Overview:** what platform the site runs on, which theme it uses and whether there's any custom code.
- **Where things live:** registrar, DNS, hosting, email, backups and code repository.
- **Key plugins or features:** what each one does and why it was chosen.
- **Integrations:** forms, booking, payments, CRM or email marketing connections, and how they're set up.
- **Scheduled tasks:** anything that runs automatically, such as imports, feeds or reminder emails.
- **Known quirks:** "the events page breaks if you leave the end date blank", that sort of thing.
- **Open issues:** bugs, half-finished jobs and anything promised but not delivered.

Even a rough document saves your new developer hours of detective work, and those hours are usually billed to you. It also helps your own team understand what they actually have.

## Timing The Switch

Avoid changing developers right before your busiest season. For a Causeway Coast tourism business, that might mean handling the move in autumn or winter rather than June. For a retailer, avoid the run-up to Christmas. Give yourself a few calm weeks where both the old and new teams are reachable, just in case something has been missed.

## When Access Can't Be Recovered

Occasionally a developer has vanished or won't respond. Don't panic. If the domain is registered to your business, the registrar can usually help you regain control with proof of identity. Hosting providers have similar processes. Your new developer can often rebuild access to the website itself from the hosting side.

The hardest case is a domain registered in someone else's name. That's why checking registrant details matters so much, today, before you need it.

## Make The Next Handover Easier

Once everything's in your hands, keep it that way. Hold your own logins, keep a simple record of where things live and review it once a year. Our guide to [who owns your website in Northern Ireland](/blog/who-owns-your-website-in-northern-ireland-code-content-and-logins/) covers the ownership side in more detail.

If you're changing developer and want a calm pair of hands, our [web development](/web-development/) team can take over, check the handover and fill any gaps. And the [Orbit monthly website plan](/orbit/) keeps your site updated afterwards, with everything held in your business's name.

## Frequently asked questions

### What should a web developer hand over when I leave?

Admin access to your domain registrar, DNS, hosting and website, a full backup, the code or theme files, details of premium licences and integrations, and any notes on how the site is set up.

### What if my old developer won't hand over access?

Start with what you can prove you own, such as the domain registered in your business name. Check your contract, keep communication polite and written, and ask your new developer to help recover access through the registrar or host.

### Should I change passwords after a handover?

Yes. Once the new team has confirmed everything works, change passwords and remove the old developer's user accounts and API keys.
