SFUMIA / Documentation
Guide
Export and reimport a project's graph
Keep a JSON file of the canvas and choose between merging and replacing.
In this guide
Understand the JSON contents
The export covers the active project: nodes, parameters, internal connections, shots and saved presentation data. It does not include scene files, images, videos, output files or AI models. To move your files to another PC, use personal workspace transfer.
Links to other projects are listed in the file. They are not recreated automatically on import; check these dependencies in the destination project.
Export the active project
- Save your current work and select the project to export.
- With no node or frame selected, find « Exporter canvas » in the properties panel and click it.
- Check that the .json file has actually downloaded. Keep a name that identifies the project and date.
Choose the import mode
« Importer (fusion) » adds new elements and updates those with the same identifier. Two nodes with the same name are not necessarily the same node. Merging can therefore change existing work.
« Importer (remplacer) » replaces nodes, connections and shots with those in the export. Nodes absent from the file can disappear from the destination graph. An empty graph can therefore clear its node list.
View and colour data in the file can also be applied when merging. Export the destination state before importing and keep full backups; do not rely on canvas undo to restore everything.
Import and check the result
- Open the destination project. In a studio, check your permissions and reserve the existing nodes the operation will modify or remove, including affected parent resources.
- With no node or frame selected, choose « Importer (fusion) » or « Importer (remplacer) », then select the JSON file exported by SFUMIA.
- Review the source, destination, mode and numbers of nodes, connections and shots in the confirmation. Cancel if the summary does not match your intention.
- After confirming, read the displayed result. Check nodes, connections, shots, required files and cross-project links before running a calculation.
Import by dragging a file
Drop the .json onto the active project's canvas to request a merge. Holding Shift when dropping requests replacement. Review the confirmation before continuing.
Understand a refusal
Keep the original JSON and read the specific message. An invalid format, duplicate identifiers, a link to a missing node or a folder already assigned to a node can prevent import.
If the graph has changed, refresh and check the destination, mode and reservations again before retrying. To change an existing node's type, folder or shot, use its dedicated tools; JSON does not replace that process.
Models and access
Node definitions remain subject to your installation's access rights. Mentioning an engine or product in a file does not make it available on import. Check the component's status and retain the model terms.
Available features depend on your version and installation.