Migrate from Mutt to NeoMutt#
Prerequisites#
Install NeoMutt alongside your existing Mutt installation.
Make a backup of your current Mutt configuration.
Key Differences Between Mutt and NeoMutt#
NeoMutt is a fork of Mutt that aggregates long-standing patches and features.
It keeps Mutt compatibility where possible while adding features like Notmuch integration, sidebar, and extra hooks.
Expected result: you understand that most Mutt configuration still works, but NeoMutt adds optional features you can enable.
Config File Compatibility#
Copy your Mutt config to a NeoMutt config file location:
~/.neomuttrc
Start NeoMutt with that file:
neomutt -F ~/.neomuttrc
Expected result: NeoMutt starts using your existing configuration.
New Features in NeoMutt#
Review NeoMutt features in the project README.
Enable features you want in small steps.
Expected result: you can add features without breaking your base config.
Deprecated or Changed Settings#
Start NeoMutt and watch for warnings on startup.
Look up any warnings in the reference documentation.
Expected result: any incompatible settings are identified early.
Testing Your Existing Config#
Run NeoMutt with system config disabled to isolate issues:
neomutt -nF ~/.neomuttrc
Add sections of your config back in gradually if needed.
Expected result: you can pinpoint which settings cause problems.
Common Migration Issues#
Missing optional features because your build lacks certain libraries (IMAP, Notmuch, crypto).
External tool integrations not installed on the new system.
Different config file location or
$folderpaths.
Expected result: you can resolve issues by installing missing dependencies or fixing paths.
Running Mutt and NeoMutt Side by Side#
Keep separate config files, for example
~/.muttrcand~/.neomuttrc.Start each client with its own config:
mutt -F ~/.muttrc
neomutt -F ~/.neomuttrc
Expected result: you can compare behavior while migrating without downtime.