# Migrating approvals Approvals are state rather than content, so they move differently from other macros. Two paths are fully supported: AppFox Approvals, and Capable's own standalone Approval app moving to the suite. --- ## Common tasks | **You want to** | **Go to** | | -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Move off AppFox Approvals | [Migrate Confluence approvals from AppFox](https://help.gocapable.com/migration/migrate-confluence-approvals-from-appfox.html) | | Move from standalone Capable Approval to the suite | [Move approvals from standalone Capable Approval to the suite](https://help.gocapable.com/migration/move-approvals-from-standalone-capable-approval-to-the-suite.html) | | See every approval app we recognise | [Approval](https://help.gocapable.com/migration/approval.html) | --- ## Guides in this section [Migrate Confluence approvals from AppFoxMove page approvals from AppFox Approvals for Confluence into Capable Approval, without changing page content.](https://help.gocapable.com/migration/migrate-confluence-approvals-from-appfox.html)[Move approvals from standalone Capable Approval to the suiteFreeze and export in Capable Approval, migrate the approval macros, then import into Capable for Confluence.](https://help.gocapable.com/migration/move-approvals-from-standalone-capable-approval-to-the-suite.html) --- ## Related ### [Approval](https://help.gocapable.com/migration/approval.html) Every approval migrator. ### [Move from standalone Capable Approval](https://staging.dev.capable-sites.com/wiki/pages/1541865474) The Approval guide to the move. ### [Running a migration](https://help.gocapable.com/migration/running-a-migration.html) Dry runs and rollback. --- _State, not content. That is why it is careful._