Leave Signavio without losing what you built
A practical 6-phase playbook for teams evaluating alternatives after the SAP acquisition. Covers the technical migration, the people work, and the governance gotchas.
Why this playbook exists
Since SAP's 2021 Signavio acquisition, the product has steadily moved into SAP's enterprise contract structure. For teams not on S/4HANA, this has meant: rising renewal quotes, longer procurement cycles, bundling pressure with adjacent SAP products, and a feature roadmap increasingly oriented toward S/4HANA integration scenarios.
The hardest part of leaving isn't finding an alternative tool. It's preserving what your team built inside Signavio: the structured glossary, the 41 metadata fields per element, the reusable risk and control library, the revision history, the cross-diagram links between process landscapes. Signavio's built-in BPMN 2.0 export strips most of this on purpose. Without a real workspace converter, "migration" means starting from scratch.
This playbook is built around the free .sgx converter that parses the Signavio workspace archive directly. The technical conversion is the easy part. The phases below cover what comes before and after.
The 6-phase migration playbook
Inventory: what do you actually have?
Before exporting anything, map what lives in your workspace. Count diagrams per folder. List glossary categories and entry counts. Identify which metadata fields are actually used (most workspaces use 8-15 of the 41 available). Find your top 10 most-referenced diagrams. This inventory becomes the success metric for the technical migration.
Outcomes
- →Diagram count per folder
- →Glossary inventory (categories, entry count, usage frequency)
- →Active metadata field list (with field type and usage count)
- →Top 10 reference diagrams (by inbound link count)
- →List of approval-workflow diagrams (for governance planning)
Pilot conversion: one folder, end-to-end
Pick one critical process domain (usually 10-30 diagrams). Export just that folder as .sgx. Run it through the converter. Import into Crismo. Have the original modelers validate: is the layout right, are the glossary references intact, did the metadata survive, can they navigate the structure as expected? Fix any converter edge cases here, before scaling.
Outcomes
- →One domain fully converted and validated
- →List of any converter issues found (fed back to us)
- →Modeler-confirmed match between Signavio and Crismo views
- →Decision: proceed with full migration, or rescope
Parallel-run window
Continue daily work in Signavio. Mirror it in Crismo for the converted domain. This isn't about doing work twice - it's about confirming the team can navigate, edit, and govern in Crismo as fluently as in Signavio. End-of-week reviews in Crismo, daily work still in Signavio. Train modelers, set up the dictionary structure, configure attributes, establish the new approval flow.
Outcomes
- →All modelers trained on Crismo basics
- →Crismo dictionaries match Signavio glossary structure
- →Crismo attributes match Signavio metadata structure
- →Approval workflow established in Crismo
- →Decision: switch source of truth, or extend parallel period
Full workspace conversion
Once the parallel run validates the approach, export the full Signavio workspace. Convert via the .sgx converter. Import to Crismo. The technical step is fast. The settle period is for: catching any diagrams the converter handled differently than expected, re-establishing cross-team links that span domains, and retiring duplicate or stale diagrams that the inventory in phase 1 surfaced.
Outcomes
- →Full workspace converted and imported
- →Cross-domain links restored
- →Stale or duplicate diagrams archived (not migrated)
- →Final modeler sign-off on the new workspace structure
Switch source of truth
Announce internally that Crismo is now the source of truth. Put the Signavio workspace in read-only mode (don't cancel the contract yet - keep it accessible for reference). Update all internal links, documentation, and tool integrations to point at Crismo URLs. Communicate the change to consumers (managers, auditors, downstream teams).
Outcomes
- →Crismo is the source of truth
- →Signavio workspace in read-only mode (still accessible)
- →Internal documentation updated
- →Stakeholders notified
Decommission Signavio
Hold the Signavio workspace in read-only mode through your remaining contract period. This gives you a fallback if anyone needs to verify a historical state. At contract end, archive the .sgx export to long-term storage (compliance retention) and decommission. Document the migration in your team's runbook so the next platform decision starts from data, not guesswork.
Outcomes
- →.sgx archive in long-term storage (compliance)
- →Signavio contract decommissioned
- →Migration runbook documented
- →Cost savings vs prior Signavio renewal quantified
Risks and gotchas teams hit
Underestimating the people work
Modelers who have years of muscle memory in Signavio need real practice time before they can be productive in any new tool. Budget the parallel-run phase fully - cutting it short to save calendar weeks usually backfires with rejection later.
Approval workflow assumptions
Signavio's approval workflow has accumulated a lot of organizational logic over time. Migrating diagrams is easy; replicating the exact approval chain often requires re-thinking governance from scratch. Use this as an opportunity, not a blocker.
Cross-workspace references
If your Signavio setup has multiple workspaces with cross-references, migration is harder. Crismo is tenant-scoped (one workspace per tenant). Plan to consolidate or to model cross-workspace references as external links.
Custom Signavio extensions
Some enterprises have custom Signavio plugins, S/4HANA integrations, or scripted attributes. These don't migrate automatically. Inventory them in phase 1 so they don't surface as surprises in phase 4.
Stakeholder communication lag
Auditors, managers, and downstream teams often discover the migration only when a link breaks. The phase 5 communication is non-optional. We've seen migrations succeed technically but get blamed for "disrupting" users who weren't briefed.
Treating it as a tool swap, not a process refresh
A workspace migration is a rare opportunity to retire stale diagrams, consolidate duplicates, and re-establish modeling conventions. Teams that just lift-and-shift miss this. Phase 1's inventory step is where the cleanup decisions get made.
Related resources
.sgx Converter
The free workspace converter at the heart of the playbook. Closed beta, request access.
Crismo vs Signavio
Feature-by-feature comparison with sourced citations from Signavio's own documentation.
Crismo vs SAP Signavio
What changed under SAP, and how the SAP-Signavio offering compares to a tool built outside SAP's orbit.
Frequently asked questions
Ready to start the migration?
Request access to the converter beta. We onboard teams 1:1 and can usually convert your first workspace export within 48 hours.