# Prepare a WordPress migration cutover Inventory site state, plan migration destination, DNS changes, and acceptance testing. The target accepts new leads after DNS change and old leads reconcile. Canonical: https://xcloud.host/use-cases/solutions/prepare-a-wordpress-migration-cutover/ Published: 2026-09-30 · Updated: 2026-09-30 · Technical review: 2026-09-30 Evidence: Source reviewed; no production deployment test claimed Editorial owner: xCloud editorial Intent: Inventory site state, plan migration destination, DNS changes, and acceptance testing. For: business-owner, operator ## Requirements and responsibilities - Have named ownership of the domain, selected xCloud team and site, and WordPress administrator access. For this scenario, agree who supplies the data and signs off: A business is changing WordPress hosts without losing form leads near launch. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/) - Use a compatible Nginx or OpenLiteSpeed stack for native WordPress. Verify current server resources, plan eligibility and each selected plugin or service license and requirements before installing; a Docker server does not host a new native WordPress site. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [WordPress plugin administration](https://wordpress.org/documentation/article/manage-plugins/) - Prepare a safe test identity and a completed, accessible backup before consequential changes. The important failure to plan around is: A DNS switch can straddle two live databases. Sources: [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/); [WordPress hardening handbook](https://developer.wordpress.org/advanced-administration/security/hardening/) - Before any database copy or restore starts, the authorized operator restricts the target and quarantines outbound mail, payment, fulfillment and other provider effects. Restored settings may overwrite plugin suppression; reapply sandbox credentials and verify isolation before testing. Sources: [Create a staging environment in xCloud](https://xcloud.host/docs/how-to-create-a-staging-environment-in-xcloud/); [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/) ## Illustrative situation Illustrative scenario, not a customer case study: A business is changing WordPress hosts without losing form leads near launch. The target accepts new leads after DNS change and old leads reconcile. ## Choose the approach - Select a cutover window and explicit content freeze or replay process. Verify the selected provider or plugin documentation and license against this requirement; xCloud hosting does not supply its business configuration. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs); [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [xCloud WordPress migration guide](https://xcloud.host/docs/guide-to-wordpress-site-migration-on-xcloud/) - Keep application setup, domain/DNS ownership, mail delivery and external integrations with their named administrators. Use a plain documented path when a proposed integration cannot be demonstrated end to end. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [WordPress plugin administration](https://wordpress.org/documentation/article/manage-plugins/) ## Dashboard and application procedure ### 1. Inventory source data, mail, dns and integrations **Where:** WordPress public/admin views and relevant provider evidence **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Inventory source data, mail, dns and integrations; exact site identity, named approver and controlled sample data. **Action:** Inventory source WordPress data, integrations, mail, DNS authority and newest lead record. **Expected result:** The migration has a source snapshot and decision owner. **Verify:** The migration has a source snapshot and decision owner. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If ongoing edits cannot pause, start a replay log. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [xCloud WordPress migration guide](https://xcloud.host/docs/guide-to-wordpress-site-migration-on-xcloud/); [Enable HTTPS and configure SSL certificates in xCloud](https://xcloud.host/docs/enable-https-in-xcloud-configure-ssl-certificates/) ### 2. Migrate to a compatible WordPress target **Where:** xCloud Add site and site overview **Permissions:** Named xCloud team/site administrator; confirm target and scope. **Inputs:** Migrate to a compatible wordpress target; exact site identity, named approver and controlled sample data. **Action:** Build a compatible target in xCloud and migrate a copy using the documented procedure, leaving live DNS unchanged. **Expected result:** The target can be tested without public traffic. **Verify:** The target can be tested without public traffic. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If PHP/plugin requirements differ, resolve them on a copy. Capability: Create a WordPress site Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs); [xCloud WordPress migration guide](https://xcloud.host/docs/guide-to-wordpress-site-migration-on-xcloud/); [Enable HTTPS and configure SSL certificates in xCloud](https://xcloud.host/docs/enable-https-in-xcloud-configure-ssl-certificates/) ### 3. Compare latest records and choose freeze boundary **Where:** WordPress public/admin views and relevant provider evidence **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Compare latest records and choose freeze boundary; exact site identity, named approver and controlled sample data. **Action:** Compare recent posts, forms and media; agree a freeze time or a way to replay late submissions from old site. **Expected result:** Cutover has a defined data boundary. **Verify:** Cutover has a defined data boundary. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If both sites can receive leads with no reconciliation, delay DNS change. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [xCloud WordPress migration guide](https://xcloud.host/docs/guide-to-wordpress-site-migration-on-xcloud/); [Enable HTTPS and configure SSL certificates in xCloud](https://xcloud.host/docs/enable-https-in-xcloud-configure-ssl-certificates/) ### 4. Lower dns ttl if appropriate and switch approved records **Where:** Authorized DNS provider and public browser **Permissions:** Named xCloud team/site administrator; confirm target and scope. **Inputs:** Lower dns ttl if appropriate and switch approved records; exact site identity, named approver and controlled sample data. **Action:** At approved time the domain owner updates exact DNS records; inspect authoritative answers and HTTPS on the target. **Expected result:** New visitors reach the intended target. **Verify:** New visitors reach the intended target. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If traffic splits, retain old site data and reconcile both sides. Capability: Change domain DNS and verify routing Sources: [xCloud WordPress migration guide](https://xcloud.host/docs/guide-to-wordpress-site-migration-on-xcloud/); [Enable HTTPS and configure SSL certificates in xCloud](https://xcloud.host/docs/enable-https-in-xcloud-configure-ssl-certificates/) ### 5. Watch both sites and reconcile late submissions **Where:** WordPress public/admin views and relevant provider evidence **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Watch both sites and reconcile late submissions; exact site identity, named approver and controlled sample data. **Action:** Monitor first real submissions and old-host logs, then close old intake only when late records are accounted for. **Expected result:** No lead is silently abandoned at cutover. **Verify:** No lead is silently abandoned at cutover. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If a new lead remains on old host, move it through the agreed process before shutdown. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [xCloud WordPress migration guide](https://xcloud.host/docs/guide-to-wordpress-site-migration-on-xcloud/); [Enable HTTPS and configure SSL certificates in xCloud](https://xcloud.host/docs/enable-https-in-xcloud-configure-ssl-certificates/) ## Maintenance - Assign a cadence for selected WordPress core, theme and plugin updates, review version-based findings and retest the path in this guide. In particular, repeat: The target accepts new leads after DNS change and old leads reconcile. A chat prompt is not a scheduled task. Sources: [Manage WordPress updates with Updates Manager](https://xcloud.host/docs/manage-wordpress-updates-with-updates-manager/); [Vulnerability Checker in xCloud](https://xcloud.host/docs/vulnerability-checker-in-xcloud/) - Record actual backup completion, storage access and responsible staff. Recheck connected application and provider behavior after changes rather than relying on a site health status alone. Sources: [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/); [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) ## Recovery decisions - Before restoring, compare the chosen recovery point with newer business records. A DNS switch can straddle two live databases. Use the xCloud dashboard for native restore only after the owner approves target and scope; reconcile or preserve newer data first. Sources: [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/); [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) - Validate the restored copy with representative content, authentication, HTTPS and this guide’s business acceptance test before moving traffic or closing the incident. Sources: [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/); [WordPress hardening handbook](https://developer.wordpress.org/advanced-administration/security/hardening/) ## AI handoff Connect xCloud MCP through the current documented profile and grant only the scopes needed for the selected team. Discover tool schemas first. Read resources to plan; require approval for any supported write. Use returned dashboard URLs for manual work. The packaged REST wrapper accepts GET requests only. ### Supported scope - **Confirm requirements and inspect resources** (mcp; read): Discover the connected profile and operation schema first; only teams granted to the connection are visible. Checkpoint: Confirm exact team, server and site identity. Use dashboard\_url returned by the resource; do not invent a dashboard link. Operation identifiers to discover: teams.index, servers.show, sites.show. Scopes: read:servers, read:sites. Sources: [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs); [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) - **Review a WordPress business journey** (app; manual): Application data and observed transactions cannot be inferred from xCloud resource reads. Use authorized test accounts and the application or provider evidence. Checkpoint: Record the test identity, timestamp, expected outcome, observed result and owner decision. Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/) - **Create a WordPress site** (mcp; write): Requires a compatible Nginx or OpenLiteSpeed server; Docker and single-site agentic servers cannot host a new WordPress site. Checkpoint: Approve the exact server, domain, capacity, cost and creation inputs before provisioning. Verify completion and HTTPS. Operation identifiers to discover: servers.sites.wordpress.create. Scopes: write:sites. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs) - **Change domain DNS and verify routing** (app; manual): DNS changes belong to the domain provider or authorized DNS integration; reading an xCloud site does not establish public propagation or certificate validity. Checkpoint: Approve exact hostname and record values; check authoritative DNS and live HTTPS from an independent session. Sources: [xCloud WordPress migration guide](https://xcloud.host/docs/guide-to-wordpress-site-migration-on-xcloud/); [Enable HTTPS and configure SSL certificates in xCloud](https://xcloud.host/docs/enable-https-in-xcloud-configure-ssl-certificates/) ### Copyable agent brief ```text Help with prepare a wordpress migration cutover for the exact xCloud team and site I name. Read available hosting identity and state first, then ask the named WordPress, app, provider or dashboard owner for operations and records outside this connection. Prepare these authored tasks: Inventory source data, mail, dns and integrations; Migrate to a compatible WordPress target; Compare latest records and choose freeze boundary; Lower dns ttl if appropriate and switch approved records; Watch both sites and reconcile late submissions. The acceptance check is: New visitors reach the intended target. Do not infer application transactions or completed dashboard jobs from hosting resource reads. WordPress staging push/pull, backup schedule, restore and cache-setting changes require the authorized dashboard owner; the packaged REST wrapper is GET-only. ``` ### Manual checkpoints - The named WordPress, app, dashboard or provider administrator performs the guide’s actual configuration step: Compare recent posts, forms and media; agree a freeze time or a way to replay late submissions from old site. - The business owner compares the controlled sample with this observable result: New visitors reach the intended target. - Staging push/pull, native backup schedules, restores and cache-setting edits require the authorized xCloud dashboard operator; the packaged REST wrapper is GET-only. ## Feature coverage - **business-acceptance** (covered): The target accepts new leads after DNS change and old leads reconcile. Steps: phase-4 - **recovery** (covered): A DNS switch can straddle two live databases. Steps: phase-5 ## Sources - [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) — reviewed 2026-09-30; v4.4.2 package; xCloud v2.8.8 capability review - [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/) — reviewed 2026-09-30 - [WordPress plugin administration](https://wordpress.org/documentation/article/manage-plugins/) — reviewed 2026-09-30 - [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/) — reviewed 2026-09-30 - [WordPress hardening handbook](https://developer.wordpress.org/advanced-administration/security/hardening/) — reviewed 2026-09-30 - [Create a staging environment in xCloud](https://xcloud.host/docs/how-to-create-a-staging-environment-in-xcloud/) — reviewed 2026-09-30 - [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs) — reviewed 2026-09-30 - [xCloud WordPress migration guide](https://xcloud.host/docs/guide-to-wordpress-site-migration-on-xcloud/) — reviewed 2026-09-30 - [Manage WordPress updates with Updates Manager](https://xcloud.host/docs/manage-wordpress-updates-with-updates-manager/) — reviewed 2026-09-30 - [Vulnerability Checker in xCloud](https://xcloud.host/docs/vulnerability-checker-in-xcloud/) — reviewed 2026-09-30 - [Enable HTTPS and configure SSL certificates in xCloud](https://xcloud.host/docs/enable-https-in-xcloud-configure-ssl-certificates/) — reviewed 2026-09-30 ## Continue [Explore the next WordPress workflow](https://xcloud.host/use-cases/solutions/check-wordpress-mail-delivery-after-launch/) - [Verify WordPress SSL and domain renewal status](https://xcloud.host/use-cases/operations/wordpress-https-certificate-troubleshooting/)