No Man’s Sky has evolved over many years, so older profile directories can contain naming conventions that differ from current saves. That makes destructive cleanup risky. Archive the whole NMS directory before renaming or moving anything, and keep Microsoft Store WGS data separate from normal desktop .hg files. A future game-specific tool should identify the exact generation and container before writing; Phase 23 only documents the storage and backup boundaries.
Prepare the source PC
On the source system, identify the actual No Man's Sky save root: Windows: %APPDATA%HelloGamesNMS
Microsoft Store: %LOCALAPPDATA%PackagesHelloGames.NoMansSky_bs190hzg1sesySystemAppDatawgs | macOS: $HOME/Library/Application Support/HelloGames/NMS/ | Linux / Steam Play: Steam Play: <SteamLibrary-folder>/steamapps/compatdata/275850/pfx/. The expected file/folder pattern is save*.hg
mf_save*.hg (current/metadata family; older installs may contain storage*.hg names). Close the game, let the active launcher finish writing and synchronizing, then make a complete offline copy rather than transferring a file that may still be open.
Preserve storefront and profile identity
Documented storefronts: Steam, GOG Galaxy, Microsoft Store / Xbox app. Desktop storefront files and Microsoft WGS containers are different migration surfaces. Older installations can also contain legacy storage*.hg naming. A transfer between two PCs is simplest when both systems use the same storefront/account/profile context. If the destination uses a different store or container, treat that as a migration problem rather than an ordinary restore.
Move the complete save boundary
Copy the entire NMS profile directory, including metadata companions, before editing or migrating. For Microsoft Store, preserve the WGS container separately. Put the copied data on the destination only after confirming the destination save path. If the game creates a new empty save first, keep that new folder as another backup so you can compare structures and revert.
Handle cloud sync deliberately
Storefront cloud support can synchronize the same profile. Cross-platform/cross-save features should be treated as service workflows rather than proof that arbitrary local files are byte-compatible. Decide whether the local transferred copy or cloud copy should be authoritative before launching the game. If possible, preserve both. After the transferred save loads correctly, make a fresh in-game save and let the launcher synchronize normally.
Check compatibility before blaming the transfer
No Man's Sky uses profile-scoped .hg save records. The Microsoft Store/Xbox app build uses WGS instead of the same visible Steam/GOG-style files. Compatibility note: Older 2016/2017 file naming and current save naming can differ. Do not rename historical .hg files blindly without retaining the originals. If the destination does not see the transferred progress, If an older save is not listed, first preserve every .hg record and compare modification times. PCGamingWiki documents historical storage-to-save rename cases, but any rename attempt should be reversible. Verify game edition/version, store, profile IDs, redirected folders, and mod/DLC dependencies before editing the save itself.
Verification context: Windows/macOS/Microsoft Store/Steam Play locations and historical .hg naming notes were reviewed against current PCGamingWiki coverage.