This page explains how to move CelesteCS Reporting for Confluence from Confluence Data Center to Confluence Cloud, what is migrated automatically and which limitations to check after the migration.
Before you start
CelesteCS Reporting does not store any data of its own: there are no app settings and no app database tables to migrate. Everything a report needs lives in the page content itself, in the macros and their parameters. When you migrate a space with the Confluence Cloud Migration Assistant, the Reporting macros are migrated together with the pages.
The Data Center and Cloud versions of the app use the same app key and the same macro keys, so Confluence Cloud recognizes the migrated macros as CelesteCS Reporting macros.
Migration steps
- Install CelesteCS Reporting for Confluence Cloud on your Cloud site from the Atlassian Marketplace. Install it before you open the migrated pages, otherwise Confluence shows the macros as unknown.
- Migrate your spaces with the Confluence Cloud Migration Assistant as usual. No app data migration is required for CelesteCS Reporting.
- Open several pages with reports and check them against the limitations below.
What is migrated automatically
- All seven macros: Reporting Table View, Reporting Table Item, Reporting List View, Reporting List Item, Reporting Confluence Data Provider, Reporting Jira Data Provider and Reporting Json Data Provider.
- All macro parameters, formulas, filters, sorting, formatting and footer aggregates.
- Json data stored in attachments, including attachments on another page referenced by the 'page' parameter of Reporting Json Data Provider (written as 'SPACEKEY:Page title').
Things to check after the migration
| Area | What changes in Cloud | What to do |
|---|---|---|
| Jira data | In Data Center the 'source' parameter of Reporting Jira Data Provider names an Application Link. In Cloud the app always reads Jira on the same Cloud site, and the 'source' parameter is ignored. | Migrate your Jira to the same Cloud site as Confluence. If your Jira stays in Data Center or moves to another site, Jira reports return no data. |
| Search index after migration | Reports built with Reporting Confluence Data Provider use Confluence search (CQL). Right after the migration, Confluence Cloud may not have added the migrated pages to its search index yet, so these reports can show "No data." for some time, while reports based on Jira or Json data already work. The same applies to a Json data attachment on another page, which is found by search. | Wait until Confluence Cloud indexes the migrated pages. To speed it up for specific pages, open the pages your reports query and publish them again without changes (Edit, then Update); each published page is added to the search index within a few minutes. |
| Page IDs in CQL queries | Pages get new IDs when they are migrated. A Reporting Confluence Data Provider query that uses a page ID, for example 'ancestor = 123456' or 'id = 123456', points to a wrong or missing page after the migration. | Replace page IDs with the new IDs, or rewrite the queries to use space keys, titles or labels, which are kept by the migration. |
| JQL functions | Reports that use CelesteCS JQL Extensions functions in their JQL need CelesteCS JQL Extensions for Jira Cloud. Three functions are available in Data Center only: 'jqlxIssuesWithAttachmentCountGreaterThan', 'jqlxIssuesWithLinksOfTypes' and 'jqlxFlattenedTwoLevelTree'. | Install CelesteCS JQL Extensions for Jira Cloud and replace the Data Center only functions. |
| Load macro dynamically | The Data Center 'load-macro-dynamically' parameter is not available in Cloud. Reports are always rendered with the page. | Nothing, the parameter is ignored. |
If a migrated report does not look as it did in Data Center, please contact