Final Fantasy IX needs a particularly cautious backup workflow because the Steam save directory is named EncryptedSavedData and modern mod setups may write additional derived files into the same area. The safest baseline is an untouched copy of the whole directory before any editor or Memoria operation. That gives you a known-good source even if a mod creates exported slot files or changes which file is loaded. The Microsoft Store release uses WGS instead, so SaveEditor does not present a simple rename-and-copy operation as universal compatibility.
Prepare the source PC
On the source system, identify the actual Final Fantasy IX save root: Windows: Steam: %USERPROFILE%AppDataLocalLowSquareEnixFINAL FANTASY IXSteamEncryptedSavedData ; Microsoft Store: %LOCALAPPDATA%Packages39EA002F.FINALFANTASYIX_n746a19ndrrjgSystemAppDatawgs. The expected file/folder pattern is Steam master save commonly includes SavedData_ww.dat; Memoria/modded setups may create additional derived files.. 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, Microsoft Store. Steam and Microsoft Store paths are different. Memoria or other mods can add extra files beside the original save and should not be confused with the untouched source data. 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 EncryptedSavedData folder on Steam before installing a save editor or mod framework. On Microsoft Store, back up the WGS container rather than renaming arbitrary files into the Steam directory. 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 and Xbox Cloud are documented for their corresponding editions. 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 Steam release stores an encrypted save-data set under LocalLow. Microsoft Store uses WGS. Mod frameworks can add their own companion or exported files, so a clean backup should preserve the original game-owned data before modded copies. Compatibility note: A Steam master save and Microsoft WGS container are not interchangeable by filename alone. Mod-created Memoria files may depend on the mod version and should be kept separate from the original backup. If the destination does not see the transferred progress, If an edit or restore seems ignored, disable competing cloud restoration temporarily, verify whether the game is loading the original or a Memoria-derived file, and use Load rather than assuming Continue points to the intended slot. Verify game edition/version, store, profile IDs, redirected folders, and mod/DLC dependencies before editing the save itself.
Verification context: Reviewed against current PCGamingWiki Final Fantasy IX save path and current community notes describing SavedData_ww and Memoria-derived files.