Scody Cloud
Migration

Move in without downtime surprises

We build your new environment in parallel with your existing one, verify it, then cut over on a schedule you control — with a rollback path if anything looks wrong.

Scope

What we move

Migration covers the whole stack behind a site or service, not just the files.

Websites and applications

Static sites, WordPress, and custom applications — files, configuration and runtime dependencies.

Databases

MySQL/MariaDB and PostgreSQL databases, migrated with schema and data intact and verified against the source before cutover.

Mail

Mailboxes, folders and existing mail routing, moved so inbox continuity is preserved through the switch.

DNS

Zone records recreated and verified on our nameservers before any cutover, so propagation is a planned step, not a surprise.

TLS certificates

Existing certificates carried over where valid, or reissued automatically once DNS points here.

Method

Parallel build, then cutover

The source environment stays live and untouched until the new one is verified — cutover is a deliberate final step, not the start of the process.

  1. 01We provision the new environment alongside your existing one — nothing is turned off yet.
  2. 02Data is copied and synced into the new environment while the source keeps running.
  3. 03You (and we) verify the new environment against the source: pages render, logins work, mail flows, queries return the same results.
  4. 04DNS and mail routing are cut over at a time you choose, once verification passes.
  5. 05The old environment is kept available for a rollback window in case anything needs to be reverted.
Rollback

If something doesn't look right

The previous environment is kept intact and reachable for an agreed rollback window after cutover. If an issue surfaces post-cutover that can't be fixed quickly in place, DNS and mail routing can be pointed back to the source while we resolve it — nothing is decommissioned until you confirm the migration is stable.

What we need from you

To plan the migration

  • Access credentials or temporary access to the source environment (control panel, SSH, or database credentials).
  • A list of domains, mailboxes and any custom services that need to move.
  • A preferred cutover window, especially if the site or mail system is business-critical.
  • Sign-off after verification, before we flip DNS and mail routing.
Cost

Assisted migration is part of onboarding

We don't charge a separate migration fee for standard moves onto ScodyX Cloud — it's treated as part of getting your account set up correctly, not a line-item upsell.

Get started

Tell us what you're moving

Share what you're running today and where, and we'll scope the move.

We use your details to reply to this enquiry. See our privacy policy.