Personal files, repositories, secrets and app data
No Omarchy system snapshot should be counted as recovery for this layer: the v4.0.1 snapshot guide explicitly says /home is not restored. Repositories with uncommitted work, SSH keys, environment files, browser profiles, containers, and local databases need an independent backup and a tested restore.
What this means: Inventory this layer before any install. Keep secrets out of public configuration repositories, retain at least one offline or independent copy, and prove representative files and databases can be restored before wiping hardware.
Basis: Official Omarchy code or documentation · Omarchy v4.0.1 system-snapshots manual
User-owned Omarchy configuration
The v4.0.1 dotfiles manual identifies user configuration under ~/.config, ~/.XCompose, and ~/.bashrc, and recommends backing up customized dotfiles. It distinguishes those files from Omarchy-owned internals under /usr/share/omarchy. That separation is useful, but it is not an automated restore guarantee.
What this means: Version or back up only reviewed user-owned configuration, with machine-specific monitor and input settings separated where possible. Apply it to a fresh test user first so an old config does not mask a current default or migration.
Basis: Official Omarchy code or documentation · Omarchy v4.0.1 dotfiles manual
Applications, web apps, services and removals
The current migration and restore discussions ask for an inspectable environment receipt because this layer is not yet covered by a verified v4.0.1 whole-machine replay. A list of package names alone may miss install method, service state, removals, plugins, and sign-in requirements.
What this means: Keep a human-readable inventory now, but do not assume it can replay the setup automatically. Reinstall through current Omarchy commands, confirm each external account separately, and note what could not be restored.
Basis: Not established · Restore-my-Omarchy workflow proposal
System snapshots
Snapshots are same-installation rollback for the root filesystem through Limine. They are useful after a broken update, but they do not move the machine and they do not recover /home. The guide also warns that user config can remain newer than a rolled-back application format.
What this means: Use snapshots as a maintenance safety net, not as the migration plan or personal-data backup. Record whether the source machine actually uses Limine before relying on the feature.
Basis: Official Omarchy code or documentation · Omarchy v4.0.1 system-snapshots manual
One-command whole-workstation migration
We found a current request for Ubuntu/Fedora-to-Omarchy migration and a separate old-Omarchy-to-new-Omarchy restore proposal. Both are useful evidence of the job people want done. Neither source demonstrates that a migration assistant, backup integration, or environment replay has shipped and passed a clean-machine round trip.
What this means: Plan a staged, inspectable migration today. Do not delay a necessary backup because a proposed assistant may arrive, and do not run an unreviewed script against the only copy of a workstation.
Basis: Not established · Migration assistant request for existing Linux installations