draw.io 3.x for Confluence Cloud in pages using the legacy page editor.

[davidjgraph]

draw.io 3.x and onwards uses Atlassian's Forge platform, the replacement integration platform to connect.

After releasing on Forge we discovered that Forge macros do not work on legacy pages. Instances that have migrated from DC in the past, or intend to, are likely to have a significant number of legacy editor pages.

The legacy editor is deprecated in cloud, so most pages will automatically be migrated in early 2026.

There are three possible states your instance might be in regarding this issue:

1. You have legacy pages and have updated to draw.io 3.x or later.

In this case, if you have legacy pages then the only option is to update the page to the new editor.

2. You have legacy pages and are running draw.io 2.2 or earlier.

In this case do not update draw.io while you have legacy editor pages. The forge version has a smaller editor area, so the connect version is better, regardless. We won't remove the connect version, probably for some years.

3. You are running on data centre and intend to migrate to cloud.

Discuss with Atlassian support whether it's possible to migrate legacy page editors.

Obviously, if https://ecosystem.atlassian.net/browse/FRGE-1841 were resolved, this would resolve the problem. However, with the date of the legacy editor EOL being close, I think this is unlikely to happen unless the problem stopped a huge number of DC migrations going to cloud because of it.

A secondary issue that is coming up is that migrating the page(s) to the new editor is resulting in the draw.io viewer displaying at an incorrectly small size.

Also please read:

https://ecosystem.atlassian.net/browse/FRGE-1733
https://jira.atlassian.com/browse/CONFCLOUD-80208
https://ecosystem.atlassian.net/browse/FRGE-1992

[davidjgraph]

FAQ

Why did draw.io move from Connect to Forge now?

As part of upcoming changes in the Atlassian Marketplace, all apps must move to Forge or face a staged revenue penalty (4% at year-end, rising to 8% six months later).

Due to engineering resourcing constraints in December 2025, we had to migrate by the start of October to provide us enough time to deal with problems prior to December 2025.