Move approvals from standalone Capable Approval to the suite

Updated
View as text
Open in Confluence
Open in ChatGPT Open in Claude

To move approvals from the standalone Capable Approval app to Capable for Confluence, freeze and export in Capable Approval, load the export in the suite, migrate the approval macros with Approval macro (Standalone → Suite) in the migration assistant, then import. Status, approvers, comments and full history come across. The order matters: each step checks the one before.

#Before you start

  • You need to be a Confluence site administrator. Both apps must be installed, licensed and up to date.

  • Approvals are read-only from the freeze until each page is imported, so plan a quiet period and tell your approvers.

  • Export before the Capable Approval licence ends: an unlicensed app cannot export.

#Steps

  1. In Capable Approval, go to Settings > Approval > Migration, select Freeze and export and download the export file.

  2. In Capable for Confluence, go to Settings > Approval > Migration, upload the export and select Load.

  3. Open the migration assistant. Under Approval for Confluence (Capable), select Approval macro (Standalone → Suite), without keeping source macros.

  4. Press Perform verification, then Start migration. Run it again until no approval page is listed as failed or skipped.

  5. Back in Settings > Approval > Migration in the suite, select Import and review the results.

  6. Select Finish, and uninstall Capable Approval once you are happy.

#If it does not work

  • The macro migrator refuses every page: the export is not loaded in the suite yet. Do step 2 first.

  • A page is Held: it still has a Capable Approval macro. Migrate it, then import again.

  • You want to go back: roll the macros back in the migration assistant, then select Unfreeze in Capable Approval.

The full walkthrough, including what does not move, is in Move from standalone Capable Approval.

Freeze, export, migrate, import. In that order.