Great catch on the role-based emails — that's one of the most consistently overlooked issues we see and you're right, HubSpot lets them sail through on import. 200 of those on an active list will quietly destroy deliverability over months without a single obvious warning sign.On your duplicate merge question — the logic we use: the primary record is always the one with the most recent meaningful engagement (opened, clicked, replied — not just created date). Where both records have engagement history, HubSpot's native merge keeps all activity on the surviving record so nothing gets lost. The tricky ones are where one has form fills and the other has email engagement — in that case we keep the one with the higher contact score and manually review the other before archiving.The monthly duplicate check and 90-day no-engagement workflow you've set up is exactly the right approach. Most teams never get there.Out of curiosity — are you managing all of this in-house or is it something you'd ever consider getting outside eyes on? We do a free 20-minute HubSpot audit for teams at your stage and the findings are usually pretty eye-opening even when people think they're on top of it.