Moving Licenses Between Sites
Royal MCP Pro-specific notes on moving a seat. The full move walkthrough — standard flow, forgot-to-deactivate recovery, activation-limit conflicts — is centralized because it's identical for every Royal Plugins Pro plugin.
The complete step-by-step walkthrough (standard move, forgot-to-deactivate recovery via the Active Sites view, activation-limit conflicts, staging → production patterns, edge cases) is centralized at Licensing → Moving Licenses Between Sites →. This page adds only the Royal MCP Pro-specific pieces.
Royal MCP Pro-specific move details
Where the License page lives
On both the old and new site, license management is at wp-admin → Royal MCP Pro → License. Same button labels apply: Deactivate License on the old site, Activate License on the new one.
Verify Pro is live on the new site
After activating on the new site, call royal_mcp_connection_health from any MCP client. The response includes pro_licensed: true when the seat has been claimed successfully. See Royal MCP Pro License & Renewals for the exact response shape.
What Royal MCP Pro data stays on the old site
Deactivating removes the license, not your Pro-created data. On the old site, the following stay in the database even after deactivation:
- Audit Log rows
- Endpoint Profiles
- Undo store table (tokens remain visible even after they become unredeemable)
- Pro-tier settings
If you want any of this on the new site, export it separately before deactivating. For the Audit Log specifically, use the CSV export from Royal MCP Pro → Audit Log before deactivating (see CSV Export).
What doesn't transfer with the move
- OAuth clients registered on the old site stay on the old site (OAuth is a Free-tier feature that persists in each site's own database). On the new site, MCP clients (Claude Desktop, ChatGPT, Cursor) go through the connection flow fresh.
- Undo tokens issued on the old site cannot be redeemed on the new site — they're tied to that site's local storage table.
If the sites share the same WordPress install (e.g., you're renaming a domain), a full database + files migration moves everything with it and no separate export is needed.
Still Stuck? Two-Step Support Path
If the move isn't working, work through these two steps in order.
Step 1: Cross-check on My Account
Go to My Account → Active Sites and confirm:
- The Royal MCP Pro license shows Active (not Expired or Cancelled)
- The activation count is below your tier's limit
- The old site you meant to deactivate no longer appears in Active Sites — if it does, deactivate it directly from that dashboard
If your issue is a specific activation error, see License Activation Issues. Full walkthrough of the Active Sites view (columns, "Last seen" timestamps, remote deactivation): Connected Sites Dashboard.
Step 2: Email priority support
If you've verified the license state on My Account and the move still won't complete, email support@royalplugins.com from your purchase email address. Priority email support is included with every Pro license — typical response within 24 hours. Never include your license key in email; we look it up from your purchase address.
- The old site URL and the new site URL you're moving between
- Hosting provider for each site (SiteGround, Cloudways, Kinsta, WP Engine, self-hosted VPS, etc.)
- Royal MCP Pro version on the new site (from WP Admin → Plugins)
- The exact error message from the License page on the new site, if any
- What you've already tried — direct local deactivate, remote deactivate from Active Sites, wait-and-retry, force refresh, etc.
- Screenshot of the License page on the new site showing the current state
- Screenshot of My Account → Active Sites showing the connected sites list