Copy or move pages between websites

Guides

Choose copy or move

A copy leaves the original available. A move requires a verified destination plus an explicitly approved decision about the original. Do not delete the source merely because a destination page was created successfully.

The inspected MCP tool named transfer_pages transfers subtrees between collections within one website. It is not a cross-website transfer tool. The current source does not establish a single automatic cross-website operation, so use a reviewed recreation process or request an administrator-assisted transfer with a documented inventory.

Prepare a transfer inventory

You need permission to read the source website and write to the destination. Removing source pages also requires source write permission and specific approval. If using an assistant, begin with read-only access and authorize destination writes only after reviewing the plan.

Record the exact website domains, source page IDs, languages, public URLs, child pages, and intended destination URLs. Include templates, forms, collection memberships, shared sections, media, redirects, and internal links. Obtain approval for the selected inventory, especially if several pages or translations are involved. Do not include passwords, client records, or access tokens in the inventory.

Recreate and review

1. Inspect the source pages and destination settings. Decide whether the destination needs ordinary pages, a sequential collection, or a dated collection. A source collection's relative slugs cannot be treated as complete destination URLs.
2. Create the destination structure using Collections and Add Page. Keep content requiring protection on a suitably private destination. MCP create_page defaults to direct-link availability, which does not provide confidentiality. Do not briefly expose sensitive content during creation.
3. Rebuild native sections in managed design, preserving the real header. For custom design, copy only supported source after checking destination support; it does not become visually editable native content. Resolve template and form dependencies against the destination website before saving.
4. Copy approved text and media. Check image ownership and delivery availability rather than assuming a source media reference becomes destination-owned. Do not remove source media that the destination still uses.
5. Replace internal page references with the destination pages' identities. A source /@p/ reference can otherwise identify the wrong website's page. Review links in buttons, body copy, navigation, shared content, and translations. Test anchors as well as page links.
6. Save and inspect every destination page at its normal URL. Compare its text, images, access settings, collection position, and mobile layout against the inventory. Keep an old-to-new URL table for external bookmarks and inbound links.

Complete a move safely

Request separate approval for source redirects, disabling, or deletion. Where appropriate, retain the original as a redirect to the verified destination instead of deleting it. Never promise that moving content automatically updates external links or redirects.

If a partial operation fails, inspect what already exists before retrying. Do not repeat creation blindly or run a bulk delete to tidy up. See assistant connections, pages and navigation, and recovery.