Move from a standalone Capable app to Capable for Confluence
To move from a standalone Capable app to Capable for Confluence, install the suite next to the standalone app, run the Migration wizard in Capable's Global settings, check the result, and only then uninstall the standalone app. Content is copied, not moved. Approval has a guided move of its own that also carries approval history.
#Before you start
You need to be a Confluence site administrator.
Keep the standalone app installed and licensed until you have checked the result. The migration reads the standalone app's content, and uninstalling deletes everything the app holds in Forge storage and Forge SQL, such as approvals and their history.
Moving Approval? Follow Move from standalone Capable Approval instead, which freezes, exports and imports approvals.
#Steps
Install Capable for Confluence from the Atlassian Marketplace. Leave the standalone app installed.
Open Global settings for Capable and select the Migration tab.
On Options, choose the behaviour version that copies standalone app content as well as converting macros.
On Select apps and Select macros, tick the standalone app and its migrators.
Press Perform verification, then Start migration, and Download log when it finishes.
Check the results and a few pages, and run it again until nothing is listed as failed.
Uninstall the standalone app.
#If it does not work
Pages show their content twice: you kept the source macros. Re-run without that option.
Templates or image libraries did not come across: the behaviour version you chose converts macros only. Run again with the version that copies content.
The run stopped: it lives in the browser tab. Open it again and re-run; re-runs repair rather than duplicate.
#Related
Install, migrate, verify, then uninstall.
