Import Connection and Migration Options
Understand SSH identity confirmation, package mappings, account conflicts, staging, concurrency, destination IPs and DNS options in Eenos import wizards.
These controls apply to the Import Accounts provider wizards. Provider guides explain differences in discovery and ownership.
Connection details
| Field | Purpose and requirements |
|---|---|
| Source hostname or IP address | The source server reachable from the destination. |
| SSH port | Integer from 1 to 65535; default 22. |
| Username | Source SSH login; default root. Provider privilege checks still apply. |
| Authentication method | SSH key or password. |
| SSH key | Select a managed root key, without a passphrase, authorized on the source. |
| Password | Required for password authentication. Enter the source login password. |
Choose Connect and discover packages. The wizard first detects the source SSH host key and opens Confirm source server identity. Compare the SHA256 fingerprint against a trusted source before choosing Accept and continue. Detection alone does not prove that you reached the intended server. A changed host or port requires identity confirmation for that endpoint.
Connection drafts are session-bound and expire. If a draft expires, reconnect and rediscover. If the wizard reports an outdated revision, reload the current state before continuing. Do not share credentials, private keys or unredacted diagnostic output.
Packages and hosting accounts
Select source packages and enter destination package names. Existing destination packages cannot be overwritten through package creation; change the destination name or leave the package unselected. Check converted limits rather than assuming every source feature has an identical Eenos equivalent.
You can skip package import and continue to hosting account discovery. Account discovery is not restricted to the packages you selected. A package-only migration is also possible: the final selection must contain at least one package or account.
Choose eligible hosting accounts. Use Recheck conflicts after destination changes. Conflicting usernames, domains, active reservations or incomplete inventory need resolution before review; do not bypass the conflict checks. Select all eligible can select across table pages, so inspect the complete selection.
Migration options
| Field | Behavior |
|---|---|
| Staging directory | Existing absolute destination path; default /home. Requires usable free space and inodes. |
| Destination IPv4 | Required configured destination shared IPv4 address. |
| Destination IPv6 | Optional configured shared IPv6 address, or no IPv6 mapping. |
| Parallel transfer | Enables concurrent account processing when destination resources allow it. |
| Transfer threads | Transfer concurrency; use the maximum currently shown by the wizard. |
| Restore threads | Restore concurrency, with its own resource-based maximum. |
| Session inactivity timeout | Seconds without progress; default 1800. This is not a total migration duration limit. |
| Point DNS records to the new server IP | Requests source DNS repointing after restoration. External DNS must be updated with its provider. |
Without parallel transfer, both thread counts become one. CPU and memory availability determine the permitted concurrency; increasing counts can increase simultaneous staging requirements.
The staging path cannot be /, a protected system location or an existing account's live home directory. Invalid traversal, unsafe permissions and read-only storage are rejected. Review free disk space, inodes and estimated concurrently active data. Unknown estimates and accepted capacity checks are not guarantees that a long-running migration cannot fill storage.
DNS affects live traffic
Request repointing only when it matches your cutover plan. Verify the restored sites, mail and databases, and confirm authoritative DNS and external records before treating the migration as complete.
Final review and start
Review the source, selected accounts and packages, destination owners and IPs, staging capacity, concurrency, inactivity timeout and DNS request. Remove unwanted rows or return to edit the selection; keep at least one package or account.
Choose Start Migration only after review. The server checks the summary again before queuing the job and redirects to Transfer Progress. Follow its status and per-account logs to distinguish queued, running, failed and completed work. Resetting or changing a preparation draft does not undo a migration already started.
After completion, check account ownership and limits, website behavior, database access, mail and DNS. Preserve the source until your verification and recovery requirements are satisfied.