Migrator: subsite to its own hosting, and standalone site into the network
Imported from GitHub issue El-SaMa/oma#176 by @El-SaMa.
Out of the network (client outgrows it)
- Export a subsite to a standalone WordPress: tables renamed to a single-site prefix, users and their meta copied, URLs and upload paths rewritten (
uploads/sites/N→uploads), required themes and plugins installed, licences sorted (operator). - Target: a new Enhance website on a Pro plan via OMA provisioning; DNS switch with low TTL; verification (HTTP, sample pages, Woo checkout test); subsite left read-only then archived.
Into the network (onboarding)
- Import a standalone WordPress into a new subsite (plugins outside the catalogue reported and replaced or blocked).
Both
- Dry run report before the real move; MCP tools and portal button for staff; customer-facing request flow.
Acceptance criteria
- A staging shop subsite moved out to an Enhance test site with orders and users intact.
Depends on
#175.
Plan key W22. Epic: El-SaMa/lamoi-waas#25.