60.4 Profile Import and Export
60.4.1 Overview ¶
Profiles can be exported as a JSON file and imported again on the same or another machine - to transfer between workstations, as a targeted backup copy of individual profiles, or as a template.
60.4.2 Exporting ¶
| Path |
Scope |
| Toolbar → Profiles → Export profiles... |
All profiles |
| Context menu of a profile list entry → Export profile... |
Only the selected profiles |
60.4.3 Importing ¶
Toolbar → Profiles → Import profiles... reads a previously exported JSON file. For profiles whose name already exists, the import dialog asks how to handle them: Overwrite existing profile, Add as copy, or Skip.
Besides export files, the import also reads a Profiles.json as well as profile files of Automatic X-Invoice Processor 1 (its export or Profiles.json). Version 1 profiles are converted in the process; profiles with tasks for several file types are distributed across up to three profiles (see chapter 99.8). The import dialog handles the parts of such a profile together - Overwrite existing profile then also replaces a profile of the same name without suffix.
Note: Machine-specific resources do not travel with the profile: database connections are referenced by name only (see chapter 40.15); depending on the setting, passwords remain in the Windows vault of the source machine (see chapter 40.5.5). After importing, also check whether the monitored folders exist on the target machine - with environment variables in the paths (see chapter 8.8.2), exports work across user profiles as well.
60.4.4 Distinction from backup and the central profile file ¶
- The backup (see chapter 60.3) captures the complete application data including options; the profile export targets individual or all profiles.
- For profiles permanently shared by several workstations, the centrally managed profile file is the right tool (see chapter 40.5.6).