# Approval

One approval migrator is fully supported: AppFox Approvals, which moves approval state without touching page content at all.

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 8 recognised macros here across 3 apps: 1 convert, and 7 are reported only.

ℹ️

One fully supported migrator, AppFox Page Approval, which moves approval state without touching page content at all. Everything else in this family is reported for visibility only. Note that most approval macros are found by looking at stored page properties rather than by macro name.

---

## Apps we migrate from

[Approvals for Confluence (Appfox)How Capable migrates Approvals for Confluence (AppFox): every macro it recognises, what converts, what is reported only, and the caveats worth knowing first.](https://help.gocapable.com/migration/approvals-for-confluence-appfox.html)[Page Approval for Confluence (Appfire)How Capable migrates Page Approval (Appfire): every macro it recognises, what converts, what is reported only, and the caveats worth knowing first.](https://help.gocapable.com/migration/page-approval-for-confluence-appfire.html)[Comala Document Management (Appfire)How Capable migrates Comala Document Management (Appfire): every macro it recognises, what converts, what is reported only, and the caveats worth knowing first.](https://help.gocapable.com/migration/comala-document-management-appfire.html)

---

## Related

[What we migrateEvery family.](https://help.gocapable.com/migration/what-we-migrate.html)

[Using the migration assistantRunning one of these.](https://help.gocapable.com/migration/using-the-migration-assistant.html)

[TroubleshootingWhen something does not convert.](https://help.gocapable.com/migration/troubleshooting.html)

---

_State, not content. That is why it is careful._