Use the MSFS 2024 Legacy Importer safely: choose the right folders, transfer compatible 2020 add-ons and fix packages that fail to load.
On PC, point the MSFS 2024 Legacy Importer at your MSFS 2020 Community folder, set the active MSFS 2024 Community folder as the destination, scan, select only add-ons known to be compatible, then import and test them in small batches. The tool transfers packages; it cannot convert incompatible code, dependencies or licences.
What does the MSFS 2024 Legacy Importer transfer?
The Legacy Importer is a migration aid for unencrypted Community packages, not a universal add-on converter. It transfers an add-on's existing files into the MSFS 2024 package location without rewriting aircraft systems, models, gauges or external programs for the newer simulator.
MSFS 2024 can read many packages created for MSFS 2020, but compatibility varies considerably by add-on type. Our detailed compatibility guide for 2020 aircraft, scenery, liveries and utilities explains which packages are sensible candidates.
Use the importer only for PC Community content. Marketplace-managed products should be installed or enabled through My Library in MSFS 2024; do not copy them from the MSFS 2020 Official packages area. Xbox Series X|S, PlayStation 5 and PS5 Pro do not allow a desktop importer to write to simulator storage.
How do I import MSFS 2020 add-ons safely?
The safest method is to preserve the MSFS 2020 installation, copy a few packages at a time and verify each batch inside MSFS 2024.
- Back up the source packages. Keep an untouched copy of the MSFS 2020 Community folder, and update each add-on to its latest supported 2020 release before migration.
- Close both simulators. Also close add-on managers or utilities that could be changing files while the importer scans them.
- Confirm the active folder paths. Do not assume the first Community folder found by Windows is the one MSFS 2024 uses. Custom installations and moved package libraries often leave old folders behind. If necessary, follow our method for finding the active Community path through UserCfg.opt.
- Choose the correct source and destination. Set the source to the MSFS 2020
Communityfolder and the destination to the MSFS 2024Communityfolder. Never select either simulator's Official packages directory. - Scan and review the results. Deselect Marketplace content, external applications and anything for which a native MSFS 2024 edition is already installed. The native package should take precedence.
- Import a small batch. If the importer offers copy or move operations, choose copy. Moving removes the working 2020 installation, while a shared writable folder can let one simulator's installer damage the other one's packages.
- Start MSFS 2024 and test each item. Check that aircraft appear in the selector, liveries attach to the intended model and scenery loads at the correct location. For aircraft, test avionics, controls and sounds rather than assuming that appearing in the menu proves compatibility.
- Remove failures before importing more. Delete the failed package from the MSFS 2024 Community folder, not from the 2020 source. Retesting after every batch makes the conflicting package much easier to identify.
An import is normally a one-time copy, not ongoing synchronisation. If the MSFS 2020 package is updated later, install a dedicated MSFS 2024 release where available rather than repeatedly overwriting the imported files.
Which add-ons should I transfer?
Transfer self-contained packages with confirmed MSFS 2024 compatibility; reinstall or replace anything that depends on an external executable, protected content or simulator-specific systems.
| Add-on type | Recommendation | Main checks |
|---|---|---|
| Liveries | Usually good candidates | Correct base-aircraft reference, model matching and thumbnail behaviour |
| Simple scenery | Often transferable | Missing libraries, elevation changes and clashes with revised default scenery |
| Airports | Test individually | Duplicate buildings, runway alignment, jetways, navigation data and services |
| Aircraft | Import only when compatibility is confirmed | Avionics, WASM components, flight model, sounds, animations and dependencies |
| Traffic, weather and external utilities | Install a 2024-compatible edition | External programs and simulator connections are not converted by the importer |
| Marketplace-managed packages | Use My Library | Ownership, platform availability and publisher compatibility |
A mistake we see constantly is importing the entire 2020 Community folder in one operation. One outdated library or aircraft can then cause long loading, a start-up failure or apparently unrelated missing objects throughout the simulator.
Why is the imported add-on missing or broken?
An imported add-on usually fails because MSFS 2024 is reading a different Community folder, the package is nested incorrectly, a dependency is absent or the add-on is not genuinely compatible.
- Nothing appears in the simulator: verify the destination path and extract any archive first. A normal package has files such as
manifest.jsonandlayout.jsoninside its package root, not beneath an extra duplicate folder. Our PC package-installation and conflict checks cover the correct structure. - MSFS 2024 hangs or closes during loading: remove the last imported batch and start again with one package at a time. Duplicate package identifiers, incompatible modules and missing dependencies are common causes.
- The aircraft appears but systems do not work: the menu entry and model may be readable while its avionics, gauges or compiled components are incompatible. The importer cannot repair these; use a developer-supplied MSFS 2024 build.
- Textures or objects are missing: install the required library if it is compatible, or remove the package. Pink textures, invisible models and empty scenery areas usually indicate missing or invalid asset references.
- An airport has duplicate buildings or terrain faults: check for another edition of the same airport and compare it with the revised MSFS 2024 default scenery. Keep only one replacement package enabled.
- An external utility no longer connects: reinstall a version explicitly intended for MSFS 2024. Copying its Community component does not transfer its desktop application, configuration or licence activation.
If a package still fails when installed alone with all documented dependencies, treat it as incompatible. Reverting the import is safer than editing its manifest or layout files without instructions from the add-on developer.