Migrate from Stratus Mermaid and PlantUML to Capable Diagrams in Confluence

To migrate from Stratus's Mermaid Diagrams for Confluence or PlantUML Diagrams for Confluence, a Confluence administrator opens the Migration tab in Capable, selects the Stratus apps and their macros, runs Perform verification, then Start migration. Each macro becomes a Capable diagram holding the same Mermaid or PlantUML source, so nothing is redrawn.

#Before you start

You need	Why
Confluence administrator rights	Only administrators can open the Migration tab.
A pilot space	A small first run shows you the real failure rate in minutes.
The browser tab left open	The migration runs in your browser and stops if you close the tab.
The Stratus apps still installed	Keep them until you have checked the migrated pages, so you can compare.

#Steps

In Confluence administration, open the app's settings page (Capable, or Capable Diagrams for the standalone app) and select the Migration tab.
Read Introduction and tick the confirmations, then go to Options. Leave Skip errors on.
In Select apps, choose Mermaid Diagrams for Confluence (Stratus), PlantUML Diagrams for Confluence (Stratus), or both.
In Select macros, choose Mermaid Diagram and PlantUML Diagram, and narrow the pages to your pilot space.
On Run, select Perform verification. It reads the pages and writes nothing. Read the results.
Select Start migration. When it finishes, select Download log and keep the file.

#What converts

Macro	Becomes	Worth knowing
Mermaid Diagram	A Capable diagram holding the Mermaid source	The source is read from the page attachment, at the revision the macro pinned. The title comes from the attachment name. A macro with no file name cannot be resolved and is reported. Source that does not start with a known Mermaid keyword is still migrated, with a warning.
PlantUML Diagram	A Capable diagram holding the PlantUML source	Compressed and plain source both convert, including source held in the macro body, which is how Data Center imports usually arrive. Missing `@startuml` and `@enduml` lines are added. Copies of the same macro on one page become references to the first migrated diagram. A macro with no source at all fails.

Only a few diagrams? Edit the page, insert Diagram (Capable), select Import and pick the Stratus diagram under Diagrams from other apps. It is converted one at a time, with no migration run.

#What happens next

Each page the run changes gets a new version labelled "Migrated by Capable", so any page can be put back from its history.
Re-running is safe. Run again for more spaces, or for pages that failed once you have fixed the cause.
To undo a whole run, open Repair on the Migration tab and use Roll back pages with the log you downloaded. See Roll back a Confluence macro migration.

#If it does not work

No Migration tab: you are not a Confluence administrator, or you are in the wrong app. See I cannot find the Migration tab.
Pages you cannot edit are skipped and reported as permission failures. Use Admin Key (experimental) under Advanced options lets an administrator migrate them.

Mermaid for Confluence (Stratus)

Full migration notes for the Mermaid app.

PlantUML for Confluence (Stratus)

Full migration notes for the PlantUML app.

Test a Confluence migration with a dry run

Verify before you write anything.

Roll back a Confluence macro migration

Undo a run from its log.

Mermaid

Where migrated Mermaid diagrams live.

Run a migration

Every wizard step and option.

Same source, now a Capable diagram.