Import and export
Select the groups to back up, preserve linked images and review conflicts before importing.
Rights and scope
File import/export requires the relevant Pro entitlement. MCP access alone is not a file-transfer right. If rights have just changed, use Account → Overview → Refresh rights.
Export
- Open Export in the account area.
- Select root groups and subgroups. A parent selection may include children; inspect the selected list.
- Include dependency groups referenced by the selected flow.
- Save the .jaqb backup in a trusted folder.
- Restore it into an empty test project and verify the content.
Import
Choose the file and review the groups. If an existing root group has the same name, inspect the conflict and explicitly accept a renamed copy. Check the added groups and entry point instead of assuming existing content was overwritten.
Preserve images
Linked PNG templates travel with the selected workflow. IDs are remapped during import to avoid conflicts with the existing project. File integrity and PNG structure are checked. Use a sound backup rather than forcing a corrupted file to load.
Another computer
A transported image does not imply identical screen resolution, DPI or window geometry. Recheck program paths, targets, coordinate references and local object-library requirements. Start with dry run and a single group test.
Different resource scopes
Cloud delivery, a local .jaqb backup and the training/model library are separate. Do not assume every ONNX model is packaged in the file. Keep private API keys out of shared workflows.