Your application.
Ready for another Studio.
Move an editable application between teams or separate Cohuno installations. A Studio source bundle keeps saved processes, pinned dependencies and local resource files together.
Open application workspace →Package saved sources.
Open the project workspace and choose Import / export application. Save your work first. Review literal values, variable defaults, code and resource files; sample inputs are excluded by default.
Inspect before importing.
Choose the .csp file in the recipient Studio. Inspect process and resource revisions, connection requirements and the SHA-256 digest. Compare the digest with the sender over a trusted channel.
Create a new project.
Pick an unused project ID and confirm. References are rewritten to new revision-1 copies owned by the recipient. The original application and any existing recipient projects are not overwritten.
Source exchange is not deployment.
A .csp bundle is an editable source package. A .car belongs to the deployment workflow. Importing sources does not execute code, start listeners, install dependencies or deploy a runtime.
What travels with an application?
Processes and project resources
Saved process revisions, transitive subprocess references, project resources, pinned schema and mapping resources, local files contained in those resources, and logical connection declarations. Unsaved editor changes, live state and execution history are not included.
Credentials and external dependencies
Runtime connector profiles, environment secrets, cloud credentials and paid vendor binaries are not transferred. Imported connector IDs are isolated; an operator must bind the new IDs locally. Install required third-party drivers or packages separately under their applicable licenses.
Trust and compatibility
Archive checksums detect corruption, not publisher identity. Review code, SQL and transformations before running them. Both Studios must support the exchange format and the activities used by the application. Unknown model fields or unsupported formats are rejected instead of silently discarded.
Interrupted imports
The import writes the project and its receipt in one database transaction. The same request ID, file and target project return the same result. Reusing that request ID with different contents is rejected.