Migrating accounts from another control panel
How to bring existing hosting accounts across from Enhance, cPanel, or DirectAdmin.
If you're moving your hosting business to JSOPanel, you don't need to rebuild every customer's website, email, and database by hand. JSOPanel can bring accounts across from Enhance, cPanel, or DirectAdmin, copying websites, email, databases, DNS settings, and cron jobs automatically.
Choosing where the account is coming from
Click Migration in the sidebar. There are three tabs, depending on what you have access to:
- From a live server: connect directly to the old server over SSH. This works for Enhance, cPanel, or DirectAdmin, you don't have to say which one it runs; JSOPanel asks when it connects. Enter the server's address, SSH port, login, and password to connect and list the accounts on it.
- From a cPanel backup: point JSOPanel at a cPanel backup file you already have.
- From a DirectAdmin backup: point JSOPanel at a DirectAdmin backup file you already have.
Nothing on the old server is changed when connecting live, JSOPanel only reads from it. Your password for the old server is held for half an hour so you aren't asked again for each account, then it's forgotten; it's never saved.
Steps
- Connect to the old server, or point at your backup file.
- Review the list of accounts found and select the ones you want to bring across.
- Read the plan JSOPanel shows for what would happen, then start the migration.
Larger accounts can take a while, especially with a lot of email or large databases. The migration runs in the background, so you can leave the page and check back later. If copying an account stops partway, pressing Fetch again picks up where it left off rather than starting over.
What gets migrated
A migrated account brings across its websites and files, mailboxes and their messages, databases, DNS records, and cron jobs. Anything that can't be automatically matched to a JSOPanel setting is listed so you can review it.
After migrating
A migrated account has no package assigned by default. Once you've confirmed it works correctly, assign it a package, or set sensible default limits for package-less accounts under Service Configuration, and manage it exactly like any other hosting account.