Migrating Table Filter, Charts & Spreadsheets to Confluence Cloud: What you need to know

[#1]

With Atlassian's announcement of Data Center end of life by 2029, many Confluence administrators are preparing for migration to Cloud. If you're using Table Filter, Charts & Spreadsheets for Confluence, this guide will help you understand what to expect during and after the transition.

How migration works

The good news: migration is straightforward. Table Filter, Charts & Spreadsheets has an "Install-only" status in the Confluence Cloud Migration Assistant (CCMA). Simply install the Cloud version through CCMA, and your content migrates automatically with your Confluence pages. All macros, configurations, and data transfer seamlessly - no data loss expected.

For paying Data Center customers, you're eligible for a free Cloud Migration Trial that matches your remaining subscription term, including access to the app.

Five key differences to prepare for

While we maintain 99% feature parity between versions, Confluence Cloud's architecture introduces some changes:

1. The Table Toolbox macro

This is the most significant change you'll encounter. Cloud's editor doesn't support nesting bodied macros the way Data Center did. The Table Toolbox macro solves this limitation, allowing you to combine Table Filter, Table Transformer, Pivot Table, Chart from Table, and Table Excerpt in one place.

Your existing nested macros will continue working in the legacy editor after migration - no need to rebuild pages immediately. However, new macro combinations must use Table Toolbox.

2. Table Filter adjustments

Two minor changes affect our most popular macro. First, live filtration isn't available in Cloud due to editor limitations. You'll need to enable filters manually by adding the Table Filter macro in edit mode or accessing it through the Apps menu in view mode.

Second, the "show filter" option in page edit mode is unavailable. You can preview table changes in edit mode, but filtered views only appear after saving.

3. No app buttons in editor panel

Cloud's limitations removed our action buttons from the editor panel. Instead, use the slash command - type "/" followed by the macro name (e.g., "/table filter"). Since all our macros include "TABLE" in their names, typing that gives you quick access to the full list.

4. Third-party app compatibility

Interactions with some apps are limited in Cloud. For third-party macros to work with our app, they must support static data rendering. We're working with vendors like Scroll PDF/Word Exporter and Comala Document Management to resolve compatibility issues and will share updates as they become available.

5. Some Confluence features don't work inside macros

Currently, you cannot create Jira issues from highlighted text, add inline comments, or navigate to anchors and heading links placed inside our macros in view mode. We'll notify customers of any changes to these limitations.

Pro tips for a smooth transition

Before migrating, test your migration in a sandbox environment. Pay special attention to pages that already load slowly in Data Center - they'll likely perform worse in Cloud due to Atlassian's page size limits. Consider splitting large pages or simplifying complex macro combinations.

Also, review your macro setups. Sometimes multiple macros can be consolidated into a single SQL query or by using native app features instead of combining third-party solutions.

If you encounter performance issues or loading errors after migration, contact Atlassian Support. Server request limits sometimes affect pages with many macros.

Authorization reminder

If you used CSV/JSON from Table with URL authorization in Data Center, you'll need to re-enter credentials after migration due to different encryption keys between platforms.

Looking ahead

We're actively migrating from Atlassian Connect to Forge to meet Atlassian's highest cloud standards. This transition will enhance data residency options and help you meet security and compliance requirements, all while maintaining the functionality you rely on.

We have also prepared a video and a blog post that contain all the necessary information for the end-users of the app. For detailed technical documentation, visit our migration guide. We're here to support you through this transition. If you encounter any issues not covered here, don't hesitate to contact our support team.