# draw.io for Confluence Capable recognises **3** macros from **draw.io Diagrams for Confluence**. 3 of them convert, and none are left behind. --- ## At a glance | **Macro** | **Becomes** | **Support** | | ------------------------------------ | ------------------------- | ----------- | | draw.io Diagram | Capable Diagram | Converted | | draw.io Board | Capable Diagram | Converted | | Embed draw.io Diagrams (second pass) | Capable Diagram Reference | Converted | --- ## What each one does ### draw.io Diagram ![A Confluence editor showing the same circular business model diagram twice, first inside a macro labelled Draw.io Diagram and below it inside a macro labelled Capable Diagram.](https://help.gocapable.com/images/63f2d6b1-327a-441b-a88e-de895df3c8dd.webp) The source macro and the Capable macro it becomes, with the drawing carried across untouched. | **Migrates to** | Capable Diagram | | --------------- | --------------- | | **Support** | Converted | For each draw.io macro on the page, Capable recovers the diagram's source drawing and writes it into a new Capable diagram stored on the same page, then replaces the macro. The source is looked for in order: the copy draw.io keeps alongside the macro, then the page attachment (read as raw bytes so drawings saved inside PNG or SVG previews are recovered correctly), then a sibling preview image on the same page. If the diagram lives on a different page, Capable follows the macro's own page reference and, failing that, searches the site for a single page holding an attachment with that name. Macros buried inside Data Center import wrappers are found and converted too. **What survives the move** * The complete draw.io drawing, so shapes, layers, links inside the diagram and multi-tab files all survive * The diagram title, taken from the attachment name * A link to the old draw.io preview image, used for catalogue thumbnails and exports until Capable generates its own * Full version history with each version's original author and edit date, when the migration behaviour version is 1.1.0 or higher **What does not come across** * The macro's authored width and height, every migrated diagram is created at a standard height * The draw.io border option * The selected tab on a single diagram macro that pointed at a specific page of a multi-tab file **Options that affect this one** * Classic draw.io layout (beta) * Keep source macros * Migration behaviour version 1.1.0 or higher for version history ⚠️ **Worth knowing before you run it.** * Verification substitutes a stand-in drawing and never downloads the real file, so a clean dry run does not prove these will migrate. * A macro that was never saved, or whose attachment was deleted, is reported as unsupported (nothing to migrate). Genuine read failures, including permission-blocked pages, are reported as failed so they get investigated. * When a macro pins a specific revision, that historical snapshot is migrated rather than the current drawing. When no revision is pinned, the live copy draw.io keeps wins over the attachment file. * Leftover Gliffy files from an old bulk import are deliberately skipped in favour of the converted draw.io file. If only the Gliffy file remains, the macro is left alone, this migrator does not convert Gliffy. * A diagram still called "Untitled Diagram" is never searched for site-wide, because the name is too generic to trust. * If the same diagram name exists on several pages, Capable refuses to guess and reports the ambiguity with the candidate pages named. ### draw.io Board | **Migrates to** | Capable Diagram | | --------------- | --------------- | | **Support** | Converted | Works the same way as the Diagram migrator: the board's drawing is recovered and written into a new Capable diagram on the page, and the macro is replaced. Version history and original authorship are supported at behaviour version 1.1.0 and above. **What survives the move** * The board drawing * The board title * Version history and authorship at behaviour version 1.1.0 or higher **What does not come across** * Macro sizing ⚠️ **Worth knowing before you run it.** * Materially less capable than the Diagram migrator despite carrying the same support badge. Boards are not found inside Data Center import wrappers, do not use the site-wide recovery search, do not honour a pinned revision, do not carry a preview-image link, and do not run the leftover-file sweep. A board macro inside an import wrapper, or one whose page reference no longer resolves, will fail where the equivalent diagram macro succeeds. ### Embed draw.io Diagrams (second pass) | **Migrates to** | Capable Diagram Reference | | --------------- | ------------------------- | | **Support** | Converted | This runs only after every other selected migrator has finished all its pages and those pages have been saved, because each embed has to point at a diagram another migrator created earlier in the same run. For each embed, Capable looks for the already-migrated Capable diagram on the source page, then for a converted loose file on that page, and if neither exists it converts the source diagram on demand and points the reference at it. On-demand conversions are counted and logged as their own successes. **What survives the move** * The embed's height * The draw.io border option, as "Show Border" * The selected tab of a multi-tab file ⚠️ **Worth knowing before you run it.** * Running this migrator alone only works if the source diagrams were already migrated in an earlier run. * Embeds pointing at a diagram hosted outside this Confluence site are reported as unsupported and left as they are. Detection is a judgement call, so an unusual but genuinely local embed can be skipped. * On-demand source conversion is skipped in verification, so a dry run over-reports embed failures that the real run would resolve. --- ## Related [draw.io Diagrams (Zero Egress)3 macros recognised.](https://help.gocapable.com/migration/draw-io-for-confluence-zero-egress.html) [PlantUML (Avono)3 macros recognised.](https://help.gocapable.com/migration/plantuml-for-confluence-avono-dc.html) [DiagramsThe rest of the diagrams migrators.](https://help.gocapable.com/migration/diagrams.html) [TroubleshootingWhen a macro fails or is skipped.](https://help.gocapable.com/migration/troubleshooting.html) --- _Find the drawing first. Everything else follows._