Kingdom Come: Deliverance II preserves the useful Windows Saved Games convention but moves into its own kingdomcome2 tree. That separation should be respected during backups: a similarly named save from the first game is not evidence of compatibility. The cloud situation also differs by storefront, with current PCGamingWiki coverage noting a GOG Galaxy cloud limitation. SaveEditor therefore recommends a local dated copy even for players who normally rely on cloud synchronization.
Prepare the source PC
On the source system, identify the actual Kingdom Come: Deliverance II save root: Windows: %USERPROFILE%Saved Gameskingdomcome2saves. The expected file/folder pattern is Save files beneath the kingdomcome2 saves tree; profile XML remains under Saved Gameskingdomcome2profilesdefault.. 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, Epic Games Launcher, GOG, Microsoft Store. Do not restore first-game files into kingdomcome2 because the directory naming reflects a separate generation. GOG users should not assume Galaxy will provide a cloud backup for this title. 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
Back up kingdomcome2saves locally even if cloud synchronization is enabled. Keep profilesdefault separately if configuration preservation is also important. 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
Steam Cloud, Epic cloud, and Xbox Cloud are documented. PCGamingWiki notes GOG Galaxy cloud is unavailable due to its cloud-save limit. 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
The sequel intentionally uses a kingdomcome2 root, keeping it separate from the first game. Storefront cloud support differs; GOG Galaxy cloud is documented as unavailable because of its cloud save limit. Compatibility note: The sequel’s saves are version-sensitive and should be kept with notes about patches/DLC/mods. First-game save compatibility is not implied by the similar folder structure. If the destination does not see the transferred progress, If a save disappears after switching storefront or machine, inspect the local Saved Games path first and confirm whether the cloud service actually supports this edition/storefront. Verify game edition/version, store, profile IDs, redirected folders, and mod/DLC dependencies before editing the save itself.
Verification context: Reviewed against current PCGamingWiki Kingdom Come: Deliverance II save paths and cloud-support notes.