CPanel to Plesk Migration Guide
Preparation steps for cPanel to Plesk migrationFailing your cPanel to Plesk migration can lose you a lot of time. So ensure your Plesk migration process is seamless with these necessary preparation steps. And make sure you prepare both servers for the process. These are the essential steps that you need to follow to prepare the migration in a proper way.
- Make sure that you have enough disk space on both cPanel and Plesk servers. The space available within the source needs to be at least the same as the amount of data transferred. And the destination should have at least 5 GBs more than that.
- Use you migration manager to make sure that the versions of Plesk and cPanel you have are compatible for the transfer.
- Install the Plesk transfer and migration manager on the destination.
- In order to make sure there are no IP issues, add one or more shared IP addresses. Meanwhile, follow up with the exact number of dedicated IP addresses within both servers.
- If you have mailing lists in the source, install the Mailman mailing list manager in the destination server. And that way, you can handle them properly.
- To connect the destination server to the source server, allow the IP of the Plesk server within the cPanel firewall. Also, configure the source server to allow SSH connections.
- Make sure that SELinux is disabled on your Plesk server while the process is ongoing.
How to execute cPanel to Plesk migrationMigrations need different time frames, depending on the size of the data and your network speed. But do schedule the execution for quiet hours so that the transfer can go faster. Configure your “Transfer and Migration Manager” with Plesk’s interface. Then change the source server details including password, IP address, upload path, data that needs to be transferred, and add some custom rules just in case some conflicts occur while the migration takes place. One of the important things you need to do is IP address mapping. So remember to map all the dedicated and shared IPs within the source server to all of the corresponding IPs which are in the destination server. When the process is finished, make sure to look at the report to ensure that everything was transferred correctly.
How to overcome Migration Agent downsidesAlthough you can use the migration agent for a more automatized migration, you may run into some bumps. 1. Your FTP account passwords don’t get migrated and you generate new ones. Your solution is to track the passwords and update your users. 2. You will not manage to migrate DNS zones. So you have to edit your domain DNS records post-migration to configure them properly. 3. You won’t transfer data such as SSL certificates, PHP extensions, Apache modules, Domain keys and IP blacklists. So you’ll have to configure them manually in your destination server. 4. Often, the migration agent splits user accounts with multiple databases that are under one domain into several user accounts. So, you need to find the database dump within the source server. Then copy all of it to the destination server manually.
How useful was this post?
Click on a heart to rate it!
Average rating / 5. Vote count:
Oh no, sorry about that!
Let us know how we can do better below
Thanks for your feedback!