Knowledgebase

Handing a Project Over to a Client Print

  • developersgitdeployment, developers, domain, email, backup, restore, security, password, woocommerce
  • 0

Leaving a site someone else can maintain.

WHAT TO PROVIDE

Credentials for everything, transferred securely, ideally through a password manager A list of what was installed and why The repository, if code was written Documentation of anything non-standard Backup arrangements and how to restore

A note of recurring costs: licences, services, subscriptions

DOMAINS

The domain should be registered in the client's name, not yours. If it is in yours, transfer it.

A client discovering they do not own their own domain is the most damaging dispute in this line of work.

ACCESS

Remove your own administrative accounts, or agree that they remain for ongoing maintenance.

Rotate any shared credential.

WHAT TO EXPLAIN

How to update the site What needs updating and how often What not to change Who to contact for what

THE THING THAT CAUSES TROUBLE

Third-party services registered to your email address on the client's behalf. Transfer them or the client cannot access their own accounts.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot