Skip to main content

Operational guide · digital-agency · Global

Agency hosting ownership and handover checklist

Document client ownership, delegated access, billing, backups and offboarding for agency hosting. Separate a handover plan from a customer success claim.

This is an educational operational guide, not a customer testimonial or a report of measured customer results. Editorial review: .

Agency hosting creates two relationships: the supplier's service to the agency and the agency's obligations to each client. A successful handover depends on documented ownership and controlled access, not simply the number of sites in a reseller panel. This guide is an operating checklist, not a report that an agency hosted a particular number of clients.

Establish who owns each asset

Create an inventory for every client covering domains, DNS, hosting, application code, databases, media, mail, certificates and third-party accounts. Record the legal or contractual owner, operational administrator, renewal payer and recovery contact separately. They may not be the same person.

For domain names, review the relevant registrar and registry rules. ICANN's registrant rights and responsibilities provide context for covered generic top-level domains; do not assume every country-code registry follows the same process. Keep a client's registration and renewal status verifiable without depending on one developer's personal inbox.

Delegate access without sharing the master account

Use individual identities and the narrowest practical role for the task. Separate client administration from agency-wide supplier administration. A contractor working on one site should not automatically gain access to every client database or payment setting.

The OWASP authorization guidance explains least privilege, default denial and permission checks. Apply those principles to the actual panel and application; a role name is not proof that isolation works. Test the permitted and refused actions with controlled accounts before delegating access.

Protect recovery and emergency administration as carefully as routine access. Decide who can approve a privileged change, how the organization recovers a locked account and how access is removed when a staff member or contractor leaves.

Make service boundaries visible to the client

State what the client is buying: infrastructure, site maintenance, updates, mail administration, monitoring or some defined combination. Identify out-of-scope work and who responds outside normal hours. Avoid describing a supplier feature as an agency-managed service unless the agency actually operates it.

Explain renewal responsibility, cancellation handling and the process for an unpaid invoice without promising rights that the contract does not provide. Keep current supplier pricing and terms in the catalogue or agreement, not copied into a long-lived handover document.

Test the exit before it is urgent

Prepare an export and restoration procedure for the website and its required data. Identify service-specific components that cannot be transferred by copying files alone, such as DNS, mail, scheduled jobs or external integrations.

Use a separate environment to confirm that an authorized recipient can restore the agreed scope. Record required software, configuration locations and remaining manual steps without embedding secrets in the handover pack. A backup archive is useful only if the receiving party knows what it contains and can use it.

Complete a controlled offboarding

Agree the final synchronization window and which system can accept writes during the move. Confirm domain and DNS administration, billing contacts, application access and delivery of the approved data. Have the client or authorized recipient accept the result before closing the migration.

Then revoke temporary and former-operator access according to the agreement. Rotate credentials when sharing or exposure makes that necessary. Keep an appropriately protected record of approvals and work completed, not an unrestricted duplicate of every client's data.

Use an acceptance pack

The pack should identify the client and authorized recipient, asset inventory, responsibilities, recovery test, unresolved exceptions and sign-off. Update it when the operating arrangement changes rather than leaving the original onboarding assumptions in place indefinitely.

Compare current reseller services against this operating model. Use the backup verification guide for recovery planning, or request a scoped discussion about a handover whose ownership or access boundaries remain unclear.