Moving to a new PC, console, drive, or operating-system install does not have to mean losing progress. This guide explains how to back up game saves, verify cloud copies, transfer local files, resolve sync conflicts, and restore progress safely before you change devices.
Overview
A reliable game-save backup uses more than one layer. Cloud synchronization is convenient, but it is not always a complete archive: a service may sync the newest version, a game may store progress outside its normal save folder, or a corrupted local file may upload before you notice the problem. A local copy on an external drive gives you another recovery option.
Before moving anything, identify three details:
- Where the save lives: on the platform account, in a local folder, on the console, or partly on the game’s own servers.
- Which account owns the progress: a platform account, publisher account, or separate game profile.
- Whether the destination uses the same version: different editions, regions, launchers, operating systems, or remasters may not share saves.
Do not uninstall the old game or wipe the original device until you have launched the game on the new device and confirmed that your expected saves, settings, characters, and unlocks are present.
Checklist by scenario
Moving from one Windows PC to another
- Open the game on the old PC, save manually, and exit normally.
- Allow the launcher to finish its cloud-sync process. If it reports a conflict, stop and investigate rather than selecting an option at random.
- Locate the local save folder and copy it to an external drive or a separate cloud-storage service. Keep the original folder structure.
- Record the game version, launcher, account, and installation location. These details help if several editions are installed.
- Install the game on the new PC, sign in to the same account, and let the launcher complete its initial synchronization.
- Start the game and check the save list before copying anything over. If the cloud save is correct, make a separate backup of that newly downloaded folder.
Common Windows locations include %USERPROFILE%\Documents\My Games, %APPDATA%, %LOCALAPPDATA%, and %USERPROFILE%\Saved Games. Some games use a folder inside their installation directory, a launcher-specific user-data folder, or a publisher folder under Documents. Search by the game’s title, publisher name, or a distinctive save-file extension, and consult the game’s own support documentation when the location is unclear. Avoid copying an entire installation directory as a substitute for finding the actual saves.
Reinstalling Windows or replacing a storage drive
Treat this as a full migration. Before reinstalling, copy likely save folders, configuration files, screenshots or replay files you care about, and any mod profiles to an external destination. If the old drive is still readable, make the backup before formatting it. Cloud synchronization should be considered an additional layer, not your only copy.
After the reinstall, install the relevant launcher and sign in before restoring local files. Launch the game once, close it, then compare the newly created save-folder structure with your backup. Copy only the backed-up files into the matching location. Keep a renamed copy of the new folder until the restore is confirmed.
Moving between PlayStation, Xbox, or Nintendo consoles
Use the platform’s built-in transfer or cloud-save feature when available, and sign in with the same account used on the original console. Keep both consoles powered and connected as required by the platform’s transfer process, and do not delete the old console’s data until the destination has been tested.
Console progress is not automatically interchangeable between every platform, edition, or generation. A game may support cross-progression through a publisher account, while another may keep saves tied to a specific platform. Check the game’s transfer instructions for your exact version. Installed games, downloadable content, screenshots, and save data may also be handled separately, so verify each category you need.
Using a game with server-side or unusual saves
Online games often store characters, inventory, rankings, or campaign progress on the publisher’s servers. In that case, signing in to the correct account may be more important than copying a local file. However, local settings, photo modes, offline profiles, replay files, and configuration data may still require a manual backup.
Some games use one save folder per profile, rolling backups, autosaves, or a single slot that is replaced each time synchronization runs. For these games, make several dated copies before experimenting. Games with mods may also require a mod manager profile, load order, or separate configuration folder to reproduce the old setup.
| Scenario | Primary action | Extra protection | Main risk |
|---|---|---|---|
| New PC with the same launcher | Sign in and allow cloud sync | Copy the old local save folder | Downloading an older or incorrect cloud version |
| Windows reinstall or drive replacement | Back up folders before formatting | Keep a dated external copy | Missing saves stored outside the usual folder |
| New console | Use the platform transfer or cloud-save workflow | Test the game before erasing the old console | Different accounts, editions, or generations |
| Cross-platform move | Check whether the game supports cross-progression | Back up local-only files separately | Assuming cross-play also means shared saves |
| Modded or unusual game | Back up saves and the mod profile | Make multiple dated copies | Version or load-order incompatibility |
What to double-check
Cloud-sync status
Confirm that synchronization completed on the old device and that the timestamp or file state looks current. If a launcher asks whether to use local or cloud data, compare the dates and progress first. When uncertain, preserve both versions by copying the local files before choosing.
Account and edition matching
Use the same platform and publisher accounts where the game requires them. Confirm that the destination is running the same game edition, region, generation, and downloadable-content setup. A save can appear missing when the correct account is signed in but the destination has a different product version.
Save-file integrity
Open several save slots, not just the newest one. Check the campaign location, character inventory, settings, and any important user-created content. If the game crashes or shows an empty save list, close it without saving over the backup and restore one dated copy at a time.
Backup readability
A backup is only useful if you can access it. Keep at least one copy disconnected from the device being replaced, label folders with the game and date, and make sure the external drive or storage account can be opened on the destination device. Do not rely on a shortcut, a launcher download, or an untested archive.
Common mistakes
- Assuming cloud saves are universal: Cloud support can differ by game, launcher, platform, edition, or account. Verify it for each important title.
- Formatting too early: Keep the old device or drive intact until restoration is confirmed.
- Choosing a sync-conflict option without checking dates: The wrong selection can replace a newer local save with an older cloud copy.
- Copying only the installation folder: Saves are often stored separately from game files.
- Forgetting mod data: A save may depend on a particular mod list, load order, or configuration.
- Confusing cross-play with cross-progression: Playing together across platforms does not necessarily mean sharing saves.
- Testing only one save: Check multiple slots and user profiles before declaring the migration successful.
- Overwriting the backup during troubleshooting: Work from a copy and retain the original dated archive.
When to revisit
Use this checklist before every device upgrade, storage replacement, operating-system reinstall, major launcher change, or move between console generations. Recheck the steps after a game changes its launcher, adds cross-progression, introduces a remaster, or receives an update that changes save locations or mod compatibility.
For important games, create a simple recurring routine: save manually, exit cleanly, confirm cloud synchronization, copy the local folder, and label the backup with the date. Before wiping the old device, complete one final test on the destination. Open the game, load more than one save, verify your progress, and only then retire or erase the original hardware.
If you are also changing editions or downloadable content, compare what transfers before buying or reinstalling; our guide to comparing game editions, DLC, and bundles can help. When a patch changes save behavior or compatibility, review the relevant patch notes guide before launching the restored copy.
