Copy an entire Confluence space, attachments and labels intact
Copy a whole space or any page tree into a new or existing space, with attachments, labels and optional restrictions, internal links rewritten, and large spaces copied in resumable batches.
This app answers a request that has been open on Atlassian's public tracker for years:
CONFCLOUD-3191,
"Easily create a copy of an entire space", with 882 votes.
The gap
CONFCLOUD-3191 — "Easily create a copy of an entire space" — was opened in May 2005. It has 882 votes and is still Gathering Interest, twenty-one years later. The native option is copying one page tree at a time, which loses the space itself, and the manual workaround loses attachments or leaves every internal link pointing back at the space you were trying to leave behind.
What it does
Copy a whole space into a new space, or a page tree into an existing one.
Attachments (up to 25 MB each) and labels come with every page.
Internal links are rewritten: space keys and /spaces/KEY/ paths point at the copy.
Page restrictions copied on request, off by default.
Resumable batches: 20 pages per invocation through the Forge async queue, so a 4,000-page space finishes instead of timing out.
A failed page is recorded and the copy continues, with a per-page list of what did not make it.
Save any space as a template, then use it to create new spaces.
A copy in flight: the source space, the target, pages done against pages found, and the per-page list of anything that failed rather than a single red error.Space templates: any existing space saved as a blueprint, with the page count it will stamp out and what is included.Why the copy is permission-safe: the space is created as you and every source page is confirmed readable by you before it is copied, so the copy can never widen access.
Honest about its limits
Links written by page id (/pages/123456/) still point at the source page. Ids only exist after a page is created, so a link to a page that has not been copied yet cannot be rewritten.
Blog posts, comments and page history are not copied. The copy is the current version of each page.
Space permissions are not copied; the new space gets the creator's defaults. Page restrictions are a separate opt-in.
It copies pages, not Confluence's page-template objects. A space template here is a space used as a blueprint.
The one write path, honestly scoped: The app creates a space and pages, and uploads attachments and labels onto the pages it created. It never modifies a page in the source space.
Security & permissions
Built on Atlassian Forge: the app runs on Atlassian's own serverless platform inside your
tenant and stores its data in Forge storage.
It makes no external network calls. Every scope it requests, and why:
read:space:confluence
listing the spaces you can read, so only those are offered
No. The app runs on Atlassian Forge inside your own tenant with zero external egress,
which makes it eligible for Atlassian's Runs on Atlassian trust marker.
How is it billed?
Through the Atlassian Marketplace, on your existing Atlassian bill, priced per user like
any Cloud app. The listing has a free evaluation and the exact calculator for your tier.
