Migrating From Plesk to cPanel Print

  • 0

Server Account Migration Between Control Panels

This article explains the process of migrating a hosting account between different server control panel environments. Please note this article assumes that you already have an account running on the source server you are migrating from, a destination server that you are migrating to, and the necessary access credentials.

Log into your destination server as the migration process will be initiated from this server. Once you are logged in, you will need to navigate to the migration tool, which is typically located under administrative sections such as Main >> Account Transfers >> Copy an account from another server.

You will need to provide the following information for this migration:

  • Hostname or IP address of the source server

  • SSH port number (typically 22, but may vary)

  • Exact account name of the account you are migrating

  • Administrative username and password with appropriate privileges

Unlike some migration scenarios between similar systems, you must have the exact account name from the source server, otherwise the migration will not start properly. The migration typically uses SSH for secure transfer, however you may also have the option to choose FTP if preferred or if SSH is not available.

Once you have provided all of the required information, click "Transfer" or "Start Migration" to begin the process.

The control panel will then initiate the migration, providing detailed progress information on the screen. The process typically involves:

  1. Establishing connection to the source server

  2. Verifying account information and permissions

  3. Transferring website files and databases

  4. Migrating email accounts and configurations

  5. Recreating DNS zones and settings

  6. Verifying the integrity of transferred data

Once the migration has completed successfully, the system will display a confirmation message such as "Account Copy Process Completed" or similar completion notification.

Important Considerations:

  1. Pre-Migration Preparation:

    • Create full backups on both source and destination servers

    • Verify disk space availability on the destination server

    • Check compatibility of PHP versions, database versions, and other software

    • Document any custom configurations or special requirements

  2. During Migration:

    • The source website should be placed in maintenance mode

    • Avoid making changes to the source account during migration

    • Monitor the migration progress for any errors or warnings

    • Be prepared for the migration time to vary based on account size and server performance

  3. Post-Migration Verification:

    • Test website functionality on the new server before DNS changes

    • Verify all files transferred completely and correctly

    • Check database connections and data integrity

    • Test email sending and receiving capabilities

    • Confirm SSL certificates are properly installed and working

    • Update any hard-coded paths or URLs that may reference the old server

  4. DNS Update and Propagation:

    • Update nameservers or DNS records to point to the new server

    • Allow time for DNS propagation (typically 24-48 hours)

    • Monitor for any issues during the transition period

    • Keep the source account active until you confirm everything works on the destination

Alternative Migration Approaches:

If the automated migration tool encounters issues or is unavailable, consider these alternatives:

  1. Manual Migration: Create backups on the source server, transfer files via FTP/SFTP, export/import databases, and manually reconfigure settings

  2. Third-Party Migration Tools: Use specialized migration software designed for cross-platform transfers

  3. Professional Migration Services: Consider hiring migration experts for complex or critical migrations

Troubleshooting Common Issues:

  • Connection failures: Verify network connectivity, firewall settings, and credentials

  • Permission errors: Check user permissions on both source and destination servers

  • Incomplete transfers: Monitor disk space and network stability during migration

  • Database issues: Ensure compatible database versions and character sets

Remember that successful migration requires careful planning, execution, and verification to ensure minimal downtime and data integrity throughout the process.

 

Was this answer helpful?

« Back