Website Migration Agreement Template

Website Migration Agreement Template

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

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

Website/Project Name: [Project Name]
Current Site URL(s): [URL(s)]
Target Site URL(s) (If Changing): [URL(s)]
Migration Type: ☐ Hosting move ☐ Domain transfer ☐ CMS/platform migration ☐ Infrastructure change ☐ Other: [__]

1. Scope of Migration

1.1 Provider will perform the migration services described in this Agreement (the “Services”), which may include (select and customize):

• Environment setup (hosting/server/CMS)

• Database export/import (if applicable)

• Content migration: ☐ pages ☐ posts ☐ media ☐ products ☐ users ☐ other: [__]

• Configuration updates (themes/plugins/settings)

• DNS updates and cutover

• SSL/TLS setup (HTTPS)

• Email/transactional email configuration (optional): ☐ included ☐ excluded

• Analytics/tag manager setup (optional): ☐ included ☐ excluded

• Other: [List]

1.2 Out of Scope: Unless added by written change, the following are excluded:

• redesign or new feature development beyond migration needs

• rewriting content or adding new content beyond agreed migration

• ongoing SEO campaigns (except redirects if included)

• third-party vendor work outside Provider’s control (unless explicitly managed)

• data recovery from corrupted systems not caused by Provider

2. Deliverables

2.1 Deliverables may include:

• Migrated website functioning in the target environment

• Basic configuration checklist completed (SSL, caching, backups if included)

• Redirect map (if included) and redirect implementation

• Migration report (optional): [what was moved + known issues]

3. Timeline and Milestones

3.1 Target Start Date: [Date]
3.2 Target Cutover/Launch Date: [Date] (estimate unless stated as fixed)
3.3 Milestones (Optional):

• Access/credentials received by: [Date]

• Staging migration complete by: [Date]

• UAT/testing window: [Dates]

• Final content freeze: [Date/Time]

• DNS cutover window: [Date/Time]

4. Access, Credentials, and Third-Party Services

4.1 Client will provide timely access to systems needed for the Services, including: hosting, DNS registrar, CMS admin, repositories, analytics, CDN, and third-party plugins/services.
4.2 Third-Party Services List (Optional):

• DNS/Registrar: [Provider]

• Hosting: [Provider]

• Email/SMTP: [Provider]

• CDN/WAF: [Provider]

• Payments (if any): [Provider]

• Other: [List]

4.3 Unless stated otherwise, Client is responsible for third-party fees and maintaining active accounts.

5. Data, Content, and Mapping Rules

5.1 What Data Will Be Migrated: [Describe: content types, tables, products, users].
5.2 Mapping/Structure: Provider will migrate content according to: ☐ existing structure ☐ new mapping (attach as Exhibit A) ☐ other: [__].
5.3 Excluded Data (Optional): [Old test users, logs, obsolete files, etc.].
5.4 Client will confirm content priorities and provide any required exports, spreadsheets, or source files.

6. Backups and Safety

6.1 Before cutover, Provider will: ☐ create a full backup ☐ request Client to create a full backup ☐ both.
6.2 Backup Location: [Where stored] and Retention (Optional): [__] days.
6.3 Client understands backups may not include third-party SaaS data unless explicitly included.

7. SEO, URLs, and Redirects (Optional)

7.1 Redirects are: ☐ included ☐ excluded.
7.2 If included, Provider will implement 301 redirects based on: ☐ Client-provided redirect list ☐ Provider-generated draft approved by Client ☐ other: [__].
7.3 Provider does not guarantee rankings or traffic outcomes; results depend on many factors outside Provider control.

8. Testing, Acceptance, and Go/No-Go

8.1 Provider will perform basic functional testing (navigation, forms, critical pages).
8.2 Client will perform user acceptance testing (UAT) during: [Dates] and report issues in writing.
8.3 Acceptance Criteria (Customize):

• Site loads and core pages render correctly

• Critical functions work: [checkout/forms/login/booking/etc.]

• No critical errors in logs (reasonable standard)

• Other: [Criteria]

8.4 If Client does not report material issues within [__] business days after cutover, the migration will be deemed accepted (optional).

9. Cutover, Downtime, and Rollback

9.1 Cutover will occur during a planned window: [Date/Time/Time zone].
9.2 Expected downtime (if any): [Estimate] (best effort; not a guarantee).
9.3 Content Freeze: Client agrees to stop making changes to the source site during: [Window], unless otherwise agreed.
9.4 Rollback Plan (Optional): If a critical failure occurs, Parties may roll back to the prior environment. Rollback trigger: [Define] and rollback method: [DNS revert/restore backup/etc.].

10. Fees and Payment

10.1 Fee Structure: ☐ fixed fee $[Amount] ☐ time & materials at $[Rate]/hour ☐ milestone-based: [__].
10.2 Payment Schedule: [Deposit + milestones or invoice terms].
10.3 Out-of-scope work requires written approval and may be billed separately.

11. Post-Migration Support

11.1 Included support period after cutover: [__] days/weeks.
11.2 Included support covers: bug fixes related to migration and minor adjustments.
11.3 Ongoing maintenance beyond the support period is: ☐ included under separate retainer ☐ available as a new agreement ☐ not included.

12. Client Responsibilities

12.1 Client will provide timely feedback and approvals and designate a primary decision-maker.
12.2 Client is responsible for content accuracy, legal compliance of content, and business decisions about what to publish, remove, or change.

13. Warranties and Disclaimers

13.1 Provider will perform Services in a professional and workmanlike manner.
13.2 Except as stated, Services are provided “as is,” and Provider does not guarantee uninterrupted uptime, specific performance metrics, or SEO outcomes.

14. Limitation of Liability (Optional)

14.1 Consequential damages: ☐ excluded ☐ not excluded.
14.2 Liability cap: ☐ none ☐ $[Amount] ☐ fees paid under this Agreement.

15. Governing Law

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

Signatures

Client: [Client Legal Name]
Name/Title: [Authorized Signer]
Date: [Date]
Signature: ___________________________

Service Provider: [Provider Legal Name]
Name/Title: [Authorized Signer]
Date: [Date]
Signature: ___________________________