---
title: "Migration Path - Content Formatting Toolkit for Confluence"
canonical: "https://support.covectors.io/space/SAMM/551485441/Migration%20Path%20-%20Content%20Formatting%20Toolkit%20for%20Confluence"
format: markdown
---
> ℹ️ To plan your DC to Cloud Migration, read about our Content Formatting Toolkit Ascend program.
> ℹ️
> ℹ️ We offer a dedicated assessment within CFT DC to prepare your spaces and ensure a smooth migration without obstacles.
> ℹ️
> ℹ️ Read more here: [https://support.covectors.io/space/MH/1760362526/Content+Formatting+Toolkit+for+Confluence+-+Migration+Hub](https://support.covectors.io/space/MH/1760362526/Content+Formatting+Toolkit+for+Confluence+-+Migration+Hub)
Below is a step-by-step guide to migrate your Content Formatting Toolkit for Confluence app data to Confluence Cloud.
## Before you start, please read this checklist
- [ ] Read [this Atlassian article](https://confluence.atlassian.com/cloud/plan-your-cloud-migration-972349846.html) to plan your migration.
- [ ] Ensure you have the latest version (3.1.0 or higher) of Content Formatting Toolkit for Confluence for server/DC and the latest version of “Content Formatting Toolkit for Confluence Cloud” installed in Confluence Cloud.
- [ ] Confirm that Confluence users have valid email addresses matching their cloud accounts.
- [ ] Ideally, perform the migration with a user who has admin privileges on your Confluence Cloud site.
- [ ] Update the Confluence Cloud Migration Assistant to the latest version.
> ✅ **To proceed with the migration correctly, follow these steps in order:**
> ✅
> ✅ 1. Install or update to the latest Cloud version available on the Marketplace to enable API V2 for your apps.
> ✅ 2. Install or update to the latest Server/DC version (3.1.0 or higher) of Content Formatting Toolkit for Confluence on your Confluence instance.
> ✅ 3. Update your Confluence Cloud Migration Assistant to its latest version.
> ✅ 4. Run the migration.
## :warning: Content Formatting Toolkit for Confluence - Nested macros migration and new Confluence Cloud editor
We conducted an extensive study to enable macros based on nested body logic in Server/DC to function in Cloud, despite Atlassian's decision. (More details on Atlassian's decision can be found [in this Jira Ticket](https://jira.atlassian.com/browse/CONFCLOUD-68323)).
Unfortunately, Atlassian has determined that nested *rich body* macros are *not* supported in Confluence Cloud. This decision significantly impacts our core macros: SP Tabs, SP Vertical Nav, and SP Horizontal Nav.
Since version 1.0 of our Cloud App, we have released a version that allows users to utilize our macros within the new Confluence Cloud editor. We restructured our macros so that a macro can group child macros within its body, but these child macros are bodiless. We employ content parsing to display content within the related tab.
However, this solution still prevents our customers from migrating content containing our macros from their Server/DC pages to Cloud.
To facilitate app migration, Atlassian created a dual experience: Legacy content and new editor rendering.
In legacy mode, nested macros can function and display embedded content within a legacy macro. However, that content cannot be copied or reproduced on the page or other pages. This strategy allows Atlassian to provide at least a “read-only” experience for the nested content.
To support both users migrating from Server/DC and our current Cloud users, we implemented the following:
1. We released a Cloud version that distinguishes between Legacy content and the new Cloud editor. Macros supporting nested bodies (related to content migration from Server/DC pages) point to V1 of our API, while macros that do not support nested bodies (used in the new Confluence page editor) point to V2 of our API. **All macros for the new editor include "-cloud" in their IDs.**
2. V1 macros supporting legacy content are NOT BROWSABLE and can be injected by Cloud users into their pages.
## :info: Content Formatting Toolkit for Confluence VS Spectrum Formatting Advanced and migration process for both
It known that we have merged our App Spectrum Formatting Advanced into Content Formatting Toolkit for Confluence within version 3.0.0. SF Advanced have been archived and all its macros are now available when you install SF Macros in Confluence.
For the moment our migration process support original SF Macros only, and our team is currently working on making equivalent SF Advanced macros available in Cloud with their migration path.
All details on macros parity can be found [in this document.](https://vectors.atlassian.net/wiki/spaces/SAMM/pages/551452685)
## Running a migration of Content Formatting Toolkit for Confluence
### Step 1
Start by making sure that your Content Formatting Toolkit for Confluence App is tagged as needed in Cloud in order to trigger the right event once a space is migrated via the Migration Assistant.
Navigate to Confluence Administration and choose Migration Assistant. Choose the Assess your apps option and select our Content Formatting Toolkit for Confluence app to be needed in Cloud :
### Step 2
Select your Cloud site where your data will be migrated.
To do so:
- Enter the site from which you want to migrate data and select the cloud site which data will be migrated to
- Make sure the admin’s email address is the same on both cloud and server environment
- Check “Allow Atlassian” to access migrations data
- Confirm
Now that your pre-configuration is done, you can proceed to creating a new migration plan.
### Step 3
Navigate to home page and **create a new migration**.
You will be redirect to the interface to confirm your cloud site selection and will be asked to choose what to migrate as following:
- Select Migrate spaces to choose after what spaces to migrate
- Select the users policy.
Proceed to space select to migrate content from and migrate glossary data from as following:
After confirming the action, the migration assist will provide you with a list of checks and errors to fix before migration.
> ℹ️ We included Pre-Checks module to make sure user has run the scan on the select spaces via our Assistant as following:
> ℹ️
> ℹ️ 
You will get a recap of your migration before to run it: Details about your spaces, number of pages, what apps are impacted, etc.
ou simply need to run the migration. You will be redirected to the home page where you can select the migration that you just launched to follow its state.
Please note that app migration progress will take time before displaying the feedback.
Two types of feedback are handled based on Atlassian API:
| **Migration App data state** | |
| --- | --- |
| COMPLETE | Your data are successfully migrated after space content and users migration. |
| INCOMPLETE | Something happened that may have broken the migration.
Some common cases for migration data errors:
- Non existing users in cloud
- Space data not found during migration due to latencies within cloud instance or internet |