Back up your SAP GUI settings before reinstalling Windows

Wiping Windows or moving to a new PC will erase your SAP Logon system list unless you save it first. The good news: it's all in one small file. Back that up and you can restore every system in seconds.

The one file you need

SAP GUI 7.10 and later keep your entire system list in SAPUILandscape.xml, stored here:

%APPDATA%\SAP\Common\SAPUILandscape.xml

Paste that path into the File Explorer address bar to jump straight to the folder. Copy SAPUILandscape.xml somewhere safe — a USB stick, cloud folder, or another drive. That single file holds your folders, servers, routers and logon groups.

There are no passwords in this file — it only stores where to connect, not how to authenticate. That's why it's safe to copy and keep.

Also check for a global file

If your organisation pushes a shared configuration, there may also be SAPUILandscapeGlobal.xml. In most cases you only need your personal SAPUILandscape.xml; back up the global one too if you maintain it.

Restoring after reinstall

You have two ways to restore, depending on the situation:

If the new machine has no systems yet

Install SAP GUI, close SAP Logon, then copy your saved SAPUILandscape.xml back into %APPDATA%\SAP\Common\, overwriting the empty one. Reopen SAP Logon and everything is back.

If the new machine already has some systems

Don't overwrite — you'd wipe the systems already there. Instead, use SAP Logon Transfer to import your saved file: it merges the two lists, adds only what's new, blocks duplicates, and writes a backup first. See moving SAP GUI to a new computer.

Make it a habit

Rather than remembering to copy the file manually, you can push a timestamped backup to your OneDrive, Google Drive or Dropbox folder with SAP Logon Transfer's cloud backup. Next reinstall, restore is one click — no hunting for the file.

Quick checklist

• Copy %APPDATA%\SAP\Common\SAPUILandscape.xml before wiping Windows.
• Store it somewhere off the machine (USB, cloud, another drive).
• Restore by copying it back (empty target) or importing it (existing systems).
• No passwords are involved, so the backup is safe to keep.