Import
Importing restores application profiles — registry entries, configuration files, and data folders — from a previous export. AppProfileSafe provides simulation, dry run, and mapping features to ensure a safe and controlled restore process.
How Import Works
The import process reads a manifest file from a previous export and restores the selected applications to the local system. Registry entries are written back to the Windows registry, and files are copied to their original locations.
If restoring to a different machine or user account, mapping rules can translate registry and file system paths automatically (e.g. replacing one username with another).
Import Workflow (GUI)
In the GUI, a full import goes through up to four steps:
| Step | Description | Required |
|---|---|---|
| 1. Preflight | Validates administrator rights, license, configuration, and disk space | Yes (automatic) |
| 2. Dry Run | Read-only impact analysis: compares manifest data against the live system and shows what would change | Optional (checkbox in pre-import dialog) |
| 3. Restore Point | Creates a Windows system restore point before making changes | Yes (automatic, unless skipped with --noRestorePoint in CLI) |
| 4. Import | Writes registry entries and copies files to the target system | Yes |
Additionally, you can run a Simulate Mapping at any time before importing to preview how mapping rules will transform paths — without performing any actual changes.
GUI vs. CLI
| Method | Best For |
|---|---|
| GUI Import | Interactive use — browse manifests, configure mappings, run simulation/dry run, monitor progress |
| CLI Import | Automation — scheduled restores, scripted rollouts, silent mode for non-interactive operation |
Topics in This Section
- Import Overview (Workflow Explained) — Full walkthrough of the GUI import process
- Running a Simulation (Why and When) — Preview mapping transformations without making changes
- Running a DryRun (Impact Analysis) — Read-only comparison of manifest vs. live system
- Performing the Actual Import — What happens during the real restore operation
- Import via CLI — Command-line syntax, parameters, and examples
- Import Troubleshooting — Solutions for common import problems
Next Steps
Before importing, you may want to:
- Mapping — Set up path transformations if restoring to a different machine or user
- Understanding the Manifest File — Verify the contents of your backup
- Simulation vs. DryRun Comparison — Understand the difference between both preview modes