Moving from a standalone app
Moving from a standalone Capable app to the suite is a migration rather than an upgrade, because content does not carry across on its own. The two are different apps with different keys.
The order matters, and the migration wizard is the tool that does the work.
#The order
A user-run migration, in this order: install the Suite, keep the standalone app installed, run the Migration wizard in Capable global settings, verify, then uninstall the standalone app. Content is copied, not moved, and re-runs repair rather than duplicate. Migrators exist today for Diagrams, Markdown, Images, Search and Macros.
Step | What you do |
|---|---|
1 | Install the suite. Keep the standalone app installed. |
2 | Open the Migration wizard in Capable global settings. |
3 | Choose the behaviour version that copies standalone app content. See the Migration space. |
4 | Verify, then migrate. |
5 | Review the result, then uninstall the standalone app. |
Do not uninstall the standalone app first. Uninstalling deletes the content it stored, and the migration needs to read it.
#What carries across
Macros are converted, and the content behind them is copied: templates, saved searches and image libraries migrate as their own items, provided you choose the behaviour version that includes them.
#A few things worth knowing
The default behaviour version converts macros only. For a standalone move you need the version that also copies app content.
Both apps can be installed at the same time, which is what makes this possible.
The migration wizard is the same one used to migrate off another vendor's app.
#Related
Install, migrate, verify, then uninstall.
