Import and Export SysML v2 Files

Model → Import and Export reads and writes SysML v2 text files and SysML v2 JSON, so you can exchange models with other SysML v2 tools.

Import

• Choose Into this project or Into a new SysML v2 project. Viewers can import only into a new project.
• Drop files on the box or click it to choose them: .sysml files, a .zip of .sysml files (its folders become packages) or a SysML v2 JSON file (the element form of the Systems Modeling API).
• The preview lists each top-level package with its element count and the result: New, Changed, Unchanged or Conflict. Problems are listed above it, each with its file and line; a member that does not parse is left out.
• Clear the packages you do not want, then click Import N Packages (or Create Project). The import is one undo step.
• To start a project from files, use Project Files ▾ → Import SysML v2 Files… on Manage Projects.

Export

• Under Export, choose The whole model or one package, and the format: SysML v2 text (one .sysml file per top-level package; a .zip when there are several) or SysML v2 JSON. Click Export.
• JSON keeps element ids. Text keeps the model; when it is imported again, elements are matched by name.
• Views export as pictures and documents from the Diagrams list (PNG, SVG, HTML, Word); tables and documents have their own Word, Excel and CSV exports.

Limits

• Files are checked before anything is read: at most 2,000 files, 8 MB of text per file, a 16 MB zip, a 24 MB JSON file, 100,000 elements and nesting 64 levels deep. Zip entries with unsafe paths are skipped and listed.
• Element kinds Holarch does not support are left out of a JSON import and listed; their members move to their owner.
• Pulling from and pushing to a SysML v2 model repository (the Systems Modeling API) is not yet available. Exchange files instead.

Other tools can also read the model from Holarch, and AI clients can propose changes: The API and MCP in SysML v2 Projects.