Separate preparation from import
The newer reviewed source adds guided DNS, website and database prerequisite workflows to account migration. These supplement registered-source inventory and suspended destination mapping; they do not turn a source archive into a complete reconstructed hosting account. Use only an exact installed version with the matching service configured and accepted.
DNS preparation
POST /v1/migration-dns-previews inspects the registered archive and requested destination under current installation authority. /v1/migration-dns-imports submits the reviewed DNS preparation. A preview must show the exact source digest, owning account, resource names and conflicts. DNS import does not register a domain or change parent delegation/registrar glue.
Website preparation
POST /v1/migration-website-previews and /v1/migration-website-imports prepare the supported account-owned website configuration. Review source names, destination roots and capability before creating resources. A prepared virtual host does not prove imported files, public routing, PHP health or TLS issuance.
Database prerequisites
POST /v1/migration-database-previews and /v1/migration-database-preparations prepare supported destination database resources. Review logical names, engine, same-account bindings and private credential handling. Imported SQL is a later explicit component flow; prepared schema/database identity is not proof of complete data or grants recovery.
Review and verify
Use the server-generated typed preview/confirmation and current source scan digest. Keep one idempotency key for the reviewed submission and record every returned durable operation. Wait for each prerequisite to succeed, then refresh current destination inventory before building the component migration plan. A capability-unavailable service must remain unavailable rather than returning fake prerequisite success.
Recovery and limits
Preserve the original source, plan and destination snapshot. On stale/changed source, obtain a new preview; on uncertain delivery, inspect the original job and resource before resubmitting. Component rollback and recovery do not automatically reconstruct all passwords, application secrets, transfer identities or public DNS/TLS. General one-click Website Migration remains unavailable in the requested menu, and production migration/reconstruction acceptance is not established by these newer source handlers.