# Migrate to Capable Diagrams You almost certainly have diagrams already. The point of migration is that they arrive editable rather than as flattened images, so the next person can still change them. --- ## What can come across | **From** | **Arrives as** | **Still editable** | | ---------------------------- | ------------------------- | --------------------------------- | | **draw.io / diagrams.net** | A Capable draw.io diagram | Yes | | **Gliffy** | A Capable draw.io diagram | Yes | | **Viadee BPMN** | A Capable BPMN diagram | Yes | | **Stratus / Mermaid macros** | A Capable text diagram | Yes | | **Pasted images** | An attachment | No, there is no source to recover | 📝 Migration copies rather than moves. The original macros are left alone until you are satisfied, so a migration is reversible by doing nothing. --- ## Everything in this section [Migrate from draw.io for ConfluenceExisting diagrams, converted in place.](https://help.gocapable.com/diagrams/migrate-from-draw-io-for-confluence.html)[Run a migrationThe five steps, and what to do at each.](https://help.gocapable.com/diagrams/run-a-migration.html)[Migration results and re-runsReading the report, and fixing what failed.](https://help.gocapable.com/diagrams/migration-results-and-re-runs.html)[Migrate from other diagram appsEverything else, via import.](https://help.gocapable.com/diagrams/migrate-from-other-diagram-apps.html) --- ## Related [AdministrationRunning a migration across a site.](https://help.gocapable.com/diagrams/administration.html) [TroubleshootingWhen a diagram does not come across cleanly.](https://help.gocapable.com/diagrams/troubleshooting.html) [ReferenceWhich file formats are understood.](https://help.gocapable.com/diagrams/reference.html) --- _Bring them across editable, not as flattened pictures._