Migrate Accounts Between Eenos Servers
Use the Eenos Migration wizard to confirm source SSH identity, copy native packages, select accounts and review ownership, staging, IP and DNS options.
Open Transfer → Eenos Transfer → Eenos Migration. Review the source and destination requirements first.
Connection details
| Field | What to enter |
|---|---|
| Source hostname or IP address | Source Eenos server reachable from the destination. |
| SSH port | Source SSH port, from 1 to 65535; default 22. |
| SSH username | Use root; native execution requires this login and source root privileges. |
| Authentication | Choose SSH key or password. |
| Root SSH key | A managed destination root key without a passphrase, authorized on the source. |
| SSH password | Required when password authentication is selected. |
Choose Connect and discover packages. Compare the detected SHA256 host fingerprint with a trusted value supplied by the source administrator, then choose Accept and continue only for the intended server.
The source EAPI must return a supported, complete migration inventory. An older or incompatible source installation can authenticate successfully but fail discovery. If discovery reports invalid or unsupported inventory, check the source Eenos installation and migration support, then reconnect after the issue is resolved. Do not treat an empty response as proof that the server has no accounts.
Hosting packages
Inspect discovered package limits and select packages to copy unchanged. Native packages retain their source names; this wizard does not rename them or overwrite existing destination packages. Default is excluded from transferable packages. A package already present on the destination is skipped for copying; inspect its destination configuration if accounts will rely on it.
Choose Continue to accounts, or Skip packages when importing accounts without package copies. Account discovery is independent of package selection. Package-only migration is also possible by skipping accounts; at least one package or account must remain selected.
Hosting accounts
The table shows username, primary domain, package, source IP, disk usage and eligibility. Review domain and username conflicts before selecting accounts. Incomplete or inconsistent source inventory, unsafe home paths and destination reservations can block preparation.
- Select all eligible selects eligible accounts across all table pages.
- Clear selection removes the current account selection.
- Recheck conflicts refreshes account availability after changes.
- Edit migration options returns to the shared transfer controls.
- Change package selection returns to packages.
Selected resellers are restored first. A hosting account retains its source owner when that reseller is also selected; otherwise it is restored under root. Inspect Restore under in the final summary. Ownership can be changed later in WAP, but selecting a hosting account alone does not automatically import its reseller.
Migration options
| Field | Behavior and requirements |
|---|---|
| Staging directory | Existing absolute destination directory; default /home. Requires free disk space and inodes. |
| Destination shared IPv4 | Required address from configured destination shared IPv4 choices. |
| Destination shared IPv6 | Optional configured IPv6 mapping. Native restore falls back to the destination main shared IPv6 when no explicit mapping is supplied and that address is configured. |
| Enable Parallel Transfer | Allows concurrency when destination resources permit it. |
| Number of Transfer Threads | Concurrent transfers, within the resource-based maximum shown. |
| Number of Restore Threads | Concurrent restores, within its separately calculated maximum. |
| Transfer Session Timeout | Inactivity timeout in seconds, default 1800; continued progress keeps work running. |
| Point DNS records to the new server IP | Requests source DNS repointing after restoration; external DNS requires updates at its provider. |
Without parallel transfer, both thread counts become one. Use conservative concurrency for the destination workload and staging capacity. The staging path cannot be /, a protected system directory or a live account home; traversal, unsafe permissions and read-only storage are rejected. Review both available inodes and space, including estimated concurrently active data. Source backup preparation also consumes source storage.
For more detail on shared connection and option validation, see Import Connection and Migration Options. The native package and IPv6 behavior described above is specific to this workflow.
Final review and start
Choose Review transfer. Check the source, staging directory, available disk/inodes, estimated data, concurrency, inactivity timeout and DNS request. Inspect both Accounts and Packages, especially destination owners, addresses and unchanged package identities. Remove unwanted rows or go back to edit the selection.
Choose Start migration after review. The server validates the plan again, starts the shared migration controller and opens Transfer Progress. Follow job and account status and logs; a queued job is not a completed account restore. Expired drafts require reconnection, and Disconnect and clear draft does not undo work already started.
Completion checks and cautions
Native restore uses destination capabilities. If a database engine is unavailable on the destination, its data can be skipped with a warning. Check component results and warnings before declaring an account complete; arrange the required destination service or a separate data migration before cutover.
Do not treat a partial restore as complete
Check restored websites and application runtimes, home files and permissions, databases, mail, quotas, ownership and DNS. Certificate installation is scheduled separately and needs verification. Review cleanup warnings and retained staging data before removing anything manually.
The home directory is transferred separately from the metadata backup. Plan a maintenance window or application-specific handling for writes made while the migration runs; do not assume this is a single consistent snapshot of all live services. Keep the source available until your verification and recovery requirements are met.