# Migrate from AppFox Approvals to Capable Approval in Confluence To move from AppFox Approvals for Confluence to Capable Approval, a site administrator runs the Migration Assistant on the **Migration** tab of Capable's Global settings, picks **Approvals for Confluence (AppFox)** and its **Page Approval** migrator, verifies, then migrates. Each page gets a Capable approval with the same status, approvers, history and expiry. --- ## Before you start | **You need** | **Why** | | ---------------------------------------------- | ------------------------------------------------------------------ | | A Confluence site administrator | The Migration tab is in Global settings. | | Space admin permission in every affected space | The account running the migration writes approvals to those pages. | | AppFox Approvals still installed | Keep it until you have checked the result. | | Capable Approval | In Capable for Confluence or the standalone Capable Approval app. | --- ## Steps 1. Open **Global settings** for Capable in Confluence administration and select the **Migration** tab. 2. On **Introduction**, tick the acknowledgements, then continue past **Options**. 3. On **Select apps**, tick **Approvals for Confluence (AppFox)**. 4. On **Select macros**, tick **Page Approval**. 5. Select **Perform verification**. It is a dry run: nothing is written. Read the results. 6. Select **Start migration**, then **Download log** when it finishes. 7. Open a few pages and check the Capable approval and its history. --- ## What comes across | **From AppFox** | **In Capable Approval** | | ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | | Approval status, approvers and each person's response | Carried across. | | Quorum size | Becomes **Minimum approvers**. | | Approval history | Carried across. Where AppFox only recorded that a comment was made, the history says _A comment was provided but not migrated_. | | Expiry by date or interval | Carried across. A pending approval keeps its interval rule but has no expiry date until it is decided. | | Section Approval and Status Macro | Not converted. They are counted on **Select macros** so you can see where they are. | | Email notification settings | Not carried across. | Decided approvals also get a _Migrated on_ entry in their history, dated the day you ran it. Page content is never changed. --- ## If it does not work * A page reports _No AppFox approval properties found on this page_: it has no AppFox page approval to bring across. * Roll back restores page versions, and this migration does not edit pages, so it does not remove migrated approvals. Verify first, and remove any approval you do not want by hand. See [Remove or restart an approval](https://help.gocapable.com/approval/remove-or-restart-an-approval.html). * For the full procedure, scoping by space and reading the log, see [Migrate Confluence approvals from AppFox](https://innovator.atlassian.net/wiki/spaces/MB/pages/1542718200) in the Migrate to Capable space. --- ## Related ### [Migrate Confluence approvals from AppFox](https://staging.dev.capable-sites.com/wiki/pages/1542718200) The full procedure in Migrate to Capable. ### [Test a Confluence migration with a dry run](https://staging.dev.capable-sites.com/wiki/pages/1542750771) Verify before you migrate. ### [Migrate from standalone Capable Approval to Capable for Confluence](https://help.gocapable.com/approval/migrate-from-standalone-capable-approval-to-capable-for-confluence.html) Moving from Capable's own app. ### [View approval history](https://help.gocapable.com/approval/view-approval-history.html) What the history shows after migration. ### [Setting up approvals for a space](https://help.gocapable.com/approval/setting-up-approvals-for-a-space.html) All setup guides. --- _Same decisions, same history, new home._