Moving to a new console, reinstalling a PC game, or recovering after a storage failure does not have to mean starting over. This checklist explains how to back up game saves, verify cloud synchronization, transfer progress where supported, and reduce the risk of overwriting a newer save with an older one.
Overview
Game progress can be stored in several different places: on the device itself, in a platform cloud service, in a publisher account, or inside a game-specific folder. These systems are not interchangeable. A game may support cloud saves without supporting cross-save between platforms, while another may link progression to an account but keep local settings, replays, or single-player files separate.
Before moving anything, identify three details: where the save is stored, which account owns it, and whether the destination version can read it. Also distinguish cross-save from cross-buy. Cross-save means progress can follow an account across supported devices. Cross-buy concerns access to the game itself and does not necessarily transfer saves.
| Method | What it can do | Limits and risks | What to check |
|---|---|---|---|
| Local save | Stores progress on the console, PC, or storage drive | Can be lost through deletion, corruption, hardware failure, or reinstalling | Save location, file format, and whether the game uses more than one file |
| Cloud save | Synchronizes supported saves through a platform service | May require a subscription, internet connection, or the correct account; conflicts can overwrite data | Sync status, timestamp, supported games, and conflict options |
| USB or external backup | Creates a separate copy when the platform or game permits it | Some consoles restrict manual copying, and a copied file may not work on another device | Platform rules, drive format, encryption, and restore procedure |
| Account-linked progression | Moves eligible progress through a publisher or game account | Often applies only to selected games, modes, or platforms | Linked accounts, supported destinations, and transfer direction |
A reliable backup is more than one copy. When possible, keep the original save untouched, create a second local or external copy, and allow the platform cloud to finish synchronizing. Do not begin a new game on the destination device until you know which save will be selected if a conflict appears.
Checklist by scenario
Before replacing or resetting a console
- Open every important game and confirm that its latest progress has been saved normally.
- Close the game rather than relying on suspended or quick-resume state.
- Connect the console to the internet and wait for cloud synchronization to complete.
- Check the save timestamp on the source device if the platform displays one.
- Review the platform’s backup or transfer tools. If USB copying is supported, use a correctly prepared drive and label the backup with the date and game name.
- Keep the old console powered off but available until the new device has opened the expected save successfully.
When moving between consoles
First establish whether the game supports a platform-to-platform transfer. A shared login alone does not guarantee that a console save can be imported. Some games support cross-save only after linking a publisher account; others limit transfers by platform family, game edition, region, or mode.
Install the same game edition on the destination where possible, sign in with the exact platform and publisher accounts used on the source, and check the game’s own account or cross-progression menu. If the destination asks whether to use a local save or a cloud save, stop and compare timestamps before choosing. When in doubt, preserve the newer file rather than accepting an automatic overwrite.
When moving a PC save
- Quit the game and its launcher completely so files are not being written in the background.
- Check whether the game launcher offers cloud synchronization, then confirm its last-sync status.
- Find the local save folder. Common locations include a game’s installation directory, the user’s documents folder, a saved-games folder, or an application-data directory, but the exact path varies.
- Copy the entire relevant folder to a separate drive or protected folder. Include profile files, configuration files, and backup files only when the game’s documentation indicates they are part of the save system.
- On the new PC, install the same game version, launch it once, exit, and then place the backup in the expected location if manual restoration is supported.
- Rename the destination folder before replacing it. This gives you a rollback copy if the imported save fails.
For more preparation before a PC reinstall, use the same cautious approach described in a PC game compatibility checklist: confirm the game version, launcher, and storage setup before making changes.
When recovering deleted or corrupted progress
Stop playing first. New saves can replace recoverable data or trigger another cloud synchronization. Check the game’s recycle-bin-style backups, the platform cloud, the launcher’s backup files, and any operating-system file history you already use. If a cloud conflict appears, compare dates and device names instead of selecting automatically. Restore a copy to a separate location when possible, then test it before deleting the damaged original.
What to double-check
- Account identity: Verify the console profile, PC launcher account, and publisher account. Family profiles and secondary users may have separate saves.
- Game edition: Different editions, remasters, regions, or generations may store progress differently. Buying or downloading the game again does not automatically make every save compatible.
- Cloud direction: Determine whether synchronization is uploading the local file, downloading a cloud file, or asking you to choose. Never assume the cloud copy is newer.
- Subscription requirements: Cloud storage and online backup features can depend on the platform, game, device, or account plan. Check the current platform rules before relying on them.
- Cross-save scope: Confirm whether the feature covers the whole game, only online progression, or only selected characters and inventory. Offline campaigns may remain device-specific.
- Storage format: A USB backup may be encrypted, tied to one account, or intended only for restoration on the same platform family.
- Save timing: Multiplayer servers may store progression separately from local campaign saves. Allow both the game and platform to finish saving before closing.
If a subscription is part of your backup plan, review the relevant service’s current capabilities rather than relying on an old menu guide. Our comparison of Game Pass, PS Plus, and Nintendo Switch Online can help frame which service features need checking.
Common mistakes
- Starting the game on the new device before securing the original save. This can create a blank save that later replaces the cloud copy.
- Assuming cross-play means cross-save. Playing with friends across platforms does not prove that campaign progress transfers.
- Copying only one visible file. Some games use profiles, slots, shared-world data, or separate metadata files.
- Restoring an old backup without renaming the current destination folder. Keep both until the imported file has been tested.
- Disconnecting during synchronization. A shutdown, launcher exit, or network interruption can leave the cloud and local versions out of step.
- Deleting the old device immediately. Retain it until you have opened the intended save, checked recent progress, and played long enough to confirm normal saving.
- Using unofficial save editors or conversion tools without a backup. They can change file structure and may create files the game cannot read.
When to revisit
Return to this checklist before buying a new console, replacing a PC drive, reinstalling an operating system, lending a device, or switching between platform versions. It is also worth revisiting after a major game update, launcher change, console software update, or account-linking change, because menus and synchronization behavior can move.
Use this short action list each time:
- Save inside the game, then quit it fully.
- Confirm the account and the latest local timestamp.
- Wait for cloud synchronization and check its result.
- Create a separate manual backup if the platform permits it.
- On the destination, compare versions before accepting a conflict.
- Test the restored save before erasing the source device or backup.
Platform policies, supported games, operating-system paths, and cross-save features can change. Treat the game’s current support page and the platform’s current backup instructions as the final check, while keeping your own dated backup as the safeguard that does not depend on a single service.
