Improvement: "Migration is underway" /sites info not accurate for assisted migrations #97667
Labels
[Feature Group] Content Management
Features related to the tools and screens that admins use to manage their sites core content.
[Feature] Site Migration
Features related to site migrations to WPcom
[Pri] Low
Address when resources are available.
[Product] WordPress.com
All features accessible on and related to WordPress.com.
[Status] Auto-allocated
[Type] Feature Request
Feature requests
What
TLDR
Update the "Migration is underway" page in
/sites
so that it doesn't indicate that their assisted migration has started before it has.Details
While testing the migration flow today, I requested an assisted migration (for a non-wp site). While the
We'll take it from here
page notes that I will hear back from support with information on how to provide my credentials (which is correct), the/sites
dashboard information tells me the migration is already underway, and that I should sit back, and I will hear back in 2-3 days (which is often incorrect).Why
There are many cases where we can't start immediately on the migration (user provided wrong credentials or backup files, we don't have the right permissions on the site, the site is ecommerce and needs to be scheduled, its a multisite, or not even a wp site at all), and this notice may inadvertently overpromise what we can deliver, and discourage customers from checking their email right away, which we frequently need them to do so that we can access their site and get started.
How
When a customer requests an assisted migration, could this page instead say
Migration Assistance Requested
, with detail that start with how we'll be reaching out to them soon with instructions on how to grant us access to the source site?Bonus: Could this page show a button to "Cancel request", and could that notify us somehow? (This might generate double the tickets and not actually prevent us from replying, so not sure about what's possible there :) )
The text was updated successfully, but these errors were encountered: