Skip to Content
Browse documentation

Import Plesk Subscriptions

Import Plesk service plans and subscriptions into Eenos with explicit ownership policies, reseller/customer review and destination conflict checks.

Open Transfer → Import Accounts → Plesk.

Source requirements

Use the source SSH username root. Discovery identifies the Plesk installation using its version command, checks source rsync compatibility and builds a preview of subscriptions, service plans and owner identities. Prepare managed SSH keys, trusted fingerprint confirmation and destination storage/IPs as described in Import Accounts.

Plans and subscriptions

Connect and confirm the source identity, then review service plans for package creation. Each selected plan needs a unique destination package name using letters, digits, underscores or hyphens, up to 128 characters. Names must not already exist on the destination. You can skip plans and continue to subscriptions.

Plesk subscriptions are the hosting migration units. Inspect the subscription username, primary domain, domains, source owner, destination owner and eligibility. Resolve source-review or destination-conflict blockers before proceeding.

Account ownership

Choose the policy before final review and inspect the resulting preview.

PolicyDestination behavior
Preserve ownershipPrepares required reseller and customer sub-reseller identities before subscriptions. Admin-owned customers migrate under root.
Restore under rootSelected subscriptions and imported packages belong to root; reseller and customer accounts are not created.

In preserve mode, review the Reseller and customer identities table: username, owner, account allowance, disk quota and bandwidth in MiB, placeholder domain and proposed action. Eenos requires a primary domain for every account, so owner identities without a hosting domain receive a placeholder domain.

Existing owner accounts can be reused only when the system verifies their source identity and allowances. A matching destination username alone does not authorize reuse. Owner identity/resource blockers must be resolved before starting. Selected plans can also require owner preparation, including in a package-only migration.

Review ownership deliberately

Restoring under root changes the intended management hierarchy. Confirm who should manage the resulting accounts and packages before starting, and check reseller/customer access after restoration.

Review and migration

Choose subscription rows and configure staging, destination IPv4/optional IPv6, concurrency, inactivity timeout and DNS behavior. See the full option reference.

Inspect both the selected subscriptions and service-plan mappings in the final summary, along with owner restore/reuse actions and storage estimates. Start migration only after this review. Follow Transfer Progress and verify restored domains, files, databases, mail, account limits and ownership; a successful discovery preview does not establish application compatibility.