A professional handover gives the website owner the access and operating information they need while protecting unrelated accounts. Sending a reseller's master password or a shared administrator login creates unnecessary risk and makes later access changes difficult to track.
Recommended steps
- Identify the accounts involved: client area, hosting control panel, website administration, domain registrar, DNS provider and external services. Record which party owns each account and which contact receives renewal notices.
- Provide separate user access with appropriate permissions where the system supports it. Let the owner set their own password through the normal invitation or reset process. Do not reuse a credential already shared with another customer.
- Document the website's platform, document root, database dependency, scheduled tasks and important integrations. Include where backups are stored and the process for requesting a restoration, without embedding secrets in the document.
- Confirm the domain and hosting renewal cycles, current package limits and the scope of any maintenance agreement. Show the customer how to identify their service and open the correct support ticket.
- Test the new access with the owner before removing temporary project permissions. Review remaining developer, contractor and remote administration access, then revoke anything that is no longer required.
Keep the handover record current after a migration or change of supplier. If a login must be rotated, update connected applications through an agreed change process. Clear ownership and separate permissions make later troubleshooting and service renewal far more predictable.
