Space blueprints and "Create from template" after migrating to Cloud

Checked against Atlassian's documentation and issue tracker on 3 November 2026. Written by the maker of Spacewright, a Confluence Cloud app. We say where the app helps and where it does not.

Three things called "template"

What the migration assistant moves

So after the move, a space's own page templates and your global page templates should be there. Blueprints are not, and Cloud has no place for a custom space blueprint (see rebuilding standard spaces).

The "Create from template" bug: CONFCLOUD-85028

The Create from template macro puts a button on a page that creates a new page from a chosen template. Atlassian's documentation says it can point at "a blueprint or a user-created template".

What happened first (fixed)

CONFCLOUD-84407: after a migration with the assistant, buttons that used built-in templates such as Share a link showed an error that the original template had been deleted. The workaround was to edit the macro, select the right template and publish. The ticket is Closed, Fixed, resolved on 4 August 2026.

What is still open

CONFCLOUD-85028 reports that, even with that fix, spaces migrated with the assistant (version 3.14.0 and later) keep the old Data Center blueprint ID in built-in blueprint macros such as Create from template and Content Report Table. According to the ticket:

• Clicking the button creates repeated drafts without opening the editor.
• Editing the macro shows an empty template list, or the message "The original template has been deleted. Select a new template for the Create From Template macro."
• The expected result is that migration removes or remaps the old ID so the built-in template opens.
• The ticket says: "There is no viable workaround available at this time."

Status on 3 November 2026: Bug, Gathering Impact, unresolved, priority Low, 1 vote, 3 watchers; created 4 September 2026; component Migrations - Space - Import. Check the ticket for the current status.

What you can do now

1. Vote for and watch CONFCLOUD-85028 if it affects you, and report your case to Atlassian Support.
2. Find the affected pages in your test migration. In CQL, the macro field finds content that contains a given macro, for example macro = "create-from-template" and space = "KEY". Click each button once on the test site.
3. Tell people before cut-over which buttons may not work, and where the template now lives.
4. Where a button must work now, one option is to recreate the template as a page template you own (in the space or global) and point a new Create from template button at it: the macro's template list offers global templates and the current space's templates. This replaces the button rather than repairing the migrated macro, and we have not tested it on a site affected by the bug. Atlassian Support can advise on your case.

Rebuilding standard spaces in Cloud

If teams used space blueprints, or a template space, to start every project or client space the same way, these are the native options in Cloud:

• Built-in starting points. When you create a space, Cloud asks for a purpose: Collaboration, Knowledge base or Custom. You cannot add your own space to that choice; the request for that, CONFCLOUD-4538, was Under Consideration with 657 votes on 3 November 2026.
• Page templates with variables, per space or global, for pages people create again and again (space templates explained).
• A template space you copy: create the new space and duplicate the template space's page tree into it (a space for every client or project). The template space's own page templates do not come along that way.

Where Spacewright helps

Spacewright, our app, lets a space admin mark any Cloud space as a template with variables such as {{client}} or {{project}}. People create a new space from it with a short form, and Spacewright copies the whole space and fills in the values. For template buttons this means:

• The space's page templates come along (the option is ticked by default), with values filled into their name and content and links switched to the new space.
• "Create from template" buttons that point at one of the template space's own page templates are switched to that template's copy in the new space.
• Buttons that point at a global template or another space's template are left as they are and listed in the report under Links that could not be switched. A button that points at a global template should keep working, because global templates are available in every space.

So a practical routine after migration: build one template space, give it page templates of its own, point its buttons at those templates, and create new spaces from it.

Where it does not help

• It does not repair migrated spaces. Spacewright changes only the copies it makes; it never edits the source space.
• It does not fix CONFCLOUD-85028. It does not change blueprint references, so a button broken by that bug is still broken in a copy. Point the button at a page template first.
• It copies page templates, not blueprints, and it does not move anything from Data Center. Use Atlassian's migration assistant for that.
• Comments, page history, whiteboards and databases are not copied. Full list: Limits and known gaps; templates: Templates and variables.

Sources

• Bug: CONFCLOUD-85028, built-in blueprint macros keep the old blueprint ID after migration (Gathering Impact, Low, 1 vote on 3 Nov 2026)
• Bug: CONFCLOUD-84407 'Create from template' macros don't point to correct builtin blueprint template after migration (Closed, Fixed, 4 Aug 2026)
• Suggestion: MIG-1675 Consider making the Confluence Assistant migrating Blueprints (Gathering Interest)
• Atlassian: What migrates with the Confluence Cloud Migration Assistant
• Atlassian: Insert the Create from template macro (Confluence Cloud)
• Atlassian (Data Center 8.4 documentation): Create a Space From a Template (space blueprints)
• Atlassian Developer: Space Blueprint module (apps adding space blueprints in Data Center)
• Atlassian: Create a space (Confluence Cloud space purposes)
• Atlassian: Create a template (Confluence Cloud page templates)
• Atlassian Developer: CQL fields (the macro and space fields)
• Feature request: CONFCLOUD-4538 Creating a space template (Under Consideration, 657 votes on 3 Nov 2026)