so ive been using Log4OM for general day to day logging for about a year now and honestly i really like it for that, the clublog integration works great and the UI doesnt make me want to throw my computer out the window unlike some other software i wont name

but contest season is coming up and everyone keeps telling me just use N1MM for contests, which i get, N1MM is basically the gold standard for that stuff. my issue is i dont really want to maintain two separate logs or manually merge them after every contest. last time i tried importing an ADIF from N1MM into Log4OM after a state QSO party it was kind of a mess, dupes everywhere and some of the exchange data didnt come through clean

also i run WSJT-X on the side for FT8 and that auto-logs to its own file which then i have to remember to import too. so at any given time i have like three sources of truth and none of them fully agree with each other which is driving me nuts

anyone actually have a clean workflow for this or am i just overcomplicating it

yeah this is kind of a known pain point honestly. what i do is just accept that N1MM is the contest logger and Log4OM is the main shack log and after each contest i clean up the ADIF export before importing. takes maybe 20 minutes but you get used to it. the trick with the dupe issue is to make sure youre exporting from N1MM with the full cabrillo fields mapped, sometimes the ADIF it spits out is missing stuff depending on which contest module you were running

for WSJT-X i just have it point to a dedicated log file and i import that weekly, its not perfect but its manageable. the real problem is WSJT-X doesnt export some of the mode subtype stuff in a way Log4OM handles gracefully, FT8 sometimes shows up as just MFSK or something weird. i usually do a find and replace in the ADIF before importing

honestly if youre doing a lot of contesting you might just end up living in N1MM more than you expect and Log4OM becomes the archive. thats basically where i landed after fighting it for two years

WSJT-X has a setting to log directly via UDP to whatever your main logger is, if Log4OM supports that port it should just work without the ADIF shuffle. i think Log4OM does support it but i havent actually tried it myself so dont quote me on that