Import & Upload

There are three main ways to get setups into Setup Stash:

1. Browse local setups from your LMU Settings folder with Sync Agent
2. Upload a .svm file manually in the browser
3. Pull from Team Setups into your personal Stash

Browse local setups with Sync Agent

This is the best option when your setups already exist on your PC.

What happens

1. In Setup Stash, start Browse local setups
2. Sync Agent scans your LMU setups folder
3. MyLMU shows a checklist of discovered .svm files
4. You select which files to import
5. Sync Agent uploads the selected files into Stash

Why this flow is selective

Setup Stash is designed to let you choose which local setups become part of your library. You do not need to dump every setup file from your Settings folder into MyLMU.

Requirements

• Sync Agent installed and connected
• Setup folder configured in the agent
• Pro access on the MyLMU account connected to the agent

If Sync Agent is not connected or the setup folder is missing, the browse flow cannot complete. See Troubleshooting.

Manual browser upload

Use this when a .svm file is already on disk but you do not want to browse the whole folder.

Steps

1. Open Setup Stash
2. Choose Upload
3. Select the .svm file
4. Review or set metadata such as name, track, car, provider, and intent
5. Confirm the upload

Layout note

During upload, MyLMU maps the setup to an LMU Settings-relative path. If the guessed layout is wrong, you can correct it later in setup details before using Send to my LMU folder.

Pull from Team Setups

You can copy a version from Team Setups into your own Stash.

This is useful when:

• a teammate shares a strong baseline
• you want to test a team setup privately
• you want to continue editing a team setup as your own version chain

If there is already a Stash ↔ Team Setups link, MyLMU can reuse that durable pair instead of creating a disconnected duplicate.

Duplicate vs new version behavior

Setup Stash tries to preserve useful history instead of creating noise.

Common outcomes

This is why importing the same untouched file repeatedly should not create version spam, while an updated file for the same LMU location should extend the version history you already have.

Best practice

• Use Browse local setups when you want to build your library from your LMU folders
• Use Upload for one-off files you already have
• Use Pull from Team Setups when the setup starts as a team collaboration

Related

• Getting Started
• Send & Sync
• First-Time Sync Agent Setup
• Team Setups