The most expensive handovers often begin with a website that looks fine but has missing access, unknown licenses or backups nobody has tested. A receiving agency cannot safely maintain what it cannot inventory. This guide gives business owners and new technical teams a concrete transfer checklist.
Prove ownership and access before editing
Confirm who owns the domain registration, DNS, hosting account, CMS administrator access and business email systems. Ask for a named account owner, not just a temporary username. Record whether the current supplier uses shared agency logins or service accounts. Decide which access should remain after handover and which should be revoked.
Use a secure credential-transfer process and rotate credentials when responsibility changes. Do not ask anyone to email a master password in plain text. Before switching DNS or replacing plugins, verify that the new team can reach the hosting control panel and the recovery channel.
Collect a full technical inventory
Record WordPress core version, active theme and child theme, installed plugins, PHP version, web server configuration, scheduled tasks, external integrations, caching layers and transactional mail setup. Note every paid license and who is billed. A plugin that continues functioning today can still become a maintenance risk when a license expires.
For each integration, identify the business purpose, account owner and failure impact. Payment providers, booking platforms, CRM forms and analytics often use separate credentials. Do not copy secrets into the handover document; record how authorized staff can access them securely.
Verify backup and rollback capability
Ask for the backup schedule, storage location, retention policy and evidence that a restore was recently tested. A downloadable archive is not proof the website can be recovered. Check whether file backups and database backups belong to the same restore point.
Before a redesign or major plugin update, save a clean snapshot and decide who can authorize a rollback. Test staging if available. If a supplier says backups are automatic, request the restoration procedure and expected recovery window in writing.
Preserve redirects, analytics and search configuration
Export the important URL list and any redirect rules before changing page structures. Confirm access to Search Console and analytics accounts, XML sitemaps, robots.txt, canonical rules and event-tracking definitions. Losing URL history can create search problems even when the new site design is better.
Make a short list of high-value pages and forms to verify immediately after the handover. The indexing troubleshooting guide explains why crawled pages can still fail to appear in Google.
Turn the inventory into a signed operating plan
Ask who is responsible for updates, uptime checks, vulnerability response, renewal payments, content changes and emergency escalation. Establish the first 30-day priorities with one named owner per item. A handover is finished when the new team can operate the system safely, not when they receive a ZIP file.
The Site Audit and Technical Handover tool is designed around these checks. For managed development or an agency transition, explore Versys Media website services.
Example handover: a contact form suddenly stops sending
A new agency inherits a WordPress website with contact forms that apparently work. Two weeks later, enquiries stop arriving. The site accepts the submission, but the transactional mail account was owned by the previous supplier. Without an integration inventory, the failure looks like a plugin bug and wastes time across several teams.
A complete handover would record the form plugin, outbound mail provider, account owner, where delivery failures are logged, the sending domain, and who can authorize repairs. It would also specify a test submission after any change to hosting or DNS. The secret itself should stay in a controlled credential store, not in a PDF handed around by email.
Use a sign-off list with columns for asset, owner, access confirmed, backup confirmed and outstanding risk. If the former agency cannot supply a detail, label it unknown and create a recovery task. Silence is not evidence the service is working, and a rushed handover is not a reason to guess.
Takeaway checklist
- Transfer domain, DNS, hosting and WordPress account ownership.
- Inventory plugins, themes, integrations and paid licenses.
- Test a database and file restoration path.
- Save canonical URLs, redirect rules and analytics access.
- Assign maintenance and incident responsibilities in writing.
What to do next
Choose one improvement you can complete in the next working week. Write down who owns it, what evidence will show it is working, and how you will check again after rollout. A small, well-tested change is more useful than adding features nobody monitors.
For hands-on help with a business-specific workflow, explore Versys Media or the Versys Apps directory. Bring the process you want to improve, not just a request to add AI everywhere.
