Share your feedback...
Improve slow migration speeds
We're noticing really slow transfer times with the new migration plugin (often less than 1Gb per hour). What would be a normal expectation for transfer rate? A couple of weeks back it seemed way faster, but the last week plus, it's been painfully slow. (Even the old migration plugin has been really spotty for us lately too. It will transfer just a small bit of media before saying it's "finished" even though most of the media never made it over. So we have to re-run the migration multiple time, sometimes a dozen or more, for it to fully transfer all the media over.) I realize they are probably utilizing two totally different networks, but just a bummer that both are problematic at the moment. We're spending way more time on migrations than we did in the past.
Ensure the new plugin works as well as the old plugin
As the product manager of new WP Engine Site Migration plugin, I am creating this post for those who have feedback about the differences between the new plugin and the old WP Engine Automated Migration plugin (powered by BlogVault) which will be retired on February 27, 2024. We're actively working to improve the reliability of the new plugin, and I am monitoring every post on this feedback board. While you are welcome to add to the conversation below, I also encourage you to search the feedback board for existing posts that may describe your specific experience. If there is not an existing post, create a new post that includes a detailed description along with any relevant screenshots. Other details that help us to investigate these issues include: Migration ID Source or Destination URL WP Engine Environment Name If you are more comfortable discussing the details of your migration in private, you can also leave a comment and I will reach out to you via email.
Retain the table prefix of the source site
It would be great to have an option to retain a custom table prefix. After migrating from Flywheel (custom prefix) to WP Engine (wp_ prefix) we noticed some issues with plugins. I ended up sticking with the wp_ prefix but I had to find/replace references to the old Flywheel prefix manually on the database.
Prevent DNS issues after a completed migration
Every time I've attempted to transfer a wordpress site using the migration tool within WPE's Site Migration tab it has always brought over a broken, nonfunctional mess. The BlogVault migration plugin however has worked flawlessly. Is there any guarantee that these issues will be resolved since the BlogVault plugin is reaching end of life? I assumed there would be no way to continue using that plugin after the end of life date.
Migrate root directories and files
As a migrator who has important files in the root directory, I want the ability to include those files in the migration so I don't have to manually move them via SFTP.
Prevent "temporary file not found" errors
Sorry to be vague on the technicals, but just want to say I have never had a successful migration with the new plugin. It always craps out with some vague error or says "migration canceled" with no explanation, and I always have to revert back to using to the legacy migration plugin (which still works great).
Prevent terminated migrations
It happens mostly on media migration without any information if the file that made it stuck is too big or if we should increase memory
Disabled WP Migrate
This disabled WP Migrate (formerly Migrate WP DB Pro). Which whatever, you can change your branding, but the new plugin doesn't provide 90% of the functionality, so now I can't export DB's or use my saved import/export profiles. This is not at all a replacement for WP Migrate and BlogVault's extremely reliable migration tool.