Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrations: unclear feedback on failure #99355

Open
pkevan opened this issue Feb 5, 2025 · 4 comments
Open

Migrations: unclear feedback on failure #99355

pkevan opened this issue Feb 5, 2025 · 4 comments
Labels
[Feature] Site Migration Features related to site migrations to WPcom Groundskeeping Issues handled through Dotcom Groundskeeping rotations [Pri] High Address as soon as possible after BLOCKER issues [Status] Auto-allocated [Status] Escalated to Product Ambassadors [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended

Comments

@pkevan
Copy link

pkevan commented Feb 5, 2025

Context and steps to reproduce

When submitting a site, that could potentially be moved to WP.com, the user is presented with an option to input their current website, but when no suitable option is found there isn't a clear reason, or options to allow the user to progress.

Enter this:
Image

You end up here:
Image

If your platform isn't listed (e.g. Wix) then there is no step forward, and you can only choose to go back.

Ideally there would be other options provided and some reasons to why it either failed, or was unable to suggest a next option.

Site owner impact

Fewer than 20% of the total website/platform users

Severity

Moderate

What other impact(s) does this issue have?

Platform revenue

If a workaround is available, please outline it here.

No response

Platform

Simple

@pkevan pkevan added [Feature] Site Migration Features related to site migrations to WPcom [Type] Bug When a feature is broken and / or not performing as intended Needs triage Ticket needs to be triaged labels Feb 5, 2025
@matticbot matticbot added the [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts label Feb 5, 2025
@github-actions github-actions bot added [Status] Escalated to Product Ambassadors [Pri] High Address as soon as possible after BLOCKER issues labels Feb 5, 2025
@janmckell
Copy link

janmckell commented Feb 5, 2025

📌 REPRODUCTION RESULTS
– This is an Onboarding screen before a user creates their site, so Simple/Atomic doesn't apply

📌 FINDINGS/SCREENSHOTS/VIDEO
Include any additional details or steps to reproduce.
Attach screenshots or videos.

I tried 'Get started' from the Pricing plans page as well as the 'create one here' link on the 'Migrate Website' support article.

I also tried the 'Import or migrate an existing site' link when 'New site' is clicked from inside a user's existing dashboard if they already have other sites.

They both had the same result.

📌 ACTIONS
– Asked about it in Serenity Team Channel: > p1738788940960319-slack-serenity

@janmckell janmckell moved this from Needs Triage to Triaged in Automattic Prioritization: The One Board ™ Feb 5, 2025
@janmckell janmckell added Triaged To be used when issues have been triaged. and removed Needs triage Ticket needs to be triaged labels Feb 5, 2025
@andres-blanco andres-blanco added the Groundskeeping Issues handled through Dotcom Groundskeeping rotations label Feb 6, 2025
@andres-blanco andres-blanco moved this from Triaged to Needs shaping in Automattic Prioritization: The One Board ™ Feb 6, 2025
@andres-blanco
Copy link
Contributor

I've responded in the Slack ping above.
We need to understand what would a better alternative to this behaviour is, and then, we can develop it. I think it's correctly assigned to Serenity.

@pkevan
Copy link
Author

pkevan commented Feb 7, 2025

I've responded in the Slack ping above. We need to understand what would a better alternative to this behaviour is, and then, we can develop it. I think it's correctly assigned to Serenity.

Some simple text based improvements could indicate to the user that their platform/site isn't currently supported when reaching the Import Content from another platform, i.e. Unfortunately we were unable to automatically import your site, please choose from the options below, or try starting from scratch and use XXX guide to help with that.

@janmckell
Copy link

There is some comprehensive advice coming from @jp-imagines and @marcuswisecaesar on this..

Good call on improving the messaging here—we definitely want to make sure users know they’re not stuck just because their platform isn’t supported for automatic import. The key is to:

  • Acknowledge the limitation without making it feel like a dead end.
  • Reassure them that moving to WordPress.com is still possible.
  • Give them clear next steps so they know exactly what to do next.

Here’s something that might work:

  • We weren’t able to automatically import content from your platform, but you can still bring your site to WordPress.com! Here’s how you can get started:
  • Start from scratch & build your site manually – Our HTML import guide can walk you through the process step by step.
  • Check for third-party export options – Some platforms allow you to export content in a format that might work with WordPress.com. Check out our alternate migration options here and here for more info.
  • Let an expert handle it for you – If you’d rather skip the hassle, our Built By WordPress.com service can take care of everything. Head over to builtbywp.com, click Apply Now, and tell us about your project. Someone will be in touch soon!
  • Need help? Our Happiness Engineers are happy to guide you through the process.

This keeps it friendly, clear, and action-focused while giving users multiple paths forward.

..otherwise, the MarTech folks may be able to guide further on wording..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Site Migration Features related to site migrations to WPcom Groundskeeping Issues handled through Dotcom Groundskeeping rotations [Pri] High Address as soon as possible after BLOCKER issues [Status] Auto-allocated [Status] Escalated to Product Ambassadors [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended
Projects
Development

No branches or pull requests

4 participants