Export

Exporting creates a backup of application profiles — registry entries, configuration files, and data folders — based on your application definitions. Exports can be run from the GUI or automated via the CLI.


How Export Works

The export process reads your application definitions, collects the specified registry entries and files from the local system, and writes them to a target location along with a manifest XML file. The manifest describes what was exported and is required for import.

Export uses a best-effort approach: if individual registry keys or files cannot be read (e.g. access denied, locked files), the export continues with the remaining items and reports partial failures.


What Gets Created

An export produces a manifest file and a data folder at the chosen target location:

Output Description
MyBackup.xml Manifest file — lists all exported applications with metadata
MyBackup\ Data folder containing per-application subfolders with Registry\ and Files\ subdirectories

The data folder name is derived from the manifest file name (without extension). Both the manifest and data folder must remain together for import.


GUI vs. CLI

Method Best For
GUI Export Interactive use — select apps visually, create/edit definitions, monitor progress in real time
CLI Export Automation — scheduled tasks, deployment scripts, CI/CD pipelines, silent mode for non-interactive operation


Topics in This Section


Next Steps

After running your first export, you may want to: