Import from Other Panels¶
enconf can automatically import server data from Plesk via SSH. cPanel/WHM and Enhance import are in development.
More Information
Visit enconf.com for a complete overview of all features, pricing and comparisons with other hosting panels.
Overview¶
The import wizard migrates the following data:
| Data Type | Description |
|---|---|
| Customers | Customer data and credentials |
| Resellers | Reseller accounts with customer assignments |
| Sites | Websites with files and configuration |
| Redirect domains | A Plesk "redirect" (hosting type) is imported as a redirect domain — without a webspace |
| Domain Aliases | Automatic detection via DocRoot matching |
| WordPress | Automatic detection + registration in WordPress Toolkit |
| Mailboxes | Email mailboxes incl. password hashes + Maildir via rsync |
| Forwarders | Email forwarders |
| Databases | MariaDB/MySQL databases via SSH pipe (no RAM limit) |
| DNS Zones | DNS records |
| FTP Accounts | FTP credentials |
| Cron Jobs | Scheduled tasks |
Plesk Import (SSH)¶
The Plesk import connects directly to the source server via SSH and exports all data. No API key required — root access is sufficient.
Requirements¶
- SSH access to the Plesk server (root or sudo)
- Network connectivity between servers
Starting the Import¶
- Navigate to Import
- Click New Import
- Select Plesk as the source type
- Fill in the connection details:
| Field | Required | Description |
|---|---|---|
| Host | Yes | IP address or hostname of the Plesk server |
| SSH Port | Yes | SSH port (default: 22) |
| SSH User | Yes | SSH username (e.g. root) |
| SSH Password | Yes | SSH password or key |
| Default Package | Yes | Hosting package for imported customers |
| Target Server | Yes | Server for the new accounts |
| Notifications | No | Notify customers about migration via email |
- Click Connect and Scan
Scan Results¶
After the scan, a summary is displayed:
- Number of found customers and resellers
- Number of sites, mailboxes, databases
- Detected WordPress installations
- Detected domain aliases
- List of all objects to migrate
Running the Migration¶
- Review the found data
- Optionally deselect individual customers or objects
- Click Start Migration
What enconf Does Automatically¶
| Feature | Description |
|---|---|
| SSH Migration | Direct connection via root — no API key or export needed |
| DB Dump via SSH Pipe | Databases are streamed directly over SSH — no RAM limit, even for large databases |
| WordPress Detection | WordPress installations are automatically detected and registered in the WordPress Toolkit |
| Domain Alias Detection | Aliases are automatically matched via DocRoot matching |
| Reseller Import | Reseller accounts are fully imported including customer assignments |
| Mailbox + Password Hash | Email passwords are transferred as hashes — customers don't need to change their password |
| Maildir rsync | Email messages are fully transferred via rsync |
| Email Forwarders | All forwarders are automatically imported |
| Rollback on Error | If an error occurs, the import is cleanly rolled back — no half-finished state |
After Migration¶
- DNS must be pointed to the new server
- SSL certificates are automatically requested via Let's Encrypt on first access
- WordPress URLs are automatically updated via search-replace
- Customers can log in immediately with their existing credentials
No Password Reset Needed
Thanks to password hash transfer, customers do not need to change their password after migration.
Per-domain package and IP¶
Some customers have several domains on different packages or different IP addresses. enconf supports this directly during import:
- Each domain can be assigned its own package and its own IP in the import wizard (per-domain dropdown).
- Domains on different packages land in separate webspaces (one subscription per package) — each domain in the right one.
- Auto-detection: enconf reads each domain's service plan and IP from the Plesk database and pre-selects the matching panel package / IP. You can override the mapping before migrating.
Large accounts
Even customers with many domains (e.g. 50+) and mixed packages/IPs are split correctly — every domain lands in the right webspace with the right IP.
Redirect domains¶
A Plesk domain of hosting type redirect has no webspace — it only forwards to a target URL. enconf detects this from the Plesk hosting type and imports it as a redirect domain (status redirect, 301/302) with an Nginx redirect vhost — without a Linux user, PHP pool or files.
Re-syncing individual items¶
Already-migrated items can be re-synced individually (e.g. to pull files, mailboxes or databases again after a change on the source server):
- Website (with webspace) → files are pulled again via rsync
- Mailbox → the Maildir is transferred again
- Database → the database is re-imported
Redirects have nothing to sync
A redirect domain has no webspace. "Re-sync" therefore only shows a note that there are no files to transfer — this is not an error.
Re-migrate (re-analyzes first)¶
A re-sync only pulls files/mailboxes/databases again — the classification made at import time (website / alias / redirect) stays frozen. If a domain was imported with a stale classification (e.g. mistaken for an alias), use "Re-migrate" on that domain instead:
- The source is re-analyzed (with the current classifier and path detection).
- The stored plan is refreshed and the item plus its nested resources are reset.
- The domain is re-created cleanly — domain, DNS, website, database and WordPress are all rebuilt correctly.
This fixes a single domain without deleting and recreating the whole import. It's idempotent (existing records are reused, no duplicates). Currently for Plesk SSH imports.
Import log¶
Every import session has an Import log (a button at the top of the session and in the progress bar). It records what the importer detected and did, and can be copied or downloaded as .txt:
- Analysis summary — how many customers and websites were detected (zero detected websites is flagged prominently)
- Per-domain classification — website / alias of … / redirect, with the resolved source path
- Per-run result — websites/databases/mailboxes created and any warnings (e.g. "target directory empty" or "WordPress detected")
So an import that appears to "do nothing" is diagnosable without server access — and you can send the log straight to support if you have a question.
cPanel Import¶
In Development
cPanel/WHM import will be available in a future version.
Enhance Import¶
In Development
Enhance import will be available in a future version.