Cloud Migration Path
Blueprint Creator is now ready for the Cloud by migrating your Blueprint Data into the Properties - Templates, Metadata & Databases App.
Please note that this migration hast just the Blueprint creator placeholder fields in scope. It is not migrating a template with macros or other content you have put into your templates. This is part of the migration scope from the Confluence Migration Assistant from Atlassian.
Prepare the fundamental steps for the migration
To make sure you setup your environment the best way possible please follow these steps:
Install the App Properties - Templates, Metadata & Databases on your Confluence Cloud instance you want to migrate the Blueprint Creator data to.
Update your Blueprint Creator App version in your Confluence Data Center instance to the minimum version of 3.8.0 - this is required to have access to the migration preparation screen in the Blueprint Creator App.
Ensure that you can connect your Confluence Data Center instance with the Confluence Cloud instance through the Confluence Migration Assistant from Atlassian.
Identify and select your data set for the cloud migration
The Blueprint Creator offers a new overview in the Confluence Administration. In this Overview „Cloud Migration: Blueprint Creator to Properties“ you can set what scope of Blueprint data you want to select for the migration into the app Properties - Templates, Metadata & Databases.
First of all select the Global Page Blueprints you want to migrate.
Secondly select the Space-specific Page Blueprints you want to migrate. If you have multiple Page Blueprints in a Space you can select which Blueprints should be considered.
On the right side you have to select „Save Selection“ - this will save a json file which will automatically be available for the Confluence Migration Assistant from Atlassian.
Please note that this migration hast just the Blueprint creator placeholder fields in scope. It is not migrating a template with macros or other content you have put into your templates. This is part of the migration scope from the Confluence Migration Assistant from Atlassian.
Run the migration with the Confluence Migration Assistant (CMA)
When running the Confluence Migration Assistant (CMA) the CMA will provide a screen to select which app data should be part of the migration into your Confluence Cloud. You will find the Blueprint Creator data available to be selected for the migration into the Properties - Templates, Metadata & Databases App. This requires the step „Identify and select your data set for the cloud migration“ in this documentation to be finished with the result of a saved selection. Please read the previous chapter to ensure readiness for the migration path process.
In the case of not being able to use the Atlassian Migration Assistant (CMA) for the migration to your cloud instance the Blueprint Creator still offers a solution to download a json based file of your setup and import that manually into the Properties - Templates, Metadata & Databases App.
Manual steps to consider after the migration
After the migration has been finished please consider these steps for quality assurance:
Check if all selected Blueprints data configurations are available as Property Groups
Review if edit permissions needs to be set for specific Property Groups - the recommendation is to set permissions for compliance related and sensitive property groups (concept a permission scheme with the client)
Assign Property Groups to global templates or space templates by placing the property group macro into the templates according to the clients definition and needs in Confluence Cloud
Migration limitations
Due to technical limitations in Confluence Cloud these data are not in scope of the migration data set:
Space Blueprints for creating standardized space structures
Pagetree Blueprints for creating multiple standardized pages at once as a structure
Prefix & Suffix automated title functionality in Blueprints
Auto-title numbering functionality in Blueprints
Page Blueprints from Confluence Archived Spaces will be ignored and are not selectable
Other Topics to be mentioned
The Blueprint Creator is able to set a Blueprint Template to be used for Blogs. This is not possible in Confluence Cloud. Still the placeholder configuration for these Blueprints will be available as Property Group in the Properties - Templates, Metadata & Databases App.
Confluence page template metadata like e.g. labels are not part of the migration scope from the Blueprint Creator to Properties - Templates, Metadata & Databases App.