Migrate from draw.io for Confluence
If your site already runs draw.io for Confluence, its diagrams can be converted into Capable diagrams without anybody redrawing anything. The source is the same draw.io XML, so nothing is lost in translation.
The migration is run by an administrator, it can be tried as a dry run first, and it does not delete anything.
#When this applies
Moving from draw.io for Confluence to Capable Diagrams.
Consolidating onto one diagram app across a site.
Evaluating how much work a move would be, using a dry run.
#How it works
Step | What happens |
|---|---|
Scan | The migration finds draw.io macros across the spaces you select. |
Dry run | Everything is checked and reported, and nothing is written. |
Migrate | Diagram source is read and stored as Capable diagrams, and macros are updated. |
Review | A results view shows what succeeded, what failed and why. |
Re-run | Failures can be re-run without touching what already succeeded. |
Start with one space. A dry run on a single space gives you a realistic failure rate in a few minutes, and the results view explains every failure individually.
#A few things that catch people out
Nothing is deleted. The original macros and attachments remain until you decide to remove them.
Run a dry run first, on one space. It costs nothing and tells you what the real run will do.
Diagrams stored as PNG or SVG exports migrate too, because the XML travels inside the image.
#Related
Nothing is deleted. Try a dry run.
