Contract guide · checked 17 July 2026

Hosting migration policies compared

Free migration may exclude email, DNS, complex applications, final synchronization or rollback.

4 primary sources5 contract checksNo score from marketing copyRecheck before purchase

Plain language

Terms that change the outcome

Automated migration

A plugin or transfer system with application and size boundaries.

Managed migration

Provider staff move an eligible site within a defined scope.

Final synchronization

Copying data created after the initial migration before DNS cutover.

Buyer checklist

What the contract must answer

  1. 01Number and size of sites
  2. 02Files and database scope
  3. 03Email and DNS inclusion
  4. 04Final sync for changing data
  5. 05Rollback ownership and support

Common traps

What the headline leaves out

Evidence worksheet

Capture the policy before checkout

Save a dated copy or screenshot because the provider can revise public terms.

Record

Commercial terms

Product
Exact plan and billing term
Trigger
Event that creates eligibility
Deadline
Time to request or claim
Remedy
Cash, credit, extension or restore
Record

Operational terms

Exclusions
Products, events and customer actions omitted
Procedure
Required cancellation, ticket or evidence
Data effect
What can be overwritten or deleted
Escalation
Support and appeal path

Primary evidence

Read the current provider terms

Terms change. The linked provider document governs the purchase.

Policy questions

How to use this comparison

Does a longer guarantee prove better service?

No. It defines a contractual remedy. Quality requires observed evidence and the remedy still has exclusions.

Can support chat override published terms?

Ask for written confirmation, but assume the governing agreement controls unless the provider formally amends the order.

When should the policy be captured?

Immediately before payment, again before the deadline and whenever the product renews or changes.