Changing Website Developers? What Access Should Your Company Receive?

A person hands over a blue folder to a company representative across a table with a checklist and pen.

When changing website developers, start with the access your company needs to keep operating. Your team should know who can renew the domain, restore a backup, manage email and receive customer enquiries. Ask for access through accounts your company controls and test each essential function before completing the handover.

Access to include in the handover

  • Domain and DNS. Record the registrar, the registered holder, the renewal date and who pays for it. Confirm that your company can manage the domain and its DNS records, including records used for email. If these use different providers, record both.
  • Hosting and backups. Confirm how your company accesses the hosting account or gets support, along with billing and the renewal date. Ask for a copy of the files and database, the date of the latest backup and instructions for restoring it. If the hosting account also serves other clients, use access specific to your website or agree a migration plan.
  • WordPress, code and licences. Test a company-controlled WordPress Administrator account. Ask for the list of themes, plugins, snippets and integrations, plus the location of code and any design files included in the handover. Record who owns each licence and when it renews so your team knows what to renew or replace.
  • Email and enquiries. Confirm email administrator access, where website forms send enquiries and which account sends site emails. If you take payments or bookings, also check company access to the relevant order, booking and payment accounts.
  • Analytics and search. Request access to the existing Google Analytics property. In Search Console, verify a company representative as an owner so the company can manage access to the property in use.

Test access together before closing the handover

  1. Open each account using a company login. Confirm that the team responsible controls the recovery email and two-factor authentication.
  2. Test the website, incoming and outgoing email, form delivery and essential features such as checkout where applicable. Restore a backup on staging if possible to check that the copy is usable.
  3. Record the result for each asset. Note the owner account, what you tested successfully, what remains open, who is responsible and the target date.

Give the incoming developer a separate account with the access their work requires. Once company access and integrations are verified, remove any permissions the outgoing developer no longer needs. If passwords or integration keys were shared, plan their replacement around the systems that depend on them and retest those systems after the change.

If the domain is still in the outgoing developer’s account

Start by confirming the registered holder and the registrar’s process. For domains such as .com, ICANN’s guidance distinguishes changing the registered holder from transferring the domain to another registrar. What you need to do depends on the account and the rules for your domain. Save the current DNS records and check how email could be affected before changing any settings.

Once access is verified, decide who will handle backups, updates and monitoring. Explore alfatihstudio’s website maintenance service if your company needs ongoing support after the handover.

Frequently asked questions

It depends on who controls the registration and what access is already in place. If the company can manage the domain and its renewal, it can stay with the current registrar. Check the registrar’s process if you need to change access or the registered holder.

Administrator access covers management within WordPress. Also check access to the domain, DNS, hosting, backups, email and the third-party accounts your website uses.

Remove it once your company has tested owner access, confirmed essential functions work and recorded anything still outstanding. Review user accounts, provider permissions and any integration keys that were shared.

Related articles