How to Transfer Game Saves to a New PC

Do not retire your old PC as soon as a transfer archive finishes copying. The important result is a playable checkpoint on the new installation, with your original progress still recoverable. Work from a known-good source and test one save before moving everything.

Confirm the source while it still works

On the old PC, open the intended checkpoint and note the character, quest, world or other progress marker. Record the exact game build, storefront and relevant DLC or mods. Then exit normally and make a separate copy of the active save directory.

Use the game’s documented path. Different titles store local progress in different user-data locations, as illustrated by the official Cyberpunk 2077 and Baldur’s Gate 3 instructions. Copying the installation folder alone is not a universal save-transfer method. 1 2

Prepare the destination independently

Install and launch the intended version of the game on the new PC. Where appropriate, create a small test save to confirm that the installation can write and load local progress. Exit and identify the files that changed.

Back up the destination too. Even a new computer may already contain a useful test character or a synchronized copy you should preserve before overwriting. Compare the game edition, build and dependencies with the source rather than assuming every PC installation is equivalent.

Build a readable transfer archive

Prepare the archive from the source backup, not from a folder the game is actively updating. Preserve the original directory structure and companion files. Include a note with the checkpoint, version, storefront, dependencies and the source path you verified.

Use nonpersonal labels for profiles and remove unnecessary account information from any archive intended for public sharing. A private migration package and a publicly distributed save have different privacy considerations.

Transfer one checkpoint first

1. Keep independent source and destination backups.
2. Extract the archive temporarily and confirm that the expected files are present.
3. Resolve any edition, build or dependency questions before treating the package as compatible.
4. Add one identifiable save to the verified destination location without discarding same-named originals.
5. Load it and compare actual progress with your notes from the old PC.
6. Create a separate save on the new machine, exit and reload it.

Only move the rest of the archive after that limited test succeeds. Keep a record of any rollback or difference rather than treating every loadable file as the exact checkpoint you intended.

Check synchronization before clearing the old device

Do not mix a manual transfer and an unfamiliar cloud-recovery workflow without understanding which files each action will replace. Preserve local data before answering sync prompts. Verify the result on the new machine and retain an independent archive before erasing or selling the old computer.

A successful transfer is a specific result on a specific setup. It does not prove compatibility with every storefront or platform, and it should not depend on a single copy that disappears when the old PC is reset.

Frequently asked questions