Migrating Gliffy diagrams from Data Center to Cloud

Gliffy for Confluence is available for Confluence Data Center and Confluence Cloud.

Since Gliffy diagrams are stored as Confluence attachments on the page where they were created, your diagrams will be migrated even if you set the Gliffy app to "not needed" in the CCMA (Confluence Cloud Migration Assistant). However, for your diagrams to work correctly in the Cloud, the Gliffy app needs to run some post-migration functions on each diagram. This requires that the Gliffy app is set to "is needed" in the Cloud in the CCMA and that the Gliffy app has permission to access all pages that contain Gliffy diagrams. The best way to ensure a successful migration of all your Gliffy diagrams is to follow the instructions in this article.

If you would like details on how Gliffy diagrams are saved in Confluence, see Gliffy diagrams on the Confluence attachments page.

Prerequisites

Before you start the migration to the Cloud, remove any restrictions on space permissions and all restrictions on your Confluence Data Center pages or blogposts that contain Gliffy diagrams (Source instance). After the migration is complete, you can restore those permissions and restrictions on your Cloud (target) instance. If you fail to remove restrictions before the migration, the Gliffy app will not run the post-migration functions on the diagrams in pages and blogposts that have permissions and restrictions set.

This article provides information on how to View a list of Restricted pages in a space.

Migrate Gliffy diagrams

Follow these steps:

  1. Verify that your source and target Confluence instances have the Gliffy for Confluence plugin installed. The source must be using Gliffy version 9.3.2 or later. If an earlier version is used, follow the instructions in Updating the Gliffy for Confluence plugin.

  2. Use the Confluence Cloud Migration Assistant to migrate the diagrams. To ensure that diagrams are migrated, specify the option to migrate attachments. For detailed instructions, go to the Atlassian website and see Use Confluence Cloud Migration Assistant to migrate.

    You can migrate all your Confluence spaces at once or, just some of the spaces in batches.
    To migrate your spaces in batches, set the Gliffy App in the Confluence Cloud Migration Assistant to not needed, except for the last batch. For the last batch, set the Confluence Cloud Migration Assistant to Gliffy is needed.

  3. If a link gets broken, manually edit the Gliffy diagram that includes the link and update the link to point to the new page.

Linked shapes are identified with a link icon in the lower-right corner, and linked text is identified with blue underlining as shown in the following image. For instructions about updating links, see Linking objects and diagrams or Linking text.

Post-migration functions

If you met the prerequisites before the migration, the Gliffy app automatically runs functions after the migration to support the usability of the migrated diagrams.

The app runs the following post-migration functions:

  • Migrates custom shape libraries.

  • Re-indexes diagrams to support search functionality.

  • Ensures that linked diagram macros function properly so that diagrams display on the Confluence page.

If the Gliffy app is unable to run the functions, you must manually run the functions on each diagram after the migration is completed. You cannot run post-migration functions in bulk or automate them.

You would have to manually:

  • Re-create your custom shape libraries.

  • Open and save your diagrams in the Gliffy editor (to build the search index).

  • Fix broken linked diagram macros. Open the diagram in the Gliffy editor and save it to restore proper display on the Confluence page.