Migration Policy

When migration assistance is offered with your order or plan, it is best-effort help to move eligible websites and email to iHoster24. Feasibility depends on access, technology stack, and plan limits.

1. Eligibility

Complimentary or included migrations apply only where advertised for your product/order, or where we confirm assistance in writing/ticket. Complex or multi-server projects may require a paid professional service or may be declined.

2. What we migrate

  • Standard website files and databases for common stacks (for example typical cPanel hosting accounts), where source access is available.
  • Email mailboxes when protocol access (IMAP) and credentials are provided and the volume is reasonable for the plan.
  • DNS cut-over guidance after content is in place.

3. What you must provide

  • Valid credentials or temporary access to the source host (FTP/SFTP, control panel, database, or SSH as applicable).
  • A list of domains, subdomains, and mailboxes in scope.
  • Confirmation of maintenance windows and who will update DNS at the registrar if we do not manage the domain.
  • Removal or documentation of custom firewall rules that would block migration traffic.

4. Process

Typical steps: ticket intake → access verification → staging copy to iHoster24 → customer preview → DNS/mail cut-over → short hypercare for access issues. We may pause or cancel if credentials fail, the source is unreachable, or malware/AUP issues are found.

5. Limits and exclusions

  • No guarantee of zero downtime, identical plugin behaviour, or compatibility of every theme/extension.
  • We do not rebuild broken applications, rewrite code, or migrate unsupported/obsolete stacks without agreement.
  • License keys, third-party SaaS, and external CDN/API configurations remain your responsibility.
  • Very large datasets, streaming media libraries, or multi-node clusters may be out of complimentary scope.

6. Downtime and DNS

DNS propagation and mail TTL settings can cause temporary dual-delivery or brief unavailability. Lower TTLs in advance when possible. We are not responsible for registrar lock delays or third-party DNS provider errors.

7. Acceptance

After we notify you that the migration copy is ready, please verify sites and mail promptly. Unless otherwise agreed, migration assistance for that order is considered complete after successful cut-over or after a reasonable verification window stated in the ticket.

8. After migration

Keep your own backup of the source until you confirm everything works. Update CMS credentials, payment callbacks, and cron jobs. Ongoing support follows the Support Policy.

9. Updates

We may update this policy as products change. See the document information block for version and dates.