Migrate from standalone Capable Approval to Capable for Confluence

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

To move from the standalone Capable Approval app to Capable for Confluence, a site administrator freezes and exports approvals in Capable Approval, loads the file in Capable for Confluence, migrates the approval macros with the Migration Assistant, imports, checks the results, then selects Finish. Each step refuses to run until the one before it is done.

#Before you start

You need

Why

A Confluence site administrator

Every step is administrator only.

Both apps installed, licensed and up to date

An unlicensed Capable Approval cannot export.

A quiet period

Approvals are read-only from the first step until each page is imported.

#Steps

In both apps the controls are in Global settings, on the Approval tab, in the Migration section.

  1. In Capable Approval, select Freeze and export, then download the export file when it is ready.

  2. In Capable for Confluence, choose the export file and select Load.

  3. Open the Migration Assistant. Under Approval for Confluence (Capable), pick Approval macro (Standalone → Suite), run Verify, then Run. Repeat until nothing is failed or skipped.

  4. Back in the Migration section, select Import and keep the tab open while it runs.

  5. Review each page's result. Undo a page or Undo all imported pages if something looks wrong.

  6. Select Finish. This is final, so check the results first.

#What happens next

  • Capable for Confluence handles the migrated approvals normally. Imported rows show an Imported badge in the history.

  • Approvers set up their authenticator again, connect Slack again, and everyone sets their own notification choices again.

  • Keep Capable Approval installed and frozen for two to four weeks, then uninstall it and keep the export file as your archive.

Every signature comes with you.