WordPress.com on Atomic: Allow migrations/cloning across WoA sites.

[JoshuaGoode]

What The ability to migrate/clone between two WordPress.com on Atomic (WoA) sites

Why This is a common request from designers, developers, agencies, and technical users that wish to easily copy or migrate an existing WoA site to another.

Not just site cloning, to a new site. But migrating between existing sites.

How Use the Everything Import option in place but enable it to work for WoA to WoA. Or Jetpack's clone/copy feature.

Additional context We've discussed this multiple times in the past and have had a moderate amount of interactions requesting this. I would need to dig in and find those -- starting this to start tracking new reports.

[JoshuaGoode]

If we don't route through the WPCOM/Everything importer, perhaps the cloning/migration feature already provided by Jetpack? https://jetpack.com/support/cloning/

The Atomic platform also supports Jetpack-less cloning which is in use on a non-WoA provider.

[JoshuaGoode]

A previous discussion about Atomic API cloning while WPCOM Migration was being developed: pbkcP4-8-p2#comment-48

Recent internal threads where a user requested this:

• p1615838869313300/1615838679.311300-slack-C03TY6J1A
• p1615832525287100/1615830826.282800-slack-C03TY6J1A
• p1614884969298200/1614884492.297000-slack-C3GP81E05

Internal P2 thread: pbkcP4-gn-p2

A request for a WordPress.com site to be cloned that could have used such a feature: p9F6qB-6oC-p2

[Jaccuse]

An interaction where a user was requesting this functionality can be found at: 9948558-hc

[yoavf]

Noting that while Atomic to Atomic migrations via the WP migration tool is theoretically possible (though currently disabled), they are very slow and resource-intensive. We should look at this from an Atomic infrastructure POV where it might be significantly easier and faster to clone an existing site.

[nagpai]

As per internal discussion (p58i-agZ-p2), the Atomic platform has a built in API provision to clone sites. This is used by Pressable already.

It may need some developer efforts to create a HE facing tool and eventually a user facing one.

[davipontesblog]

Related: https://github.com/Automattic/wp-calypso/issues/52241 With this ability described in this issue here, the one above becomes easier to implement.

[formosattic]

30081957-hc

User had attempted to create a local staging site, using All-in-One WP Migration, but it had lots of difference with the WoA version.

For users with multiple sites, suggesting getting another Business plan for each of them is a real hassle.

Related request tracked at 384-gh-Automattic/atomic

[dragstor]

I got a chatter asking about this: 32552151-HC, and had heard about the same request multiple times from various HEs.

[davipontesblog]

Here is a user that could have used this for a much easier experience for them: 32722397-hc.

[davipontesblog]

User could have used this here: 32750926-hc

[nagpai]

I hope this feature sees light of the day sooner 34337636-hc

[arunsathiya]

Staging requested on 35106803-hc to test a WooCommerce payments gateway conflict.

[JoshuaGoode]

Being able to easily restore a downloaded Jetpack backup to another site could suffice.

[filipanoscampos]

Another request here 35390738-hc.

[cuemarie]

This user (from Codeable) definitely could have benefitted from this solution: 36419841-hc

As they are using a plugin to migrate their dev site to their live site (both hosted here), they have to contact us repeatedly to fix the Jetpack issues that follow an AIO migration. An internal solution would be so much better!

[NoHopeRadio]

User wanted to import content from one Atomic WordPress.com site to three other Atomic WordPress.com sites.

38348109-hc

[kavyagokul]

Similar request in 43209028-hc , after I realized that 'copy-site' doesn't work on ecommerce plan sites