Migrate from Structurizr to Archyl | Step-by-Step Guide
Import your Structurizr workspace into Archyl in minutes. Keep your C4 model, add AI discovery, drift detection, and MCP server integration.
Structurizr Migration
Migrate from Structurizr to Archyl
Import your Structurizr DSL workspaces into Archyl. Systems, containers, components, relationships, technologies and tags come across; views, styles, layout, deployment nodes and !docs/!adrs do not, and the importer names each one it skipped -- and unlock drift detection, conformance, DORA metrics, and AI-powered tools.
Migrate from Structurizr to Archyl | Painless DSL Import
Import your Structurizr DSL workspaces into Archyl. Keep all your systems, containers, components, relationships, and tags. Unlock drift detection, DORA metrics, and MCP tools.
Structurizr alternative, Structurizr migration, migrate from Structurizr, Structurizr to Archyl, Structurizr DSL import, architecture documentation tool
Your full Structurizr DSL workspace files are parsed and imported as-is.
All top-level software systems with their names and descriptions.
Every container including web apps, APIs, databases, and message queues.
Components within containers, preserving the full C4 hierarchy.
All connections between elements with descriptions and technologies.
Technology annotations on containers and relationships are preserved.
Custom tags defined in your DSL are imported and applied to elements.
Copy your DSL content
Open your .dsl workspace file and copy its content, or have the file ready for upload.
Select Structurizr format
In Archyl's import dialog, choose "Structurizr DSL" as the source format.
Paste or upload your DSL
Paste your DSL content directly into the editor or upload your .dsl file.
Import and start working
Archyl parses your DSL and creates the full C4 model. Review and start extending your architecture.
Get a 0-100% health score showing how accurately your documentation reflects your actual codebase. Catch drift before it compounds.
Define architecture rules and run automated checks to ensure your system stays within defined guardrails.
Track deployment frequency, lead time, change failure rate, and recovery time alongside your architecture health.
MCP Server (181 Tools)
Query architecture data from Claude, Cursor, or Windsurf through 181 specialized MCP tools. Architecture knowledge at your fingertips.
Architecture Decision Records
Link ADRs directly to C4 elements so every design decision has traceable context within your architecture model.
Attach OpenAPI, AsyncAPI, or GraphQL schemas to containers and components. Keep contracts versioned alongside your architecture.
Do I need to change my DSL?
No. Archyl parses standard Structurizr DSL syntax directly. You do not need to modify your workspace files before importing. The parser handles workspace definitions, model elements, relationships, and tags.
What about views and styles?
Archyl focuses on importing your C4 model -- systems, containers, components, and their relationships. Visual views and styles from Structurizr are not imported because Archyl uses its own visual editor and layout engine. Your architecture data is fully preserved.
Can I keep using Structurizr alongside Archyl?
Yes. You can maintain your Structurizr DSL files and re-import whenever you want. Some teams use Structurizr DSL as their source-of-truth in version control and periodically sync to Archyl for drift detection and collaboration features.
What happens to deployment environments?
Deployment and infrastructure nodes are not imported. Archyl's Structurizr parser skips them, so you model environments in Archyl after the import.
Is the import reversible?
The import creates a new version of your project. You can always roll back to a previous version if needed, or delete the imported elements and start over.