Urgent: Managed Services Migration Breaking Websites, Need Help!

I'm completely stuck and tearing my hair out trying to migrate several client websites...

1. Database Connection & Configuration Discrepancies

• Database User/Password/Host: Even if you import the database correctly, the new server's MySQL user and password might not match the old one, or the database host might have changed from `localhost` to a specific IP or hostname.
• Database Prefix: Some migration tools or manual processes can corrupt or change database table prefixes, especially if you're dealing with multiple sites in one database or a non-standard setup.
• Serialization Issues: For CMS platforms like WordPress, serialized data (e.g., widget settings, plugin configurations, custom fields) often contains the old domain or file paths. A simple search-and-replace on the database dump won't fix this correctly, leading to broken layouts or missing content.

• Verify `wp-config.php` (for WordPress) or similar config files: Ensure `DB_NAME`, `DB_USER`, `DB_PASSWORD`, and `DB_HOST` are absolutely correct for the new environment.
• Use a Serialized Data-Aware Search/Replace Tool: For WordPress, tools like Search Replace DB by interconnect/it or the `wp search-replace` command via WP-CLI are indispensable. These correctly handle serialized strings, preventing data corruption.
• Check Database Permissions: Ensure the database user has all necessary privileges (SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, ALTER) on the specific database.

2. PHP Version & Extension Mismatches

• Pre-Migration Audit: Document the exact PHP version and all active PHP extensions on the *old* server.
• Post-Migration Verification: Use the cPanel "Select PHP Version" tool on the new server to match the PHP version and enable all required extensions. Create a `phpinfo.php` file on the new server (``) to verify.

3. File Pathing & Permissions

• Verify Root Paths: Ensure the `DocumentRoot` for the domain in cPanel points to the correct folder (e.g., `public_html` or `public_html/your-site-folder`).
• Check Permissions: Standard cPanel permissions are usually 755 for directories and 644 for files. Ensure the user/group ownership is correct (usually `user:user` or `user:nobody`). Tools like `find . -type d -exec chmod 755 {} \;` and `find . -type f -exec chmod 644 {} \;` via SSH can help, followed by specific exceptions like `wp-config.php` (400 or 440).
• `.htaccess` Rules: These often contain server-specific directives that might not translate directly or conflict with the new server's Apache/Nginx configuration. Check for absolute paths in rewrite rules.

4. Web Server Configuration Differences (Apache vs. Nginx/LiteSpeed)

• Review `.htaccess`: Temporarily rename `.htaccess` to isolate if it's the cause. Then, re-add rules section by section.
• Caching: If you use server-level caching on the old server (e.g., Varnish, Memcached), ensure the new server has similar capabilities or that your application-level caching is correctly configured.

Pre-Migration Checklist:

1. Full cPanel Backup: Generate a full cPanel backup from the *old* server. This is your ultimate safety net.
2. Database Dump: Create a clean `mysqldump` of each database.
3. File Archive: Create a compressed archive (`tar.gz`) of all website files.
4. Document Current Environment: Note PHP version, installed extensions, MySQL version, cron jobs, SSL certificates, domain DNS records, and any custom server configurations.
5. Staging Environment: If possible, migrate to a staging environment on the new server first. This allows you to test thoroughly without impacting live traffic.
6. DNS TTL: Lower the TTL (Time To Live) for your domain's DNS records (A, CNAME, MX) to a low value (e.g., 300 seconds or 5 minutes) 24-48 hours *before* migration to minimize propagation time.

Post-Migration Verification & Tools:

• Check Server Error Logs: These are your best friend. Look in cPanel under "Errors" or via SSH at `/var/log/apache2/error.log` (or similar path for Nginx/LiteSpeed).
• PHP Error Logs: Configure your `php.ini` to log errors, or check default PHP error log locations.
• SSH Access: Essential for debugging, running database search/replace, checking permissions, and viewing logs.
• Browser Developer Tools: Check the console for JavaScript errors and the network tab for failed resource loads.
• DNS Propagation Checkers: Use tools like `whatsmydns.net` to confirm DNS has fully propagated to the new IP.
• Managed Services Support: Leverage the support of your *new* managed services provider. They know their environment best and can quickly identify server-specific issues.

Okay, the `wp-config` and serialized search/replace totally saved my butt on the database errors, but now a couple of the sites are running super slow and throwing random 500s, almost like the new server setup isn't optimized or something deeper is wrong...