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. Approval has a dedicated move of its own, because approval data is state rather than page content.
#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, Macros and Approval.
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. 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. Keep the app installed until you have checked the result.
#Moving from standalone Capable Approval
Approval moves with a guided tool rather than the wizard alone, so every page's approval status, approvers, comments and full history come across, along with teams, space settings and Slack channel settings. You need to be a Confluence site administrator, and both apps must be installed, licensed and up to date.
Step | Where | What you do |
|---|---|---|
1 | Capable Approval | Freeze and export. Approvals become read-only and you download an export file. |
2 | Capable for Confluence | Load the export, then migrate the approval macros with Approval macro (Standalone → Suite) in the Migration Assistant. |
3 | Capable for Confluence | Import, review the results, then Finish. |
4 | Capable Approval | Uninstall it once you are happy, and keep the export file. |
Approvals are read-only from the freeze until each page is imported. People can see status but cannot approve or reject, and a Slack or Teams button answers that approvals are read-only for now. Plan the move for a quiet period, and do step 1 before the Capable Approval licence ends.
Slack connections, authenticator codes and email opt-outs do not move: connect Slack again in the suite, and approvers set up their codes again. The full walkthrough, including how to go back, is in Move from standalone Capable Approval.
#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. For Approval, the guided move carries the approval data itself.
#A few things that catch people out
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.
Do not tick the option to keep source macros when migrating approval macros. It is not supported for them.
#Related
Install, migrate, verify, then uninstall.
