Migration behaviour versions
This is the setting people miss, and it is the one that changes the most. The picker at the top of the Options step is not "which release am I on", it selects how much work the migration does.
Each version includes everything the one before it does. Pick the highest version that describes what you actually need, then leave it alone: the version you chose is stamped into the results and the downloaded log, which is what makes a run reproducible and a log meaningful months later.
#At a glance
Option | Values | Default |
|---|---|---|
Migration behaviour (version picker) | v1.0.0 Standard migration (marked Recommended) / v1.1.0 Diagram version history / v1.2.0 Capable standalone app content | v1.0.0 |
#What each version adds
Version | What it does | Cost |
|---|---|---|
v1.0.0 Standard migration | Converts macros only. Diagrams arrive as a single current version, authored by whoever ran the migration. | Fastest. Marked Recommended in the product. |
v1.1.0 Diagram version history | Everything above, and replays draw.io and PlantUML diagrams version by version so each version keeps its original author and edit date. | Noticeably slower on large estates, because every version of every diagram is fetched. |
v1.2.0 Capable standalone app content | Everything above, and copies the content behind standalone Capable app macros into the Suite: templates, saved searches and image libraries migrate as their own rows. | Slower again, and only relevant if you are moving off a standalone Capable app. |
If you are moving off a standalone Capable app, v1.0.0 is not enough. Only v1.2.0 copies the content behind those macros. The picker still defaults to v1.0.0 and marks it Recommended, so this is worth a deliberate decision rather than accepting the default.
#Choosing
If you are | Use |
|---|---|
Moving off a third-party app and do not need diagram history | v1.0.0 |
Moving off draw.io or PlantUML and the edit history matters | v1.1.0 |
Moving from a standalone Capable app into the Capable Suite | v1.2.0 |
There is a fourth version in the changelog. v1.3.0 appears but cannot be selected: the current build can no longer reproduce it. It is kept so that an old log naming it still means something.
#A few things that catch people out
Version history and original authorship have no separate checkbox. This picker is the only way to switch them on.
Diagram history replay makes the run substantially longer. On a large estate, pilot it on one space first and measure.
Changing your mind after a run means running again with the higher version, not repairing.
#Related
Pick it deliberately. It is stamped into the log.
