---
title: "Migration of Reporting Data Center to Cloud"
canonical: "https://support.appfire.com/space/RFC/477334828/Migration%20of%20Reporting%20Data%20Center%20to%20Cloud"
format: markdown
---
> Macro (aura-html)
> ❌ Due to the architectural differences between Confluence Data Center and Confluence Cloud, Reporting Data Center **is not auto-migratable** to Reporting Cloud.
## Feature Differences between Reporting Data Center and Reporting Cloud
| **Area of difference** | **Reporting Data Center** | **Reporting Cloud** |
| --- | --- | --- |
| **How it obtains data** | Uses data suppliers and relies on direct access to the Confluence on-prem database. | Uses CQL (Confluence Query Language) and relies on Confluence APIs.
**Limitation**: Currently, Confluence API has a memory cap of 10MB. |
| **Macros structure** | There are 39 macros, categorized into four groups: display, query, filtering, and sorting.
You can nest and build infinite combinations of macros and suppliers. | Due to the Confluence Cloud restriction on nesting macros ([CONFCLOUD-68323](https://jira.atlassian.com/browse/CONFCLOUD-68323?__hstc=72543820.fc01f7207c5560bbad56602855ff793c.1626071106671.1630478299199.1630483183523.89&__hssc=72543820.18.1630483183523&__hsfp=4083207849)), we redesigned the entire user experience.
A single unified macro lets you structure your reports using a report builder and report blocks, wrapping them in one of the predefined formats: table, list, or paragraphs. |
| **Time to value** | It takes a considerable amount of time and expertise to build sophisticated reports and dashboards. You need to learn and understand dozens of different macros and suppliers and how to connect them. | The app is geared with templates that let you import and export your recipes. Our team curated different scenarios in recipe format. You can easily copy these recipes from [here](https://appfire.atlassian.net/wiki/spaces/RFC/pages/477333214).
For advanced reporting, having a basic understanding of writing a CQL syntax helps you get more value quicker. We have documentation and tutorials that can help you grasp the main concepts and build your custom reports/dashboards. |
## Minimal auto-migration
Limited migration is only supported for content that is within [Report Block](https://appfire.atlassian.net/wiki/spaces/REPS/pages/472914906) macros. After migration to Confluence Cloud, to maintain the layout of the migrated pages, the Report Block macros are rendered as info panels called `Reporting has moved into Confluence Cloud`.
You can click **View data** in the info panel to display the structure of the original report. You can view details of the macros that were used as well as the respective macro parameters.
> ❌ It is highly recommended that you back up these macros and parameters before switching to the new [Confluence editor](https://support.atlassian.com/confluence-cloud/docs/convert-pages-to-the-new-editor/) as most of this data can be lost.
## Recreate your reports in cloud
Because the report structures differ between the Reporting Data Center and Reporting Cloud, you must manually recreate your reports in cloud.