Closed beta - early access by request

Signavio .sgx BPMN 2.0

A free converter that preserves what Signavio strips: layout, glossary references, metadata, and revisions. Built for teams forced to evaluate alternatives after the SAP acquisition.

Drop your .sgx file here

Closed beta - request early access below

Tested on real customer workspaces. Currently onboarding teams 1:1 to capture edge cases before public launch.

Why convert from .sgx, not .bpmn?

Signavio's built-in BPMN export drops most of what makes your workspace valuable. The .sgx workspace archive is the only format that keeps it all.

Capability.sgx (workspace).bpmn export
Exact waypoints (dockers)✅ Pixel-perfect⚠️ Re-routed by exporter
Lane geometry⚠️ Approximate
Glossary references✅ Structured❌ Inlined as text
41 metadata definitions + values❌ Partial in <documentation>
Revisions & comments❌ Lost
Reusable risks❌ Lost
Cross-diagram links✅ Structured refs❌ Bare URL strings
Stencil set perspectives❌ Lost

Source: Comparison based on real Signavio workspace exports including HelloFresh DPD and EDI samples.

How to export your Signavio workspace

  1. 1

    Open SAP Signavio Process Manager

    Sign in to your workspace at editor.signavio.com or your tenant subdomain. You need a user role with export permission - usually any modeler or admin.

  2. 2

    Navigate to your workspace root

    Go to the top-level workspace folder. You'll export the entire workspace, including all subfolders, glossary, and attribute definitions.

  3. 3

    Click Export → Signavio Archive (.sgx)

    Choose .sgx, not .bpmn. The .sgx archive is a ZIP containing the full Oryx JSON for each diagram plus all metadata. Download size is typically 1-50 MB depending on workspace size.

  4. 4

    Drop the .sgx file into the converter above

    Once we onboard you to the closed beta, drag-drop the file. Conversion runs entirely client-side - your workspace never touches our servers. Output: clean BPMN 2.0 XML for each diagram, plus a structured JSON report.

  5. 5

    Import into Crismo (optional)

    The structured report includes glossary, attributes, and links - which Crismo re-imports natively, so your model keeps all its original semantics, not just shapes.

What survives the conversion

Diagram structure

  • All BPMN 2.0 elements (events, tasks, gateways, subprocesses)
  • Pools, lanes, and lane containment
  • Sequence flows and message flows
  • Data objects and data stores

Layout fidelity

  • Exact docker waypoints (no re-routing)
  • Lane heights and widths
  • Element positions in pixels
  • Label positions

Glossary

  • All glossary entries with their original UUIDs
  • Glossary categories (mapped to Crismo dictionaries)
  • References from diagram elements (preserved as structured links)
  • Custom attributes on glossary entries

Metadata

  • All 41 metadata field definitions
  • Field values per diagram element
  • Custom metadata categories
  • Reusable risk and control entries

Revision history

  • Every revision of every diagram
  • Author and timestamp per revision
  • Revision comments
  • Change diffs (where present)

Cross-diagram structure

  • Model-to-model links (structured, not bare URLs)
  • Sub-process call relationships
  • Process landscape hierarchy
  • Stencil set perspectives

Why teams are leaving Signavio in 2026

SAP licensing model

After the 2021 SAP acquisition, Signavio pricing moved into SAP's enterprise contracts. Renewal quotes have climbed sharply for many existing customers.

SAP Signavio rebrand friction

Product positioning shifted toward S/4HANA buyers. Teams not on SAP stacks find the bundling and integration story increasingly mismatched to their needs.

Lock-in risk

The .bpmn export is lossy on purpose - it preserves shapes but strips the structured glossary, attributes, and links your team built up over years. Without a real .sgx tool, leaving means losing data.

Frequently asked questions

Want early access to the converter?

Drop your email above to join the closed beta. We onboard teams 1:1 to capture edge cases. If you have a workspace export ready, we can usually convert it within 48 hours.