so ive been running N1MM for contests for years now and it does that job fine honestly, but for everyday logging and digital modes its kind of a pain to deal with. the interface is clearly built around contesting and when im just sitting down to work some FT8 on a random tuesday evening it feels like overkill and half the fields dont even apply.

started poking around Log4OM a few weeks ago and its got a totally different feel to it, more like a general logbook that you bolt other stuff onto. WSJT-X integration actually works pretty cleanly once you get the UDP port sorted out, took me maybe 20 minutes to figure out why it wasnt auto-logging and it turned out i just had the wrong port number in the WSJT-X settings, classic.

my question is whether anyone runs both side by side — like N1MM for when a contest weekend comes up and Log4OM as the daily driver. do you bother syncing the logs between them or just keep them totally separate? i feel like having two separate logs is gonna drive me crazy eventually but maybe thats just how people do it

yeah thats pretty much exactly what i do. N1MM stays installed purely for contests, i dont even open it otherwise. Log4OM handles everything day to day and the WSJT-X hookup is solid once its configured. i did mess around with trying to import N1MM ADIF exports into Log4OM after contest weekends but honestly the duplicate checking got annoying and i just gave up and keep them separate now. two logs, whatever, LoTW sees everything anyway so for confirmation purposes it doesnt really matter.

the one thing i will say is Log4OM's cluster integration is nicer for casual DXing, N1MM's bandmap is better for contesting obviously but Log4OM just feels less hostile when youre not in competition mode if that makes sense

I tried to make Log4OM my everything app for about six months and kept bouncing back to just using N1MM even for non-contest stuff because I already know where everything is. Probably not the answer you're looking for but there's something to be said for just knowing a piece of software really well even if it wasnt designed perfectly for your use case. The WSJT-X logging through N1MM works fine too if you set up the right macros, its not as seamless but it gets the job done. That said I know guys who swear by Log4OM and think N1MM is a dinosaur so probably just comes down to what you started with.