Prepare a usable operating record
A client needs more than a set of passwords. Provide the canonical website address, ownership map, service inventory, renewal responsibilities and a clear route for routine support. Keep secrets in the appropriate protected account system rather than embedding them in a handoff document. The record should explain what the client owns, what a collaborator operates and which services remain with third parties after the project is delivered.
Use the actual provider handoff model
Cloudways server transfers, team access and application migrations solve different tasks. Choose the one that matches the intended boundary. A fictional client receiving one site from a shared server should not accidentally receive the other clients’ infrastructure. Check the current provider requirements and the receiving account before initiating an ownership change. Where a transfer affects billing or access, make that consequence part of the agreed handoff rather than a hidden technical detail.
Verify useful access without exposing secrets
Confirm that the intended owner can reach the controls they need and that the replacement operator has an appropriate individual role. Avoid sharing account-owner credentials as a substitute for supported delegation. Check one meaningful permitted action or read-only view where possible, while preserving settings and business data. A welcome email or invitation acknowledgement is not by itself proof that the client can operate or recover the website.
Close the loop deliberately
Record outstanding issues, the next renewal and the contact responsible for each unresolved item. Once continuity is verified, remove obsolete access through the authorized process. Do not delete the only recovery record or cancel a service before confirming that it is no longer required. A successful handoff leaves the next person able to make routine decisions without chasing the original developer for every hostname, invoice or support boundary.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Cloudways collaboration and separate application credentials — Merchant documentation · support.cloudways.com · Merchant-controlled · checked 2026-09-21
- Cloudways server transfers: owner and paid-account requirements — Merchant documentation · support.cloudways.com · Merchant-controlled · checked 2026-09-21
- WP Engine site-transfer requirements and extension effects — Alternative provider · wpengine.com · Publisher independence not verified · checked 2026-09-21