Switch WordPress Developers Without Losing Access: Handover Checklist

Switching WordPress developers can feel stressful, especially when your site is busy with bookings, events, and new enquiries. If access is lost or mixed up during the change, it can hurt leads, sales and trust right when you need your website most.

In this guide we share a clear, jargon-free handover checklist. Our aim is simple: help Edinburgh businesses switch WordPress developers without losing logins, data or uptime, and with a smooth start for your new digital partner.

Protect Your Website Before You Change Developers

When the calendar fills up with autumn events, tourism offers and early festive campaigns, your website must be stable, fast and easy to update. Changing your WordPress developer at the wrong time, or in the wrong way, can lead to downtime or lost access at exactly the moment you are pushing traffic to the site.

The risk is not just about code. It is about who controls:

• Your domain name and DNS  
• Hosting and backups  
• Premium licences and integrations  
• Day-to-day content and updates  

If these sit in different accounts, or in your old developer’s name, a rushed switch can leave you locked out or unsure who is responsible for what.

Our goal here is to help you step through the change with confidence. With a bit of planning, you can change WordPress partners while keeping your site live, your logins safe and your team in control.

Confirm Who Owns What in Your WordPress Stack

Before anything else, get clear on ownership. Many businesses in Edinburgh find that domains, licences and tools have been set up over time, often with little documentation.

Start by checking that all key accounts are registered under a company email address that you control. Avoid logins that belong to the outgoing developer or a personal inbox that might vanish if someone leaves your team.

Make a simple asset list that covers:

• Domain registrar and renewal dates  
• Hosting provider and plan type  
• DNS records and who manages them  
• SSL certificate provider and expiry dates  
• Premium themes and plugin licences, and who owns them  
• Email services, such as transactional email or marketing tools  
• Any custom integrations, such as booking systems or payment gateways  

This list should show what you own directly, what your developer pays for on your behalf, and what might need to be moved. It gives your new WordPress developers a clear map of your current setup and reduces nasty surprises later.

Secure and Organise Access Before the Handover

Once you know who owns what, the next step is to lock down and organise access. At a minimum, your business should control:

• WordPress admin logins  
• Hosting control panel access  
• SFTP or SSH logins  
• Database access, often via a control panel  
• DNS logins for your domain  
• Analytics and tag manager accounts  
• Backup services and monitoring tools  

Before you change developers, follow some simple security steps. Change passwords on key accounts, turn on two-factor authentication where possible, and remove old or inactive users from WordPress and other tools. For your new agency, create role-based logins so they have what they need, but not broad access under a shared personal account.

It is worth deciding how you will store and share credentials inside your business. A password manager with shared vaults, clear naming conventions and an access log is usually far safer than random spreadsheets and emails. When everything is neat and central, future WordPress partners can get started quickly without having to chase missing details.

Request a Proper Technical Handover Pack

A clean break needs a proper technical handover. Ask your outgoing developer to prepare a pack that covers both code and configuration, not just a few loose logins.

At a minimum, request:

• A current full backup of the site files and database  
• Theme and child theme files  
• Any custom plugins or bespoke code  
• Exported settings for key plugins where possible  

On top of that, there are configuration details that save a lot of time for your new WordPress team. Ask for notes on:

• Staging environments and how to access them  
• Cron jobs or scheduled tasks  
• Caching rules at both server and plugin level  
• Redirect rules, including any from older domains  
• Form settings, including where enquiries are sent  
• API keys and connection notes for third-party services  

If you can, also request a short site status summary. This might include known bugs, performance issues, security concerns and any upcoming licence renewals. It does not need to be long, just honest. A few clear notes can stop your new agency wasting time guessing how the site was put together.

Choose New WordPress Developers in Edinburgh Wisely

Once your assets and access are in order, you can focus on finding the right new partner. For most Edinburgh businesses, that means a team that understands WordPress deeply and also understands how local organisations work.

When you speak with new WordPress developers in Edinburgh, look for:

• A portfolio that shows they can handle projects like yours  
• Clear skill with performance, security and accessibility  
• Ongoing support options, not just one-off builds  

Ask specific questions about how they onboard new sites. How do they review an inherited build? What is their disaster recovery plan? How will they communicate during the first few months? Also ask how they handle future handovers if you decide to move again one day. A good partner will not be defensive about this.

There is real value in working with a long-term support and management partner rather than only a project-based developer. Managed hosting, monitoring and proactive maintenance often mean fewer surprises and a more predictable website for your internal team and your customers.

Go Live with Confidence and Plan the First 90 Days

When it is time to switch, treat the handover like a mini launch. Agree a clear timeline with both your old and new developers so there is no confusion about who is responsible at each step.

Try to:

• Schedule DNS changes and hosting moves in low-traffic windows  
• Have a rollback plan so you can revert if something fails  
• Decide who is checking forms, payments and key pages after the move  

After your new WordPress developers are in place, the first 90 days are about stabilising and improving. A simple checklist helps:

• Monitor uptime and respond quickly to alerts  
• Test critical user journeys like enquiries, bookings and purchases  
• Review analytics to see how users behave across devices  
• Tidy content and update key landing pages  
• Work on page speed, especially for mobile visitors  

Finally, build habits that make any future change easier. Keep an up-to-date asset register, set reminders for renewals and licences, and review who has access to what every few months. With these basics in place, you keep control of your WordPress site, no matter which developers you work with in the future.

At Nimble Digital UK in Edinburgh, we focus on designing, developing and supporting high-performing WordPress websites, along with consultancy, hosting, security and ongoing management. With a structured handover and the right partner, switching developers can be calm, orderly and a positive step for your business.

Get Started With Your Project Today

If you are ready to improve your online presence, our experienced WordPress developers in Edinburgh are here to help. At Nimble Digital UK, we work closely with you to understand your goals and create a site that genuinely supports your business. Tell us what you need and we will recommend a clear, practical way forward. To discuss your project and timelines, simply contact us today.