What should I get from my web developer before switching to someone new?

List every account the website depends on, because developers often set things up in places the owner never sees. The domain registrar and the hosting control panel are the most critical; without them you cannot move or even fix the site. Then the WordPress or other admin login with full administrator rights, database access, file access, and any email accounts on the domain. Add the marketing accounts: Google Search Console, Google Analytics, Google Tag Manager, your Google Business Profile, the Meta pixel and any ad accounts. Make sure you are an owner or admin on each, not a guest.

Next, the assets. Ask for a full backup of files and database, downloaded to storage you control, along with original design files, logos and photos if they hold them. If the site uses paid themes or plugins, find out whose account the licences are under; some cannot be transferred and will need buying again. Ask for a short note of anything unusual: custom code, scheduled tasks, third-party services connected, and when each renewal is due.

Then confirm and secure. Log in to each account yourself to check access works. Once your new developer has what they need, change passwords and remove the old developer's user accounts, politely and without drama. Do all of this while the relationship is still friendly, since cooperation is far harder to get after a disagreement. If we take over your site, our maintenance service starts with exactly this checklist during the free audit, and for sites built under the Business bundle you hold these logins from the beginning.