Approval
Two approval migrations are fully supported: AppFox Approvals, which moves approval state without touching page content at all, and Capable's own standalone Approval app moving to Capable for Confluence.
Everything else in this family is detected and reported so you can see the scale of the problem, but not converted. Approval data is stateful, and a half-migrated approval is worse than none.
There are 9 recognised macros here across 4 apps: 2 convert, and 7 are reported only.
Most approval macros are found by looking at stored page properties rather than by macro name, so a space filter behaves a little differently in this family.
#From standalone Capable Approval
Sites that used the standalone Capable Approval app can move to Capable for Confluence with every page's approval status, approvers, comments and full history, plus teams, space settings and Slack channel settings. It is a guided move in three parts, and the order matters:
Step | What you do |
|---|---|
1 | In Capable Approval, Freeze and export. Approvals become read-only until each page is imported. |
2 | In Capable for Confluence, load the export, then run Approval macro (Standalone → Suite) under Approval for Confluence (Capable) in the migration assistant. Do not keep the source macros. |
3 | Back in the suite's approval migration settings, Import, review, then Finish. |
The macro migrator only changes which app renders the macro. The approval data moves with the import, and the migrator refuses every page until the export is loaded. Read the full guide before you start: Move from standalone Capable Approval, or the short version in Move approvals from standalone Capable Approval to the suite.
#Apps we migrate from
#Related
State, not content. That is why it is careful.
