Import And Export

Archflow project archives use the .archflow.gz format. Use them for backups, environment transfer, or sharing a model outside its current account.

Export Coverage

A full archive can include:

• Versions, Systems, hierarchy, and Relationships
• Architecture Views and their canvas state
• Workflows and step mappings
• Behavior Models, groups, views, and workflow-behavior links
• Capability Maps, compositions, and realization links
• Deployments and deployment relationships
• Architecture Handbook profiles
• Context Map relationships and layout state
• Architecture Documents and View references
• Generated documentation and View selections

Most families can be included or omitted through export options. A version-specific export limits version-owned content to the selected version.

Project access, account settings, provider credentials, MCP tokens, publication URLs, guest tokens, Project Knowledge sources, and Architecture Simulations should not be assumed to travel with the archive.

Export A Project

1. Confirm the project and intended source version.
2. Open the project's export action.
3. Review the resource options.
4. Download the resulting .archflow.gz file.
5. Store it according to the sensitivity of the architecture content.

An archive can contain internal topology, decisions, risks, and documentation. Treat it as confidential project data.

Import A Project

From Projects, choose the import action and upload a compatible archive. The importer remaps resource IDs so the new project does not reuse source identifiers.

After import:

1. Check version names and the active version.
2. Inspect system hierarchy and Relationships.
3. Open Workflows, Behavior Model, Capability Map, Deployments, and Views.
4. Review the Handbook and Architecture Documents.
5. Recreate settings, access, tokens, knowledge sources, and other excluded state intentionally.

Import As A System

From a project's Systems area, a project can be imported beneath an existing architecture element. Imported elements are marked as imported and can be read-only because their source of truth remains the source project.

Resync can add, update, or remove supported imported content as the source changes. Review the preview carefully: local assumptions about an imported subsystem can conflict with the refreshed source model.

Project Knowledge Is A Different Workflow

Uploading a source under Documentation → Project Knowledge extracts candidate architecture evidence; it does not restore a project archive.

Use Project Knowledge when bootstrapping from prose or maintaining evidence. Use project import when preserving structured Archflow resources and identity mappings.