# Restore a WordPress backup to another site Confirm source, destination, compatibility, overwrite impact, and acceptance checks. The restored copy has expected login, media and sample data. Canonical: https://xcloud.host/use-cases/solutions/restore-a-wordpress-backup-to-another-site/ 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: Confirm source, destination, compatibility, overwrite impact, and acceptance checks. 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: An owner wants to inspect a backup without replacing the public WordPress site. 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: Public DNS or email on a test copy can create confusion. 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: An owner wants to inspect a backup without replacing the public WordPress site. The restored copy has expected login, media and sample data. ## Choose the approach - Choose a safe target with distinct domain and access controls. 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/); [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-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. Identify source backup date and expected contents **Where:** WordPress public/admin views and relevant provider evidence **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Identify source backup date and expected contents; exact site identity, named approver and controlled sample data. **Action:** Select the source backup date, expected files/database scope and representative user/content records. **Expected result:** The owner knows what the copy should contain. **Verify:** The owner knows what the copy should contain. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If the backup identifier is ambiguous, inspect xCloud history before proceeding. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [xCloud restore backup to another site](https://xcloud.host/docs/how-to-restore-a-backup-to-another-site/); [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/) ### 2. Review the isolated destination **Where:** xCloud Site Backup and destination site overview **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Prepare isolated target and confirm capacity; exact site identity, named approver and controlled sample data. **Action:** Ask the xCloud owner to identify an existing eligible target or propose a restricted new target and domain with capacity and an outbound-mail suppression plan. This review does not create a site. **Expected result:** The approved target is identified and cannot be confused with public production. **Verify:** The approved target is identified and cannot be confused with public production. Record the exact account or record tested, result, and time with the responsible owner. **If it fails:** If the target could send real customer notices, disable delivery on the copy first. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [xCloud restore backup to another site](https://xcloud.host/docs/how-to-restore-a-backup-to-another-site/); [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/) ### 3. Use dashboard restore-to-another-site path **Where:** xCloud Site Backup dashboard **Permissions:** Named xCloud team/site administrator; confirm target and scope. **Inputs:** Use dashboard restore-to-another-site path; exact site identity, named approver and controlled sample data. **Action:** In the xCloud dashboard choose restore to another site, verify source point and destination, then start the approved operation. **Expected result:** A copy is restored without overwriting public site. **Verify:** A copy is restored without overwriting public site. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If the target shown is production, cancel before confirmation. Capability: Restore a backup Sources: [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/); [xCloud restore backup to another site](https://xcloud.host/docs/how-to-restore-a-backup-to-another-site/); [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) ### 4. Check urls, login, media and email suppression **Where:** WordPress public/admin views and relevant provider evidence **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Check urls, login, media and email suppression; exact site identity, named approver and controlled sample data. **Action:** On the copy inspect login, representative media, content URLs and business records while keeping search indexing and email controlled. **Expected result:** The backup content matches expectation. **Verify:** The backup content matches expectation. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If database or uploads are missing, investigate backup scope and try another point. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [xCloud restore backup to another site](https://xcloud.host/docs/how-to-restore-a-backup-to-another-site/); [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/) ### 5. Record copy disposition **Where:** Recovery decision sheet and xCloud site inventory **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Document differences and keep public routing unchanged; exact site identity, named approver and controlled sample data. **Action:** Record differences from current production and ask the owner to decide whether to retain or delete the copy in a separate authorized dashboard action. **Expected result:** The rehearsal report names an owner and a later cleanup decision. **Verify:** The rehearsal report names an owner and a later cleanup decision. Record the exact account or record tested, result, and time with the responsible owner. **If it fails:** If live data appeared on the test domain, restrict access and review exposure. Capability: Business owner review and acceptance Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [xCloud restore backup to another site](https://xcloud.host/docs/how-to-restore-a-backup-to-another-site/); [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/) ## 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 restored copy has expected login, media and sample data. 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. Public DNS or email on a test copy can create confusion. 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/) - **Restore a backup** (dashboard; manual): Native and Docker restore operations are dashboard-only. An in-place Docker restore replaces current data. Checkpoint: Use Site → Site Backup → Previous Backups → Restore Backup (or Restore to Another Site where offered). Confirm exact target and recovery point before proceeding. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [Back up and restore Docker apps](https://xcloud.host/docs/backup-and-restore-docker-apps/) - **Business owner review and acceptance** (app; manual): Human planning, acceptance and record reconciliation cannot be inferred from xCloud resource reads. The business owner chooses the application's source of truth. Checkpoint: Record approved criteria, observed application evidence, unresolved questions and named follow-up. Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) ### Copyable agent brief ```text Help with restore a wordpress backup to another site 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: Identify source backup date and expected contents; Review the isolated destination; Use dashboard restore-to-another-site path; Check urls, login, media and email suppression; Record copy disposition. The acceptance check is: The backup content matches expectation. 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: In the xCloud dashboard choose restore to another site, verify source point and destination, then start the approved operation. - The business owner compares the controlled sample with this observable result: The backup content matches expectation. - 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 restored copy has expected login, media and sample data. Steps: phase-4 - **recovery** (covered): Public DNS or email on a test copy can create confusion. 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 - [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 - [xCloud restore backup to another site](https://xcloud.host/docs/how-to-restore-a-backup-to-another-site/) — reviewed 2026-09-30 - [Back up and restore Docker apps](https://xcloud.host/docs/backup-and-restore-docker-apps/) — reviewed 2026-09-30 ## Continue [Explore the next WordPress workflow](https://xcloud.host/use-cases/solutions/recreate-a-wordpress-site-from-a-backup/) - [Back up and recover a Docker application](https://xcloud.host/use-cases/operations/docker-backup-and-recovery/)