Wp-calypso: Clone site - completion email and notification

[MichaelArestad]

Once the clone process is complete, we're going to send them an email notification just like we do with a restore.

Email

Notification

Notes

• We will need a support doc or maybe a blog post guiding through site migration via the link in the last paragraph of each image. CC @annezazu
• @rcoll or @singerb Do we need an error state email/notification? I'm happy to mock that up as well.

[MichaelArestad]

As for the SVG, I believe that's already an image asset in use in other emails (perhaps purchase completion emails). I can always reexport it as a PNG if you need me to.

[annezazu]

@tmmbecker heads up on this part:

We will need a support doc or maybe a blog post guiding through site migration via the link in the last paragraph of each image. CC @annezazu

As for the wording, can we remove "There shouldn't be any problems". That just immediately makes me nervous reading that over. "It should be fine but...." doesn't inspire confidence :D "Lend a hand" is also a bit ableist. Here are some alternatives:

• If your site looks different than expected for any reason, please contact support so we can make it right.
• If your site looks different than expected for any reason, please contact our support team who can help fix this for you.
• If your site looks different than expected, please contact support so we can look into any problems for you.
• SUPER SIMPLE: If your site looks different than expected, please contact support.

[michelleweber]

+1 to taking out the "shouldn't be problems" bit.

Your clone is complete! Take a minute to visit your new site, which should be identical to [name]. If anything looks different or unexpected, contact our support team -- they'll get things ironed out.

And if you're migrating content to your new site, we've got a handy guide to help!

[tmmbecker]

What's the difference between a clone and a migration? Why would they need a guide to help them migrate their content if they've just cloned it to a new site? Aren't these one in the same for our purposes?

[MichaelArestad]

@tmmbecker Clone just is an alternate restore and can be used in various ways like staging. Not just for migration. However, if they are migrating, they may want to update URLs and, if necessary, fix the ID crisis following if they switch to the same domain (host switch). Cloning or alternate restore use isn't super common, but it's necessary to maintain feature parity with VaultPress.

[tmmbecker]

Thanks for clarifying @MichaelArestad. I'd argue that alternate restores are more common than that and that most of our users would use this feature to migrate the site rather than staging. I don't know that the doc for explaining a clone would necessarily be different than the doc for explaining a migration. We can highlight what you've explained, but it would likely just be another heading in the same doc. Does that make sense?

[MichaelArestad]

@tmmbecker that makes sense

[stale[bot]]

This issue has been marked as stale and will be closed in seven days. This happened because:

• It has been inactive in the past 9 months.
• It isn't a project or a milestone, and hasn’t been labeled `[Pri] Blocker`, `[Pri] High`, `[Status] Keep Open`, or `OSS Citizen`.

You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation.