Dragon Quest XI has an uncomplicated-looking Saved/SaveGames path, but the critical backup detail is edition identity. The original Windows release and Dragon Quest XI S are not merely storefront labels for the same executable, so SaveEditor does not collapse them into one compatibility claim. A good backup includes the full SaveGames folder plus a note of which edition created it. This prevents a perfectly valid save from being diagnosed as corrupt when the real problem is that it belongs to a different release.
Prepare the source PC
On the source system, identify the actual Dragon Quest XI save root: Windows: %USERPROFILE%DocumentsMy GamesDRAGON QUEST XISavedSaveGames. The expected file/folder pattern is Unreal Engine save files beneath SavedSaveGames; exact generated filenames can vary with slot/profile context.. 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. The 2018 PC release and Dragon Quest XI S are separate products with different data expectations. This hub documents the original Dragon Quest XI URL from the project plan. 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 the entire SavedSaveGames directory and label it with the exact game edition and build. Keep configuration/mod backups separately so a gameplay save can be restored without changing unrelated settings. 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 is documented; OneDrive can also affect Documents when backup is enabled. 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 original Windows release uses an Unreal Engine Saved/SaveGames tree beneath Documents. It is distinct from later Definitive Edition products and should not be mixed across editions. Compatibility note: Do not assume a save from Dragon Quest XI S or a console edition is compatible with this original PC release. Edition identity is part of the backup metadata. If the destination does not see the transferred progress, If progress is not detected after a restore, verify that the installed title is the same edition and that Documents/OneDrive points to the location you backed up. Verify game edition/version, store, profile IDs, redirected folders, and mod/DLC dependencies before editing the save itself.
Verification context: Reviewed against current PCGamingWiki Dragon Quest XI save location and cloud documentation.