So ive been using Log4OM for a couple years now for general logging and i really like it, the interface makes sense to me and the QSL tracking stuff is solid. But every time a contest rolls around everyone seems to be running N1MM and honestly i get why, it just handles contest stuff way better. My question is whether people are actually running both on the same machine and swapping between them or if theres a cleaner way to handle this.

Right now my workflow is kind of a mess. I do WSJT-X for FT8 which logs to Log4OM fine, but when i jumped into the ARRL DX contest last month i spun up N1MM and now i have logs in two places and im not totally sure how to merge them without creating duplicate entries. I exported the N1MM log as an ADIF and tried importing it into Log4OM but a few things looked weird, some of the exchange data didnt map right and i ended up with some contacts missing the RST fields.

Is there a standard way people handle this or am i overcomplicating it. Would love to hear how other people set up their shack software, especially if youre doing a mix of digital modes and contesting.

yeah this is pretty much the classic problem and honestly there isnt a perfect answer. I run N1MM for any serious contesting, no real substitute for it when youre trying to keep a rate going and need the dupe checking to be instant. But for day to day stuff and FT8 i keep WSJT-X feeding into Log4OM. The ADIF merge headache you described is real though.

What i started doing is just accepting that N1MM is its own silo during a contest and then after the contest is over i do the ADIF export carefully — make sure youre exporting with the full cabrillo fields included and then use the ADIF master import in Log4OM rather than the quick import. Theres a field mapping screen that comes up if you go through the right menu path and you can manually tell it where to put the exchange data. Takes maybe 20 minutes after a contest but then everything ends up in one place. The RST issue is usually because N1MM stores sent and received differently than Log4OM expects, you might need to remap RST_SENT and RST_RCVD manually on that screen.

Not glamorous but it works.

I actually just use N1MM for everything including daily logging and FT8 integration. People sleep on it for general use but it handles WSJT-X via the UDP port just fine and logs everything automatically. Took me an afternoon to get the UDP setup dialed in but once it was working i stopped thinking about it. The log format isnt as pretty as Log4OM and the interface is clearly designed around contesting but for me its not worth managing two programs and two databases honestly.