so ive been using N1MM for pretty much everything for the past couple years and its great for contests obviously but outside of contest season i find myself kinda fighting it for just regular rag chew logging and working DX. a buddy of mine keeps telling me to try Log4OM for the everyday stuff and only fire up N1MM when theres an actual contest running.

the thing is i also run WSJT-X pretty regularly, FT8 mostly, and i know Log4OM can pull from WSJT-X logs but ive heard the ADIF import can be a little flakey depending on the version. anyone actually using this combo and does it work cleanly or do you end up with dupes and weird entries all over the place. i just dont want to maintain two separate logs that never quite agree with each other, had that problem years ago with some software i dont even remember the name of

also wondering if there's a point where you guys just gave up trying to integrate everything and just picked one program and stuck with it no matter what

yeah this is basically exactly what i do. N1MM stays closed unless im actually in a contest, Log4OM handles everything else. the WSJT-X integration is done through the UDP logging port and once you set it up right it pretty much just works, i havent had dupe issues in a long time. the trick i found is to make sure you're not also logging to an ADIF file in WSJT-X at the same time because then you end up importing the same QSOs twice if you're not careful about it.

the one thing N1MM does that Log4OM just cant match is the contest-specific stuff, rate meters, multiplier tracking, all that. for a serious contest weekend theres really no substitute. but for a random tuesday night working some DX on 17 meters Log4OM is way more pleasant to use honestly.

ive tried switching a few times and always end up back on just N1MM for everything because learning two programs is annoying. probably not the answer you're looking for lol. the ADIF situation with WSJT-X has always been kind of a mess in my experience regardless of what logging software youre feeding it into, theres always some field that doesnt map right or the band gets imported as frequency instead of band name or something dumb like that