Your Gliffy Migration Options
You have two options for diagramming with Gliffy in Atlassian Cloud:
- Gliffy Diagrams for Confluence: Compatible with Commercial Cloud & Government Cloud
- Gliffy Diagrams | Zero Egress & Isolated Cloud-Ready: Compatible with Isolated Cloud & Commercial Cloud
In this video, we go over your options for migrating your diagrams with Gliffy in more detail.
What Our Partners Are Saying
Our customer just tested a Gliffy migration that went so fast, we had to double-check it actually worked. Gliffy used to take a few hours to migrate, but now they have it down to just minutes
Pre-Migration Checklist
Check Gliffy Versions
The source instance should be upgraded to:
- Version 12.2.0 for Confluence 9
- Version 13.1.0 for Confluence 10
Check Target Cloud Site URL
If you renamed your target Cloud site URL after installing the Gliffy Cloud app, you need to uninstall the Gliffy Cloud app and reinstall it before the migration.
Running Your Gliffy Migration
Make sure your source and target Confluence instances both have Gliffy installed. Upgrade the Gliffy app in Confluence Data Center (the source instance) to the latest version (at least 12.2.0 for Confluence 9 or 13.1.0 for Confluence 10). Older versions do not support migrations.
Then, use the Confluence Cloud Migration Assistant (CCMA) to migrate your diagrams.
- Select the option to migrate attachments.
- Set the Gliffy app to "is needed" in the Cloud.
Migration Tip
Migrating Your Spaces in Batches
You can migrate all your Confluence spaces at once, or you can complete your migration in batches.
To migrate your spaces in batches, set the Gliffy app in the CCMA to not needed, except for the last batch. For the last batch, set the CCMA to Gliffy is needed.
After Your Migration
These functions automatically run post-migration to support full diagram functionality.
| Gliffy Diagrams for Confluence | Gliffy Diagrams Zero Egress | |
| Re-index diagrams for search | ✅ | ✅ |
| Migrate custom shape libraries | ✅ | ❌* |
| Ensure linked diagram macros function properly | ✅ | ✅ |
*Custom shape libraries not available
What if the functions don't run after migration?
If the Gliffy app is unable to run the functions, you must manually run them on each diagram after the migration is completed. You cannot run these functions in bulk or automate them.
How to manually run post-migration functions:
Open and save each Gliffy diagram. This will build the search index and fix broken linked diagram macros to restore proper display on theConfluence page.
(Commercial Cloud Only) Re-create any custom shape libraries.
What to Expect Post-Migration
Moving to Cloud opens up exciting opportunities for your team to save time and collaborate more effectively. In this video, we'll explore a few of those opportunities to help you understand how Cloud unlocks your team's full potential.
Migrating Your Diagrams to Gliffy from Another Diagramming Tool?
If you're looking to switch to Gliffy when you move to Cloud, or if you use multiple diagramming tools and want to consolidate as you prepare to migrate, you don't need to lose access to all your hard work. Our draw.io to Gliffy bulk diagram converter is currently available in Confluence Data Center and allows you to convert all your draw.io diagrams to Gliffy diagrams in minutes.
Additional Resources for Your Migration
In this video, we cover:
- How to work with our support team if you need assistance during your migration.
- How to work with our preferred partners to ensure a smooth transition to Cloud.
You can also get more migration tips from our blog, Atlassian Migration to Cloud: A Gliffy Customer's Story.
Get Gliffy for Confluence Cloud
Gliffy Diagrams for Confluence Gliffy Diagrams | Zero Egress