Control is a storefront-sensitive case: first identify Steam, Epic, or GOG, then copy that entire save root. Do not flatten the three layouts into one generic path during migration.
Where Control Ultimate Edition stores PC saves
The researched save-location boundary is Windows: Steam: <Steam-folder>userdata<account-id>870780remote ; Epic: %LOCALAPPDATA%RemedyControlDefault-Epic-User ; GOG: %USERPROFILE%DocumentsMy GamesControlSaves. The known file or folder pattern is storefront-specific Control slot/chunk records. This is the practical starting point because launcher, profile, and storefront context can change which copy is active even when two folders look similar.
Storefront and profile differences
Documented launchers or storefronts: Steam, Epic Games Store, GOG Galaxy. The active Steam, Epic Games Store, GOG Galaxy installation determines which local profile and cloud copy can overwrite the save. Identify the storefront and account before restoring files. When looking for a missing save, identify the executable/storefront you actually launched and the user/profile that created the progress before copying anything between directories.
Cloud synchronization
Steam, Epic, and GOG can each synchronize their own save root. GOG documents local backup/restore separately from Galaxy Cloud Saves. A cloud service should be treated as another copy of the save, not as proof that the local folder is disposable. Before a manual restore, let synchronization finish, make an offline backup, and avoid starting the game while files are being replaced.
What the files represent
Control uses different save roots across Steam, Epic, and GOG. A save-set is not identified safely until the storefront directory is known, and recent GOG/Epic variants can use different Default-* profile folder names. The current filename/folder evidence is storefront-specific Control slot/chunk records. File-extension context: No single extension is sufficient to identify every relevant save record. A location guide does not claim that every file in the directory is safe to edit or that files from another storefront are automatically interchangeable.
If the save is not where expected
If progress is missing after a restore, confirm the active Windows account, storefront/profile, cloud state, and exact directory first. Restore the untouched backup before experimenting with individual files or older autosaves. Also check redirected Documents folders, Steam Play prefixes, account IDs, and launcher-specific containers where applicable. Preserve every candidate copy before testing a restore so troubleshooting does not destroy the only surviving version.
Verification context: Windows save location, file-boundary, launcher/cloud, and backup notes were reviewed against the linked game-specific references for Control Ultimate Edition. This Game Hub is documentation only and does not claim a new game-specific Save Editor.
Recorded Phase 40 evidence boundary
This Phase 40 entry is grounded in the researched PC save boundary for Control Ultimate Edition: Windows: Steam: <Steam-folder>userdata<account-id>870780remote ; Epic: %LOCALAPPDATA%RemedyControlDefault-Epic-User ; GOG: %USERPROFILE%DocumentsMy GamesControlSaves The recorded file or folder pattern is storefront-specific Control slot/chunk records. These concrete identifiers are retained so backup, transfer, recovery, and editing preparation remain tied to the documented game/storefront context instead of a generic extension guess.