Website Handover Agreement Template

This Website Handover Agreement (the “Agreement”) is entered into as of [Effective Date] by and between:

Client/Owner: [Client Legal Name], address: [Address] (“Client”)

Provider (Outgoing): [Provider Legal Name], address: [Address] (“Provider”)

Website Name: [Project Name]

Production URL: [URL]

Staging/Dev URL(s) (Optional): [URL(s)]

1. Purpose

1.1 The purpose of this Agreement is to document the handover of the website and related materials from Provider to Client (or Client’s incoming vendor) and to confirm completion and access transfer.

2. Handover Date and Scope

2.1 Handover Date: [Date].

2.2 This handover covers: ☐ production site ☐ staging/dev environments ☐ code repositories ☐ design files ☐ accounts and credentials ☐ documentation.

3. Deliverables Provided

3.1 Provider will deliver (select and complete):

• Website source code (as applicable): ☐ repository transfer ☐ ZIP archive ☐ other: [__]

• Deployment/config instructions (if applicable): [Docs/location]

• Database export (if applicable): ☐ included ☐ excluded (details): [__]

• Media/assets library export (if applicable): ☐ included ☐ excluded

• Admin access credentials handoff (handled securely): ☐ yes ☐ no

• Theme/templates/plugins (if applicable): [List]

• Design/source files (optional): ☐ Figma ☐ Adobe ☐ Sketch ☐ other: [__]

• Content files (if applicable): [Exports]

• License keys (only if transferable): [List]

• Documentation/Runbook (optional): [Links/files]

• Backup package (optional): ☐ provided ☐ not provided (details): [__]

Website source code (as applicable): ☐ repository transfer ☐ ZIP archive ☐ other: [__]

Deployment/config instructions (if applicable): [Docs/location]

Database export (if applicable): ☐ included ☐ excluded (details): [__]

Media/assets library export (if applicable): ☐ included ☐ excluded

Admin access credentials handoff (handled securely): ☐ yes ☐ no

Theme/templates/plugins (if applicable): [List]

Design/source files (optional): ☐ Figma ☐ Adobe ☐ Sketch ☐ other: [__]

Content files (if applicable): [Exports]

License keys (only if transferable): [List]

Documentation/Runbook (optional): [Links/files]

Backup package (optional): ☐ provided ☐ not provided (details): [__]

3.2 Deliverables location/method: ☐ shared drive ☐ secure link ☐ repository ☐ other: [__].

4. Accounts and Access Transfer

4.1 Provider will transfer (or provide access to) the following accounts, as applicable:

• Hosting account: [Provider] — ownership transfer: ☐ yes ☐ no (details)

• Domain registrar/DNS: [Provider] — admin access: ☐ yes ☐ no

• CDN/WAF: [Provider] — admin access: ☐ yes ☐ no

• Email/SMTP: [Provider] — admin access: ☐ yes ☐ no

• Analytics/Tag Manager: [Provider] — admin access: ☐ yes ☐ no

• Payment processor (if any): [Provider] — admin access: ☐ yes ☐ no

• Other: [List]

Hosting account: [Provider] — ownership transfer: ☐ yes ☐ no (details)

Domain registrar/DNS: [Provider] — admin access: ☐ yes ☐ no

CDN/WAF: [Provider] — admin access: ☐ yes ☐ no

Email/SMTP: [Provider] — admin access: ☐ yes ☐ no

Analytics/Tag Manager: [Provider] — admin access: ☐ yes ☐ no

Payment processor (if any): [Provider] — admin access: ☐ yes ☐ no

Other: [List]

4.2 If an account cannot be transferred (vendor limitation), Provider will provide the highest available admin access and confirm the current account holder and credentials handover.

5. Security: Password Changes and Access Revocation

5.1 After handover, Client will promptly change passwords and enable 2FA where available.

5.2 Provider will remove/revoke its access from Client systems by [Date], except for limited access during a transition period (if any) described in Section 6.

5.3 Provider will not retain Client credentials after revocation, except as required by law or with Client’s written consent.

6. Transition Support (Optional)

6.1 Transition support is: ☐ included ☐ not included.

6.2 If included, support period: [**] days/weeks after handover.

6.3 Included support scope: [Answering questions, assisting with access, minor fixes].

6.4 Support rate (if not included): $[Rate]/hour (or per retainer): [**].

7. IP Ownership and Licenses (Optional)

7.1 IP ownership follows: ☐ the master agreement dated [Date] ☐ statement of work dated [Date] ☐ other: [__].

7.2 Third-party components remain subject to their licenses. Provider does not transfer non-transferable licenses or paid accounts unless explicitly stated.

8. Warranties and Disclaimers

8.1 Provider represents it has delivered the items listed in Section 3 to the best of its knowledge.

8.2 Except as stated, the website and deliverables are provided “as is.” Provider does not guarantee future performance, uptime, or compatibility with third-party updates.

9. Acceptance and Final Sign-Off

9.1 Client will review deliverables within [__] business days of the Handover Date.

9.2 If Client identifies missing items, Client will notify Provider in writing. Provider will use reasonable efforts to address the items within the agreed scope.

9.3 If no issues are reported within the review window, the handover will be deemed accepted (optional).

10. Fees and Final Payment (Optional)

10.1 Final invoice amount (if any): $[Amount], due [Date].

10.2 Payment of the final invoice is: ☐ a condition of full handover ☐ not a condition (handover occurs regardless).

11. Confidentiality (Optional)

11.1 Each party will keep non-public information confidential and use it only for handover and transition purposes.

12. Governing Law

12.1 This Agreement is governed by the laws of [State/Country].

Signatures

Client/Owner: [Client Legal Name]

Name/Title: [Authorized Signer]

Date: [Date]

Signature: ___________________________

Provider (Outgoing): [Provider Legal Name]

Name/Title: [Authorized Signer]

Date: [Date]

Signature: ___________________________