Pre-Migration Planning and Requirements
Before you migrate cPanel to Plesk, you need a destination server running Plesk Panel with the Migration and Transfer Manager extension. Most Plesk installations include this by default, but double-check through Extensions → My Extensions in your dashboard.
Document your current cPanel setup completely. List all domains, subdomains, email accounts, databases, and SSL certificates. Check disk usage in cPanel → Disk Usage to ensure your new server has enough space. Add at least 20% buffer space beyond current usage for growth.
Schedule your migration during low-traffic hours. Email services will have brief interruptions during DNS propagation. Website downtime ranges from 15 minutes to several hours based on your domain count and data volume.
Installing Plesk Migration Tools
Access your destination Plesk server and go to Extensions → Extension Catalog. Search for "Plesk Migrator" and install it if it's not already there. This tool handles most cPanel-to-Plesk transfers automatically.
The migrator works with cPanel 11.30 and newer versions. Check your source cPanel version in WHM → Server Information. Older versions might need manual migration steps for certain components.
Set up migration settings before you start. Go to Extensions → Plesk Migrator → Settings and review transfer options. Enable "Create backups before migration" so you can rollback if something goes wrong.
Preparing Your cPanel Server
Create a migration user account in cPanel with full privileges. This account lets Plesk access your current hosting data. Use WHM → Account Functions → Create a New Account or work with your hosting provider's support team.
Generate a fresh backup of critical data through cPanel → Backup Wizard. Select "Full Backup" and download the archive to your local system. This becomes your safety net during migration.
Document custom configurations that won't transfer automatically. Note any custom Apache directives in .htaccess files, PHP settings modifications, or specialized email filters. Hostperl VPS customers can contact our migration support team to review these configurations before starting.
Executing Domain Migration
Launch Plesk Migrator from Extensions → Plesk Migrator. Choose "Migrate from cPanel" and enter your source server details. Provide the IP address, migration user credentials, and select SSH or API access method.
Select domains carefully for migration. Start with a test domain if possible—choose one with minimal traffic and simple configuration. This tests your process before moving production sites.
Review the migration summary before proceeding. Plesk shows estimated transfer time based on data volume. Large sites with extensive databases may take several hours. Click "Start Migration" and monitor progress through the dashboard.
Common issues include PHP version mismatches and custom module dependencies. Plesk tries to match cPanel's PHP configuration, but review PHP settings post-migration through Domains → domain.com → PHP Settings.
Email Account and Data Transfer
Email migration happens automatically during domain transfers, but verify completeness afterward. Check that all email accounts appear in Mail → Email Addresses with correct quotas and forwarding rules.
Mailbox data transfers can take considerable time for accounts with large message volumes. Monitor transfer progress in Tools & Settings → Migration Manager. Failed email transfers show specific error messages—common causes include corrupted message files or exceeded quotas.
Test email functionality immediately after migration. Send test messages both inbound and outbound from each account. Verify that spam filters, autoresponders, and forwarding rules work correctly. The complete Plesk email setup guide covers additional configuration details.
Configure email clients with new server settings. IMAP/POP3 hostnames change from your cPanel server to the new Plesk server address. Update these settings on all devices to prevent connection errors.
Database Migration and Verification
MySQL databases transfer automatically but need verification. Access Databases → Database Servers in Plesk to confirm all databases appear with correct sizes and user permissions.
Test database connectivity from applications immediately. WordPress sites, for example, should display normally without database connection errors. Check application logs for any database-related issues that surface after DNS propagation.
Database user privileges sometimes need adjustment post-migration. Go to Databases → User Management and verify that each database user has appropriate permissions. Grant additional privileges if applications report access denied errors.
For large databases exceeding 2GB, consider using mysqldump for manual transfer if automated migration fails. This gives you more control over the transfer process and better error handling for complex database structures.
SSL Certificate Migration
SSL certificates need special attention during migration. Let's Encrypt certificates from cPanel won't transfer directly—you'll need to generate new certificates in Plesk.
For each domain, go to SSL/TLS Certificates → Let's Encrypt and request new certificates. Plesk will automatically configure renewal settings. Custom or purchased SSL certificates need manual installation through SSL/TLS Certificates → Upload Certificate.
Test SSL functionality on all domains post-migration. Check certificate validity and ensure redirects work properly. The SSL certificate installation guide provides troubleshooting steps for common certificate issues.
Update any hardcoded HTTP links to HTTPS in your website content. Search for internal links, image sources, and API endpoints that may still reference the old server or use insecure protocols.
DNS Configuration and Propagation
DNS changes trigger the actual cutover to your new Plesk server. Update nameservers at your domain registrar to point to your new hosting provider. This process varies by registrar but typically involves changing NS records in the domain management panel.
Monitor DNS propagation using tools like dig or nslookup. Check that A records resolve to your new server IP address. Propagation typically completes within 24-48 hours, though some regions may take longer.
Keep your old cPanel server active during propagation. Users may still reach the old server until DNS changes fully propagate worldwide. Plan for overlap period costs when budgeting your migration.
Configure DNS zones in Plesk if you're managing DNS internally. Go to DNS Settings for each domain and verify all necessary records exist—A, AAAA, MX, CNAME, and TXT records should match your previous configuration.
Post-Migration Testing and Optimization
Run comprehensive testing once DNS propagation completes. Test website functionality, form submissions, login systems, and any dynamic features. Pay special attention to applications that interact with databases or external APIs.
Review Plesk logs for any errors or warnings. Check Logs → Error Logs for each domain and address any issues that appear. Common problems include missing PHP extensions or incorrect file permissions.
Optimize Plesk settings for your specific use case. Configure automatic updates in Tools & Settings → Updates and Upgrades. Set up monitoring alerts for disk space, resource usage, and service availability.
Document your new Plesk configuration for future reference. Record login credentials, important settings, and any customizations made during migration. This documentation proves invaluable for ongoing server management and future migrations.
Planning a cPanel to Plesk migration for your hosting infrastructure? Hostperl VPS hosting includes migration assistance and Plesk licensing to ensure a smooth transition. Our New Zealand-based support team helps with pre-migration planning and post-migration optimization.
Frequently Asked Questions
How long does a typical cPanel to Plesk migration take?
Migration time depends on data volume and domain count. Small sites with single domains complete in 30-60 minutes. Large installations with multiple domains and extensive databases may require 4-6 hours. Plan for DNS propagation adding another 24-48 hours for complete cutover.
Will my website experience downtime during migration?
Minimal downtime occurs during DNS propagation when traffic shifts from old to new servers. The actual migration process runs in parallel, so your cPanel server remains operational. Most users experience no noticeable interruption if migration is properly timed.
Can I migrate only specific domains from a multi-domain cPanel account?
Yes, Plesk Migrator allows selective domain migration. Choose specific domains from the migration interface rather than migrating the entire account. This approach works well for phased migrations or when moving only certain sites to new hosting.
What happens to custom PHP configurations and modules?
Standard PHP configurations transfer automatically, but custom modules may need reinstallation. Review PHP extension availability in Plesk and install any missing modules through Tools & Settings → PHP Settings. Test application functionality thoroughly after migration.
Do email messages and folders transfer completely?
Email messages transfer automatically for IMAP accounts, including folder structures and message flags. POP3 accounts may lose server-side messages if they've been downloaded to email clients. Verify message counts match between old and new servers post-migration.
