so ive been using Log4OM for about two years now as my everyday logger and i really like it for general stuff, qsl tracking, the DXCC counter, all that. but every time contest season rolls around i end up switching back to N1MM and it feels like im managing two separate shack lives. someone at the club mentioned theres a way to get Log4OM and N1MM to play nice together or at least sync logs after the fact but honestly i couldnt get it to work without duplicates showing up everywhere.

the other wrinkle is WSJT-X. i run FT8 pretty regularly and right now WSJT-X is logging to Log4OM via UDP which works fine day to day, but during a contest i want those FT8 QSOs going into N1MM. every time i try to redirect the UDP port i either break one or the other or both. feels like there should be a cleaner workflow here and maybe im just overthinking it but i dunno.

anyone figured out a setup that doesnt require you to basically reconfigure everything when a contest weekend comes up? or do most contesters just accept that N1MM is its own thing and do a manual ADIF import after?

yeah the two-logger problem is pretty much just a fact of life for a lot of people. what i do is keep N1MM completely separate and just let it do its thing during the contest, then when its over i export the ADIF out of N1MM and import into Log4OM. you do get duplicates sometimes but Log4OM has that duplicate checking on import, just make sure you have it set to update existing records rather than skip or create new ones or whatever the setting is called, i forget the exact wording.

for the WSJT-X thing during contests — honestly i just change the UDP port in WSJT-X settings to point at N1MM's port (2237 i think, maybe double check that) and then when the contest is done i flip it back. takes like 30 seconds once you know where the setting is. bit annoying but it works and i havent had it break on me. the bigger issue is N1MM doesnt always score FT8 QSOs right depending on the contest rules so worth checking that after.

i ran into this exact thing last year during CQWW. ended up with like three different log files and spent more time sorting it out than actually operating which was frustrating. what i've heard from a few people is that Log4OM 2 has better contest support than the original but i never really dug into it because by that point N1MM was already working and i didnt want to mess with it mid-contest weekend.

one thing that did help me was just accepting that WSJT-X during a contest is kind of its own animal. i run it pointed at N1MM and then after the contest i do a careful ADIF merge. theres a thread somewhere on the Log4OM groups.io that goes into the duplicate handling in detail, might be worth a search over there because the guys who wrote the software actually respond which is nice.