What should happen when a new team takes over a WordPress site?
A WordPress takeover should begin with ownership and access, a restorable backup, a dependency inventory and a written risk assessment. Do not update production or promise a rebuild before the new team can reproduce the issue and understand the hosting, integrations and rollback path. The first goal is a safe, shared picture of the system.
Last reviewed
A handover is not just an administrator login
The working site may depend on a host, DNS, payment account, email sender, scheduled jobs, licences, repositories and undocumented integrations. A missing credential or expired licence can turn a routine patch into an outage. Establish who owns each dependency before changing it.
Take control in a reversible order
- Confirm the legal owner and obtain authorised administrator, hosting, DNS and repository access.
- Create a backup and verify that it can be restored to a controlled environment.
- Inventory themes, plugins, custom code, external APIs, cron jobs and email delivery.
- Record current errors, performance and critical customer journeys before changes.
- Agree the first repair, acceptance test, rollback plan and escalation contact in writing.
Stabilize before improving
Separate immediate security or availability risks from planned enhancements. Patch in staging where possible, test forms, checkout and integrations, then promote one reversible change at a time. Kaprel’s case study shows a takeover where the existing foundation, not just one symptom, required a rebuild; other sites may need only a targeted repair.
Keep a baseline for the next team
Record backup restore status, software inventory, error logs, critical journey results and page performance at takeover. Repeat those checks after the first changes and keep the evidence with the handover notes.
Common questions
What access should a new WordPress developer receive?
Only the access needed for the agreed assessment, through named accounts with appropriate privileges. Confirm ownership and use secure transfer.
Should the new team update everything at once?
No. Inventory and stage updates, then test the critical journeys and rollback path.
What if nobody knows where the site is hosted?
Trace domain, DNS, billing and server ownership before making changes. Preserve current access and document the verified account owner.
When should a takeover become a rebuild?
When the assessed architecture prevents safe, maintainable repair and the business case supports replacing it. Document the evidence and alternatives first.
Kaprel: taking over an abandoned catalogue build
The previous team had left the project mid-build; pages took around ten seconds on average and fifteen to twenty on the worst pages. The rebuild brought them under one second with the media retained.
Get the handoff measured before changing it.
Send the URL. We will write up what we can verify and what remains unknown within two working days.