---
title: "CFT | 1- Understand"
canonical: "https://support.covectors.io/space/MH/1760133124/CFT%20%7C%201-%20Understand"
format: markdown
---
## What’s the impact of cloud migration on CFT for Confluence

Confluence migration to the cloud occurs in three phases:

1. User migration
2. Spaces migration (pages and attachments)
3. App data migration (apps configured for the cloud send related data)

The Content Formatting Toolkit for Confluence includes formatting macros. Some macros store information in their parameters and the page body, while others require additional storage options like page context or database tables.

Cloud migration impacts our app on two levels:

1. During spaces migration, macros are pushed to the cloud as pages are created.
2. During app data migration, we send all related macros data to the cloud for correct display on pages.

App data migration **impacts** only macros **with** storage. Other macros remain unaffected, and rendering occurs directly in the cloud.

Below are the two groups of macros:

> ℹ️ View the full list of macro names and IDs in DC [https://vectors.atlassian.net/wiki/spaces/CFTFC/pages/1405943842](https://vectors.atlassian.net/wiki/spaces/CFTFC/pages/1405943842)

| **Macros NOT impacted by Migration** | **Macros impacted by Migration** |
| --- | --- |
| Tab Group + Tab Pane | Page Status |
| Horizontal Nav Group + Horizontal Nav Item | Progress Bar Advanced |
| Vertical Nav Group + Vertical Nav Item | Footnote |
| Progress Bar |  |
| Macro Panels |  |
| Pourcentage Progress Bar |  |
| Expander Container + Expander Box |  |
| Macro Button |  |
| Infobull |  |
| Notification |  |

## Key blockers that led us to develop CFT Ascend and our own migration assistant interface

Over the past two years, we identified several blockers affecting our app during cloud migration.

1. **Voluminous Confluence Instance**

We observed a significant number of incomplete migrations on large Confluence instances. To prepare data related to impact macros during migration (Page Status, Footnote, Progress Bar Advanced), we needed to run a [query provided by Atlassian](https://support.atlassian.com/confluence/kb/how-to-find-all-pages-and-spaces-that-use-a-specific-macro-via-sql/) to identify those macros in Confluence pages and gather the required data.

The time taken by this query to execute often blocks or interrupts the migration.

2. **Outdated macros in pages or broken macro parameters**

Our app primarily uses formatting macros. Outdated pages or macros that have not been updated may break during data migration or after the cloud migration due to missing or broken parameters.



> Macro (ui-button)




---

Need Help, want to plan your migration or you want to get more information about this program:  > Macro (ui-button)