Skip to content

Importing a Threat Model

Devici allows you to import existing threat models to continue analysis and collaboration without starting from scratch.

You can import threat models created in supported formats directly into a collection.

Supported import formats

Devici currently supports importing threat models from the following formats:

  • OTM (.otm) — Open Threat Model format
  • Draw.io (.drawio / .xml) — diagrams exported from draw.io
  • Microsoft Threat Modeling Tool (.tm7)

Imported models are converted into native Devici threat models, where you can continue refining elements, attributes, threats, and mitigations.

Where imported models live

When you import a threat model:

  • It is added to the collection you selected
  • Access is governed by the collection’s permissions
  • The model behaves like any other Devici threat model after import

Import a threat model from the Create New flow

Use this method when creating a new threat model from scratch.

  1. Navigate to the Collections view
  2. Click Create new
  3. In the modal, select Import a threat model
  4. Choose the file format you want to import
  5. Upload your file
  6. Confirm the import

Once complete, the threat model will appear in the selected collection.

Import a threat model into an existing collection

Use this method when you already know which collection the model belongs to.

  1. Navigate to Collections
  2. Locate the collection you want to import into
  3. Click the three-dot menu next to the collection name
  4. Select Import
  5. Choose the file format
  6. Upload your file

The imported threat model will be added directly to that collection.

After importing

After import, we recommend:

  • Reviewing elements, data flows, and trust boundaries
  • Verifying attributes and mappings
  • Checking generated threats and mitigations
  • Updating names or descriptions to match your conventions

Imported models can be edited, reviewed, versioned, and shared like any other Devici threat model.

Notes and limitations

  • Some formatting or layout differences may occur when importing from diagram-based tools
  • Attributes and threats are mapped to the closest supported Devici equivalents
  • Unsupported or custom constructs may require manual adjustment after import

Troubleshooting

If an import fails or the resulting model does not look as expected:

  • Verify the file format and version
  • Confirm you have access to the target collection
  • Check for unsupported elements in the source model

If issues persist, contact Devici support with the file format and error details.