so ive been using Log4OM for a while now for general logging and i really like it, the interface is pretty clean and the integration with clublog and LoTW works well for me. but every time a contest rolls around everyone says just use N1MM and i get it, N1MM is basically the standard for contesting but then i end up with my log split across two programs and its kind of a mess trying to merge things afterward.

lately ive also been doing more FT8 and WSPR through WSJT-X and that adds a third log to deal with. WSJT-X writes its own ADIF and i import it into Log4OM but sometimes there are dupes or the timestamps are slightly off and it just gets annoying. anyone else running this kind of setup or have you found a cleaner way to handle it? i thought about just going all in on N1MM for everything but it feels overkill for a casual tuesday night operating session when im just working some DX on 20m.

also not sure if Log4OM can do SO2R stuff if i ever go down that road, probably a question for another day

yeah i ran into the exact same thing a while back. what i ended up doing was just accepting N1MM as my contest logger and Log4OM for everything else and writing a little import routine so after each contest i clean up the N1MM adif export and pull it into Log4OM manually. takes maybe 10 minutes after a big contest and honestly it's not that bad once you get the workflow down. the timestamps have never been a problem for me doing it that way.

the WSJT-X thing is more annoying tbh. i have it set to auto-log to a dedicated adif file and i import that into Log4OM every few days. dupes show up but Log4OM flags them so i just skip and move on. not perfect but it works. i dont think theres really one program that does all three things well, N1MM is a contest machine but for casual logging it feels like driving a semi to the grocery store

Log4OM can actually handle contest logging to some degree, they added a contest module a couple versions back but i tried it for a state QSO party and gave up pretty fast. the rate display is nowhere near what N1MM gives you and some of the multiplier tracking felt off. for anything serious just use N1MM, thats what its built for.

for the WSJT-X integration there is a UDP logging option that can send QSOs in real time to some logging programs, Log4OM supports it i think, might be worth digging into that instead of doing manual adif imports. cuts down on the duplicate problem at least in theory, ive never actually tested it myself so take that with a grain of salt