MMM - Move Mods Masterfully.
This is a tool for migrating modding instances (modlists) between mod managers.
Only Windows is supported!
- Fully automated migration
- Automatic detection of used game folder
- New instance is customizable
- Migrate to existing instances to merge two instances into one (experimental)
- Support for global and portable MO2 instances
- Automatically download and install MO2 for portable MO2 instances
- Automatically converts Vortex conflict rules to a MO2 loadorder and vice versa
- Also supports separate file conflicts and .mohidden files
- Uses hardlinks by default when source and destination are on the same disk to save on space
- Can be disabled in File > Settings > Use hardlinks [...]
- What are hardlinks?
- Automatic detection of Windows path length limit
- Windows paths are limited to 255 characters which can cause issues for mods with long paths
- MMM will ask at the start to disable that limit when not already disabled
| Migrated | Not Migrated |
|---|---|
| Mods including basic metadata required for the link to Nexus Mods: version, file name, mod id, file id, game id | Advanced metadata not required for link to Nexus Mods: author, description, category |
| Tools/Executables (eg. xEdit, Bodyslide, SSE-AT, etc.) including link to installed mod (if any), working directory, start arguments | Custom tool icons |
| Conflict rules | Overwrite folder (MO2 -> Vortex) |
| Separate file conflict rules | LOOT rules (Vortex -> MO2 and vice versa) |
| Plugin loadorder: plugins.txt and loadorder.txt | Downloads and link to download folder |
- Enderal (+ Special Edition)
- Fallout 3
- Fallout 4
- Fallout: New Vegas
- Oblivion (not the Remastered version)
- Skyrim (all versions incl. VR and GOG)
- Vortex
- Mod Organizer 2
- Cannot migrate from/to Vortex if it is used in "Shared" mode (Vortex > Settings > Vortex)
To migrate an instance, follow these steps:
- Select the game of the instance you want to migrate.
- Select the source mod manager.
- Enter the required information for the respective mod manager.
- Click on "Load instance..." to load and display the source instance.
- Select whether you want to create a new instance or want to migrate to an existing one (experimental).
- Select the destination mod manager (may be the source mod manager to duplicate an instance).
- Either customize the destination instance as desired or select one similar to the source.
- Click on "Migrate" and wait for it to finish.
- If there are errors, check them carefully and (where appropiate) follow their recommendations and instructions.
Yes, but before deleting the old instance make sure that the migrated instance works fine and that there were no errors during the migration. I take no responsibility for modlists that get deleted without verifying that the destination instance works!
This is fully intentional and expected when migrating a MO2 instance with a non-empty overwrite folder to Vortex, as Vortex does not have anything similar (generated files stay in the game folder). As suggested in the error message, to solve this, create a mod from the files in the overwrite folder and rerun the migration. Do this by right-click > Create mod from overwrite on the mod "Overwrite" at the very bottom of your modlist in MO2.
Please check the length of the mentioned file path: If it is longer than 255 characters, you didn't fix the path limit when prompted after starting MMM. If the path is shorter than 255 characters, please create an issue or create a post in #support on our Discord server.
No, not at the moment. Please see What gets migrated and what not for a full up-to-date list.
If you encountered an issue/error or have a suggestion, open an issue with sufficient information.
- Install uv
- Python is not required to be installed as uv will download and install it for you
- Clone repository and its submodules by running the following command
git clone https://github.com/Cutleast/Mod-Manager-Migrator --recurse-submodule - Open a terminal in the cloned repository folder
- Run the following command to init your local environment and to install all dependencies
uv sync
- Open a terminal in the root folder of this repo
- Execute main file with uv
uv run src\main.py
- Run
build.batfrom the root folder of this repo. - The executable and all dependencies are built in the
dist/MMM-Folder and get packed in adist/Mod Manager Migrator v[version].zip.
Make sure to follow the steps under Code contributions above to install all requirements, including the Qt tools to translate this app.
- To generate a translation file for a new language, copy the following line in update_lupdate_file.bat:
--add-translation=res/loc/de.ts ^, insert it directly beneath it and change thedevalue to the short code of your language. For example, to generate a file for French, the new line would look like this:--add-translation=res/loc/fr.ts ^ - Run
update_lupdate_file.bat && update_qts.batto generate the translation file for your language. - Open the translation file in Qt Linguist with
uv run pyside6-linguist res/loc/<language>.ts, eg.uv run pyside6-linguist res/loc/fr.ts. - Translate MMM and save the file with Ctrl+S.
- For the compiled language file to be bundled with the app, you have to add the compiled file under
<!-- Localisation Files -->in resources.qrc. For example, for French:<file>loc/fr.qm</file>. - For your language to show up in MMM's settings: add a line, similar to the existing languages, under
class Language(BaseEnum):in localisation.py. For example, for French:French = "fr_FR". - Optional: Run
compile_qts.bat && uv run src\main.pyand change the language in Settings to your translation (and restart) to see your translation in action. - Create a pull request from your changes and I will check over it and merge it if there are no issues with it.
- Code by Cutleast (GitHub | NexusMods)
- Icon, modpage images and idea by Wuerfelhusten (NexusMods)
- Qt by The Qt Company Ltd
- FontAwesome Icons by FontAwesome
See licenses.py for a full list of used libraries, dependencies and their respective licenses.