Skip to Content
Browse documentation

Prepare for a Hosting Migration

Inventory accounts, check destination services and capacity, plan ownership and DNS, and prepare a recoverable migration to Eenos.

Prepare both servers before discovery, conversion or restore. Start with one account that represents the applications, databases and mail storage you expect to move.

Inventory and compatibility

Record account names, domains, aliases, reseller ownership, packages, disk usage, databases, mailboxes, scheduled jobs and external dependencies. Identify custom web-server configuration, application runtimes, certificates and integrations that need separate work.

Check that the destination has the required database engines and runtime versions. Missing engines can cause components to be skipped; a successful account restore does not prove application compatibility. Check mailbox format and provider-specific exclusions before selecting a converter.

The current standalone converters produce DNSv2 backups intended for Eenos 5.0.1 or later. Confirm the compatibility of the actual converter release and destination before using its output. Existing older backups may use a different format.

Account names, packages and owners

Resolve destination username, domain and package conflicts before starting. Record which reseller should own each account. For supported WAP workflows, selecting the reseller affects ownership of selected hosting accounts; Plesk has an explicit ownership policy that needs separate review.

Converted package names may differ from their source names. For example, the current cPanel converter maps dots to Dot and whitespace groups to Space; inspect the resulting names and collisions before using them. Keep a source-to-destination mapping.

Storage and access

Allow space and inodes for source backups, temporary extraction, converted archives, transfer staging and restored accounts. These can coexist during the operation. Use separate existing work and output directories for each converter run, with restricted access and sufficient capacity.

WAP imports require a root administrator session over HTTPS, appropriate source SSH access and a managed destination root SSH key pair, including when password authentication is selected. Verify the source host fingerprint through a trusted channel. See connection and options.

For standalone conversion, live-account operations need access to the corresponding source panel and its account data. Archive conversion needs a trusted supported backup and the required extraction tools. Follow your operating system's supported Python and dependency requirements.

Backups and write coordination

Keep an independent backup before migration. Test that you can inspect and recover it. Do not use the only copy of a backup as a converter's working input.

Plan a maintenance window or application-specific final synchronization. Files, databases and mail copied at different times are not automatically a single consistent snapshot. Define when source writes stop, how late mail is handled and which server is authoritative after cutover.

DNS and recovery plan

Identify the authoritative DNS provider and the records that route web and mail traffic. Plan TTL changes early enough for previously cached values to expire. Record the old values, destination IPv4/IPv6 addresses and who will make the change.

Source-DNS repointing in a WAP wizard does not update an unrelated external DNS service. Check AAAA, MX, SPF, DKIM and DMARC as well as A records. Agree on rollback criteria and a way to reconcile destination writes before returning traffic to the source.

Continue with panel migration workflows or command-line tools.