Migration guide

Migrating from Plesk

Plesk deployments can vary by edition, extension set, and provider policy. A safe migration documents each subscription, domain, application, mailbox, database, certificate, and integration.

Discuss migration
1. Map subscriptions

Identify customers, subscriptions, service plans, domains, aliases, mail settings, databases, users, scheduled tasks, and extension dependencies.

2. Build Outlaw Panel targets

Create hosting accounts and sites that match the intended domain hierarchy. Validate PHP/Node runtime expectations and managed-root boundaries.

3. Move data safely

Migrate files, databases, mailboxes, DNS, and certificates with checksum or sample-content verification. Keep production traffic on the existing panel until validation completes.

4. Certify and cut over

Confirm web, mail, DNS, TLS, backups, and customer login before updating authoritative records.

Migration checklist

  • Subscriptions and service plans
  • Plesk extensions and app dependencies
  • DNS and mail routing
  • Database engines and users
  • PHP handlers and Node apps
  • SSL lifecycle
  • Customer communication plan

Important cautions

  • Edition-specific Plesk features may not map one-to-one.
  • Marketplace runtime installation is not part of Outlaw Panel Version 1.
  • Use rollback checkpoints before changing live DNS.

Plan before cutover

Validate web, mail, DNS, TLS, backup, and rollback evidence before moving production traffic.

Back to comparisonsRead documentation