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 leaving an existing host while editors continue publishing.
xCloud agent capability boundaries · WordPress 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.
xCloud agent capability boundaries · WordPress plugin administration
Prepare a safe test identity and a completed, accessible backup before consequential changes. The important failure to plan around is: Changing DNS before comparing databases can lose late submissions.
Before a source copy or backup restore starts, the authorized operator must restrict the target and quarantine outbound mail, payment, fulfillment and other provider effects at the receiving environment. Restored WordPress settings can overwrite plugin suppression; reapply sandbox credentials and verify isolation before tests.
Create a staging environment in xCloud · Site backups in xCloud
Illustrative situation
Illustrative scenario, not a customer case study: A business is leaving an existing host while editors continue publishing. Content, media, login and forms work on the target before and after DNS switch.
Choose the approach
Choose a cutover window and freeze or reconcile edits made on the old host. Verify the selected provider or plugin documentation and license against this requirement; xCloud hosting does not supply its business configuration.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · WordPress roles and capabilities · xCloud WordPress migration guide
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.
xCloud agent capability boundaries · WordPress plugin administration
Dashboard and application procedure
Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.
Step 1 of 5
Capture source records and cutover boundary
- Where
- WordPress administrator or the selected plugin/application
- Permissions
- Named WordPress or selected app administrator; business owner approves results.
- Inputs
- Owner, hostname, approved requirements, sample record and decision date. Capture source records and cutover boundary.
- Action
- Export the source URL inventory and sample recent posts, users, uploads and form entries. Record DNS administrator, old hosting access, mail routing and the last time writers may edit before cutover.
- Expected result
- A source snapshot and late-change boundary exist.
- Verify
- Compare inventory counts and a named newest submission with the current source site.
- If it fails
- If editors cannot pause, establish a replay log for every post and submission created during the move.
Sources: WordPress roles and capabilities · WordPress plugin administration
Step 2 of 5
Choose and protect the target
- Where
- xCloud Add site and site overview
- Permissions
- Named xCloud team/site administrator; confirm the exact production or staging target.
- Inputs
- Target team/site, server or plugin version, license and documented prerequisites. Choose and protect the target.
- Action
- Select a compatible native WordPress target, check PHP/plugin requirements and choose the migration method documented for the source. Create a backup of the source before transferring credentials or files.
- Expected result
- The target and transport method are agreed and the source remains recoverable.
- Verify
- Confirm the target team, server, hostname and backup point against the migration sheet.
- If it fails
- If plugin or PHP support differs, resolve the compatibility gap on a safe copy before moving the database.
Sources: xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · xCloud WordPress migration guide
Step 3 of 5
Migrate files and database to a testable copy
- Where
- WordPress administrator or the selected plugin/application
- Permissions
- Named WordPress or selected app administrator; business owner approves results.
- Inputs
- Approved change scope, backup state, selected version and maintenance window. Migrate files and database to a testable copy.
- Action
- Move the selected files and database through the documented xCloud migration path, then replace environment-specific URLs using an approved method. Leave public DNS on the old host while testing the target.
- Expected result
- The target copy opens internally with representative content and media.
- Verify
- Compare one old and new URL per content type, a recent upload and editor login; inspect broken links.
- If it fails
- If serialized URLs or media paths are damaged, repair on the copy and rerun samples before a DNS switch.
Sources: WordPress roles and capabilities · WordPress plugin administration · xCloud WordPress migration guide
Step 4 of 5
Switch DNS and reconcile late records
- Where
- Authorized DNS provider and public browser
- Permissions
- Named domain/DNS account owner and migration lead; approve exact records and cutover time.
- Inputs
- Test accounts, sample content or transaction, expected result and provider access. Switch DNS and reconcile late records.
- Action
- Freeze or log source changes at the agreed boundary, compare latest form entries and posts, then update the approved DNS records. Monitor old and new endpoints while caches expire.
- Expected result
- New visits and submissions reach the target.
- Verify
- Check authoritative DNS, HTTPS, primary redirects and one post-cutover form record at the target.
- If it fails
- If traffic splits or late records appear on the source, preserve both databases and reconcile them before closing the old host.
Sources: xCloud WordPress migration guide · Enable HTTPS and configure SSL certificates in xCloud
Step 5 of 5
Transfer ownership after acceptance
- Where
- WordPress public pages, administrator and relevant external provider
- Permissions
- Named WordPress or selected app administrator; business owner approves results.
- Inputs
- Observed results, unresolved failures, backup point and owner contacts. Transfer ownership after acceptance.
- Action
- Hand the owner a list of old redirects, mail checks, backup points and observation period. Keep the source read-only until acceptance checks and late-data reconciliation finish.
- Expected result
- The client knows the new operational owner and rollback decision.
- Verify
- Have the owner open priority URLs and confirm a recent content item and inquiry in the target.
- If it fails
- If a priority journey still fails, route traffic back only with a data-reconciliation decision for records already created on the target.
Sources: WordPress roles and capabilities
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: Content, media, login and forms work on the target before and after DNS switch. A chat prompt is not a scheduled task.
Manage WordPress updates with Updates Manager · 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.
Recovery decisions
Before restoring, compare the chosen recovery point with newer business records. Changing DNS before comparing databases can lose late submissions. Use the xCloud dashboard for native restore only after the owner approves target and scope; reconcile or preserve newer data first.
Validate the restored copy with representative content, authentication, HTTPS and this guide’s business acceptance test before moving traffic or closing the incident.
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 and scopes to discover
teams.index, servers.show, sites.show
Scopes: read:servers, read:sites
xCloud MCP documentation and connection profiles · xCloud agent capability boundaries
- Configure WordPress content, users and selected plugins app · manual
Requires a named WordPress administrator or suitable editor. Plugin behavior, commercial license, payment, email and external integration are verified in the chosen vendor documentation and application; xCloud hosting or MCP reads do not configure them.
Checkpoint: Open the actual WordPress or selected plugin interface, record the version and role, and have the business owner accept a real user journey.
WordPress roles and capabilities · WordPress plugin administration
- 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 and scopes to discover
servers.sites.wordpress.create
Scopes: write:sites
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles
- 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.
xCloud WordPress migration guide · Enable HTTPS and configure SSL certificates in xCloud
- 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.
Copyable agent brief
Manual checkpoints
- The named WordPress, app, dashboard or provider administrator performs the guide’s actual configuration step: Move the selected files and database through the documented xCloud migration path, then replace environment-specific URLs using an approved method. Leave public DNS on the old host while testing the target.
- The business owner compares the controlled sample with this observable result: New visits and submissions reach the 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): Content, media, login and forms work on the target before and after DNS switch. Switch DNS and reconcile late records
- recovery (covered): Changing DNS before comparing databases can lose late submissions. Transfer ownership after acceptance
Sources
- xCloud agent capability boundaries
- WordPress roles and capabilities
- WordPress plugin administration
- Site backups in xCloud
- WordPress hardening handbook
- Create a staging environment in xCloud
- xCloud MCP documentation and connection profiles
- xCloud WordPress migration guide
- Manage WordPress updates with Updates Manager
- Vulnerability Checker in xCloud
- Enable HTTPS and configure SSL certificates in xCloud