Projects and transferable data
Know what a project saves and what stays local.
AlphaA project stores automation definitions and transferable configuration. Core owns the open project and coordinates its writes.
What belongs where
| Data | Owner / location |
|---|---|
| Automations, macros, variable definitions, statistics rules | Project definition |
| Plugin project settings and entity state | Project components owned by each plugin |
| Persistent statistics | The project's .shubdata sidecar |
| Captured run history | .shubdata/runs |
| Service credentials and local profiles | Protected local Core settings |
| Theme, language, hotkeys and layout | Local Editor preferences |
Use Save As to create a project at a new path. Core copies known statistics/history data and directs later writes to the new location. Keep the original files if you need a separate backup.
Import and export
Review the selected components, required plugins and conflict choices before importing. A script, automation folder or entity collection is a smaller transfer unit and can depend on macros, entities or files outside it.
Copying only .shubproj does not transfer captured history. Current .shubpack export does not include run history either. Copy the matching sidecar when manually transferring retained runs, while Core is stopped.
Local Editor layout does not travel with newly saved or exported projects. External media and context paths may need relinking on another computer.
See Editing, Apply and Save, Settings and service profiles and Project recovery.