How to request a migration

Open a support ticket, required details, stages: initial backup → test restore → delta sync → cutover → QA.

Summary

Open a migration ticket in the Client Area and include the required details. We then execute a controlled 5-stage process: initial backup → test restore → delta sync → cutover → QA.

When to use

  • You’re ready to start the move and can share access securely.

  • You want SERVER1 to handle the heavy lifting.

Prerequisites

  • Active SERVER1 service (Web Hosting, WordPress Hosting, Reseller, Managed VPS, or Managed Server).

  • Working credentials to the current host:

    • cPanel/Plesk admin (preferred), or

    • SSH/SFTP + database access, or

    • Platform-specific export access.

  • Pre-Migration Checklist completed (backups, free space, TTL lowered, mailbox list compiled).

Step-by-step

  1. Open a ticket (Client Area → Support → Submit Ticket → Migration Request).

  2. Provide details

    • Source host type (cPanel/Plesk/custom), access URL, IP, port.

    • Admin/SSH/SFTP credentials; DB credentials if separate.

    • Domain(s) to migrate; which apps (WP, Woo, custom PHP, etc.).

    • Email migration scope (mailboxes to copy, sizes).

    • Preferred maintenance window and timezone.

  3. Initial backup & test restore

    • We copy files/DB to SERVER1 and restore to a staging path/subdomain in Plesk.

    • You’ll receive a preview URL to validate.

  4. Delta sync

    • We resync changes made on the source while you test (to reduce drift).

  5. Cutover

    • We agree the exact time, adjust DNS (or switch IP), issue SSL, and verify.

  6. Quality assurance

    • We test home/login/cart/checkout/forms/admin; you run business-critical checks.

  7. Sign-off & rollback window

    • We keep a quick rollback option for a short period after cutover.

Notes/FAQ

  • If you cannot share panel access, provide SSH/SFTP and DB dump.

  • We coordinate email migration (IMAP copy) when credentials are supplied.

  • Please freeze content updates near cutover or expect a short content freeze window.

Related

  • Migrations → SERVER1 Migration Policy

  • Migrations → Limitations

  • Getting Started → Pre-Migration Checklist

  • Domains → Troubleshooting (propagation, TTL)

  • Support → SLA; Support → Tiers of Support & Scope

PreviousMigrationNextSERVER1 Migration Policy

Last updated