I had no idea the limits were lifetime limits on ADIF imports. I assumed it was a daily/weekly limit kind of thing. Note to self, read the fine print.
I had an issue with importing logs, we discussed here: Missing Log Data issue
I was not able to clear my QRZ logbook and start over, per discussion with QRZ. This would have been problematic at QRZ. So my QRZ Records are permanently missing data from those records.
To solve this problem going forward I adopted a send from my main log to all logging systems, individually, approach. Export directly to each system. This approach is my best effort to keep complete, detailed logs. Now with lifetime limits I have to once again rethink my method. Because of the earlier issue, linked above, I have trust issues with other systems transferring complete information.
I can see this being a big problem for those not using integrations. I would think that direct ADIF imports would be the preferred method, not to mention faster, by cutting out the middleman. I do not mind integration of cross platform confirmations, LoTW, QRZ, eQSL, ClubLog, etc. My concern is complete records
I also do not like running multiple programs to integrate live. I never log Live. In the heat of battle errors can and do happen. Not only do I have to repair in my main log, I also have to chase it elsewhere. I log, review afterword’s , and then send. I am never in a hurry to send my logs.
Is there a way we can look at our logs an know where we stand on the limits?
It has been a while since I have logged anything, months actually. Life has a way of getting in the way. I guess I consider myself fortunate as I have a very small log.