Migrate from Macro Pack for Confluence (Warsaw Dynamics)

View as Markdown
Open in ChatGPT Open in Claude

Many teams moving off Macro Pack as a single entry point for Diagrams, Markdown, and API docs. This release adds a migration path for Macro Pack instances where the source content was pasted directly into the macro, converting them to the equivalent Capable macros while preserving the underlying content.

#Supported Macros

We support the following macros to be migrated (from text input):

  • drawio - Draw.io XML stored as diagram custom content

  • bpmn - BPMN XML stored as diagram custom content

  • excalidraw - Excalidraw JSON stored as diagram custom content

  • mermaid - Mermaid source stored as diagram

  • plantuml - PlantUML source stored as diagram

  • wavedrom - WaveDrom JSON stored as diagram custom content

  • html - HTML passed directly to the Capable HTML macro

  • latex - Equation text migrated

  • code - Source migrated with auto language detection, line numbers, and line wrapping enabled

  • markdown - Markdown body stored in custom content and linked from the Capable Markdown macro

  • swagger - OpenAPI / Swagger spec text passed to the Capable Swagger macro

#Limitations and known issues

Macro Pack macros that load content from non-text sources are left unchanged in this release:

  • URLs

  • Page attachments

  • GitHub / GitLab / Bitbucket repositories

  • Other external or dynamic sources

These are reported as unsupported in migration results and will be picked up in a future migration pass.

#Input types not supported

The following Macro Pack inputs are not migrated, even when pasted as text:

  • json

  • csv

  • asciidoc

  • Any other input value not listed in the supported table above

#Legacy macros

Individual legacy macros remain detected only and cannot be selected for migration, but we intend to implement these at a later date - please get in touch if you have other macros you would like to migrate.

Get in touch ↗