Learn how to transfer MSFS 2020 controller profiles to MSFS 2024 by safely rebuilding axes, buttons, dead zones and sensitivity.
You cannot reliably import a built-in MSFS 2020 controller profile into Microsoft Flight Simulator 2024. The two simulators store and interpret control presets differently, so the safe method is to record each device’s assignments, create a separate MSFS 2024 profile for each peripheral, then rebind and test the controls manually.
Can MSFS 2024 import a 2020 control profile automatically?
No—MSFS 2024 has no dependable built-in process that converts a custom MSFS 2020 control profile into a working 2024 preset. Signing in with the same Microsoft or Xbox identity does not cross-convert profiles between the two simulators.
Copying local application data or cloud-cache files is not a reliable workaround. Device identifiers, control actions and profile structures may differ, while cloud synchronisation can overwrite copied data. Our explanation of what an MSFS 2020 control backup can and cannot recover covers the limits of backups: they are useful protection for 2020, not a migration tool for 2024.
What should I record before moving to MSFS 2024?
Record every assignment, curve and reversal while the working MSFS 2020 installation is still available. Do not uninstall it or reset its cloud data until the replacement setup has been tested.
- The selected profile name for each joystick, yoke, throttle, pedal set, keyboard and gamepad.
- Pitch, roll, rudder, throttle, propeller, mixture, spoiler and brake axes, including any reversed axes.
- Sensitivity, dead-zone, neutral, extremity and reactivity settings shown for each device.
- Buttons, hat switches, camera controls, modifier buttons and multi-button combinations.
- Separate engine assignments, throttle detents and aircraft-specific profiles.
Screenshots or phone photographs are usually more useful than copying profile files because they provide a readable reference. A complete cockpit is not stored as one universal preset; read our summary of how MSFS 2024 separates profiles by peripheral before documenting the setup.
How do I rebuild the profile in MSFS 2024?
Rebuild the controls one peripheral at a time, beginning with the primary flight axes. This makes duplicate assignments and reversed inputs much easier to identify.
- Keep MSFS 2020 available. Open its control settings, select each device and use the assigned-controls filter to capture the active mappings.
- Connect the same hardware to MSFS 2024. Confirm that the simulator recognises the correct device rather than treating it as a generic controller.
- Create a custom preset. Select the individual peripheral and duplicate or create a profile instead of relying on a factory preset. Our MSFS 2024 control-configuration walkthrough explains the profile and assignment process.
- Bind the flight axes first. Assign pitch and roll to the stick or yoke, rudder and toe brakes to the pedals, then throttle and other engine controls. Choose an axis action, not an increase/decrease button action.
- Check direction and full travel. Move each control through its complete range. Use the binding’s reverse option when an axis moves backwards; do not try to correct reversal with an extreme sensitivity curve.
- Add buttons and views. Recreate trim, brakes, flaps, landing gear, autopilot disconnect, camera and other frequently used functions before less important commands.
- Remove duplicate assignments. Default mappings may place the same command on several peripherals. Search by input or command and clear any binding that causes a second device to interfere.
- Save and test the preset. Verify control-surface movement from an external view, test brakes and throttles on the ground, then change aircraft and confirm that the intended profile remains active.
Why do recreated controls behave incorrectly?
Most failures come from the wrong profile being active, a digital command being used instead of an axis, or the same action being assigned twice.
| Symptom | Likely cause | Fix |
|---|---|---|
| An axis does nothing | The wrong device or preset is selected | Select the physical peripheral and confirm that its custom profile is active |
| Throttle jumps between idle and full power | It is bound to increase/decrease commands | Replace those bindings with the appropriate throttle-axis action |
| Aircraft rolls or yaws without input | Duplicate binding or hardware noise | Clear duplicate axes, then add only enough dead zone to stop the noise |
| Control moves in the wrong direction | The axis direction is reversed | Enable the reverse option for that specific binding |
| Buttons trigger two actions | One input is assigned in more than one active layer or profile | Search by input and remove the unwanted assignment |
| Bindings change with the aircraft | An aircraft-specific profile is overriding the general setup | Check the active profile after loading that aircraft |
Do sensitivity and dead-zone settings transfer?
No, sensitivity and dead-zone settings should be recreated and tuned in MSFS 2024. Even when the same numerical values are available, they may not produce an identical response because the control system and aircraft behaviour are not identical.
Start with a small dead zone sufficient to stop unwanted movement, confirm that the control reaches its full range, and adjust the response curve last. Our guide to sensitivity, dead zones and response curves covers the tuning process without duplicating it here. Aircraft with throttle-detent calibration may also require a separate calibration through that aircraft’s cockpit tablet or settings.
What if I am also changing platform?
The transfer remains manual, and only hardware supported by the destination platform can be recreated. A saved profile cannot make a PC-only joystick, driver or controller utility work on a console.
MSFS 2020 is limited to PC and Xbox, whereas MSFS 2024 is also available on PlayStation 5. Moving a 2020 setup to MSFS 2024 on PS5 therefore means starting with fresh profiles for compatible PlayStation hardware rather than importing an existing PC or Xbox configuration.