Moving to Capable for Confluence

Moving to Capable for Confluence from a standalone Capable app is a migration, not an upgrade. Install the suite next to the old app, migrate, check, and only then uninstall. Approval has a guided move of its own. Moving from another vendor's app uses the same Migration Assistant, documented in the Migrate to Capable space.

#Common tasks

You want to	Go to
Move a standalone Capable app to the suite	Move from a standalone Capable app to Capable for Confluence
Move standalone Capable Approval	Move from standalone Capable Approval
Migrate approvals from AppFox	Migrate Confluence approvals from AppFox
Migrate diagrams from draw.io	Migrate from draw.io to Capable Diagrams
Try a migration without changing anything	Test a Confluence migration with a dry run
Migrate from another vendor's app	Migrate to Capable: how-to guides and FAQ
Uninstall Capable for Confluence	Uninstall Capable for Confluence: what is kept and what is deleted
Know what happens to your data when you uninstall	Uninstalling: what is kept and what is deleted

#Guides in this section

Move from a standalone Capable app to Capable for ConfluenceInstall the suite, run the migration, check the result, then uninstall the standalone app. Approval uses its own guided move.Uninstall Capable for Confluence: what is kept and what is deletedUninstalling keeps your diagrams, documents and templates, but deletes approvals, teams, calendar events and settings held in Forge storage.

Moving from a standalone app

The order, and what carries across.

Suite or standalone?

Why the suite rather than single apps.

Uninstalling: what is kept and what is deleted

Read before you uninstall anything.

Install, migrate, verify, then uninstall.