so ive been using N1MM pretty much exclusively for a few years now and its great for contests obviously but honestly outside of contests i find it kind of clunky for just day to day logging. the interface feels like it was designed by someone who only ever thinks about contests which i guess it was

anyway a buddy at the club keeps telling me to try Log4OM and i downloaded it a couple weeks ago but havent really dug into it yet. main thing i care about is decent WSJT-X integration since i do a lot of FT8, and also being able to pull in my old N1MM logs without losing everything. anyone actually made that switch or are you running both? i kind of dont want to run two separate programs if i can help it but maybe thats just how it goes

also does Log4OM handle contest logging at all or is that still really N1MM territory

I've been running Log4OM for about two years for general logging and it works really well with WSJT-X, you just point WSJT-X at it via UDP and contacts come in automatically, pretty seamless. The ADIF import from N1MM worked fine for me, had maybe a dozen duplicate issues i had to clean up manually but nothing major.

For contests though I still fire up N1MM. Log4OM has some contest support but its pretty limited compared to N1MM and honestly for anything serious like a major CW or SSB contest you'd be doing yourself a disservice not using N1MM. So yeah i do run both but the workflow isnt that bad once you get used to it, WSJT-X logs to Log4OM day to day and then when a contest weekend comes around i switch the UDP port over to N1MM and back again after. Takes like 30 seconds.

log4om has gotten a lot better recently, the v2 rewrite was a big deal. WSJT-X integration works fine, cloudlog-style features, looks decent. but yeah if youre contesting N1MM is still the standard, nobody at a serious multi-op is gonna run anything else

the import thing should be ok but i'd test it on a copy of your logs first before you do anything permanent just in case