How To Migrate WordPress From WP Engine Or Kinsta
Managed WordPress hosts add platform caches, staging environments, restricted plugins, provider-specific configuration, and DNS or proxy layers around the WordPress files and database. The destination needs the WordPress application and customer data, but it usually does not need provider-generated cache files or platform-specific helpers.
Confirm The Environment
- Identify production and staging separately so the wrong environment is not migrated.
- Record the WordPress and PHP versions, multisite status, database size, uploads size, domain aliases, and redirects.
- List provider cache, CDN, edge rules, environment variables, cron replacements, and restricted or required plugins.
- Confirm SFTP or SSH access and a current database export or application-level source agent route.
Prepare A Neutral Destination
Create a fresh WordPress destination with a compatible PHP version, database, writable uploads directory, and enough disk and inode capacity. Use a temporary hostname or hosts-file override for testing. Keep the final domain on the managed host until the restored site passes review.
Transfer WordPress Data
Move the application files that belong to the site, including themes, plugins, uploads, and required configuration. Export and import the database, then update destination database credentials. Skip disposable caches and provider-specific generated files only after confirming WordPress can rebuild without them.
Replace URLs Safely
Managed-host staging URLs often appear in serialized WordPress data. Use a serialized-safe search and replace for the staging or old domain, then inspect menus, widgets, page builders, media, redirects, and plugin settings. Plain SQL replacement can corrupt serialized values.
Recreate Platform Services
Configure destination page cache, object cache, CDN, cron, backups, SMTP, security rules, redirects, and SSL. Remove provider-specific must-use plugins only when they are not required on the destination. Test admin login, frontend pages, media, forms, ecommerce, webhooks, and scheduled work.
Cut Over And Watch Logs
Run a final database and uploads delta for changing sites, update DNS or proxy origin records, purge every cache layer, and monitor PHP, WordPress, web server, and CDN logs. Keep the source account available through the acceptance window. Use the WordPress search-and-replace guide and post-migration checklist to finish.