Migrate draw.io from Confluence DC to Zero Egress Cloud

draw.io 21 Aug 2025

Share:

You can now migrate from draw.io for Confluence Data Center to the Zero Egress draw.io app for Atlassian’s Confluence Cloud. The Zero Egress draw.io app is fully client-side and Forge-only. This enforces data residency and isolation - there is no external data egress. Diagram data is stored within the Confluence page content on Atlassian’s infrastructure and in the user’s browser as they edit diagrams and pages in that Confluence Cloud instance.
Flowchart summary for migrating from draw.io in Confluence DC to draw.io Zero Egress for Confluence Cloud

Open this flowchart in draw.io

Zero egress gives you complete control over sensitive documentation, where diagram data is kept fully within your infrastructure allowing no transmission to external servers.

The Zero Egress draw.io app has the advanced configuration option lockdown enabled - this ensures diagram data passes only between the users’ browser and your Confluence Cloud instance where it is stored.

Tip: The Zero Egress draw.io app is qualified for Runs on Atlassian and is Cloud Fortified. This version of draw.io will work with Atlassian’s Isolated Cloud and Government Cloud, both expected to release to customers within the next year.

Migrating draw.io diagrams in Confluence

When new pages are made when migrating a Confluence instance, new page IDs are assigned. All linked content in a diagram must be identified beforehand in the source DC instance and adjusted afterwards to use the new PageIDs in the target Cloud instance. This affects diagrams containing links to content within the instance, and diagrams on one Confluence page that have been embedded on another page.

Migrating from Gliffy DC to draw.io Zero Egress in Cloud

There is no Gliffy conversion in the Zero Egress draw.io app.

Mass convert all Gliffy diagrams to be draw.io diagrams first in your Confluence DC source instance.
Go to the Gliffy Import tab in the draw.io add-on configuration in Confluence server to convert all of your diagrams at once

Once you have confirmed this conversion was successful, then you can migrate to draw.io Zero Egress in Confluence Cloud.

Migrate draw.io from Confluence DC to Cloud

This process is the same if you migrate from the standard draw.io app

  1. Ensure you have all administrator permissions for both instances (view/add attachments/pages/spaces).
    Check that the space permissions in your Cloud instance are set to: all admins can write and all users can read
  2. Re-index the draw.io Diagrams index in your source DC instance to ensure all page attachments are correctly indexed via the draw.io app Configuration before you start the migration.
    In the draw.io configuration, run a re-index on your Confluence Cloud instance to make sure all diagram links and embedded diagrams are referred to correctly
  3. Export the draw.io PageIDs from your source DC instance via the draw.io app Configuration and download this mapping file to your local device. Keep this file - it will be used after you have migrated, and for troubleshooting.
    To make sure links in diagrams continue to work, export the page IDs from Confluence to correctly migrate
  4. Migrate your source DC instance to your target Cloud instance.
     
  5. Now, import the PageIDs file you previously saved into your new target Confluence Cloud instance via the draw.io app Configuration. Make sure you save this import log for troubleshooting purposes.
    • If you are limited to short sessions that can time out, enable the Cache page IDs mapping and Remember imported pages options before starting the import.
      Cache the PageID import in your browser if short sessions cause this process to time out
    • Run the import again from this page making sure the two options remain checked, and the import will continue where it was interrupted. Note that the data is cached in the browser - use the same machine and same browser to resume.
       
  6. Finally, re-index your new Confluence Cloud target instance to double-check page attachments are all correctly indexed after migration.

Detailed steps for migrating draw.io between Confluence instances

Follow us on GitHub, Twitter, Facebook.

Share: