Current CRM constituent update batch import and template design only allows "new" addresses, phones, and emails to be marked as primary in batch. If an imported address matches to an existing address it is no longer considered a new record and cannot automatically be marked as primary. A workaround is to set constituent update configuration in batch and/or import to create a new address/phone/email record, even if the incoming record is "similar" (or matched) to an existing one, which forces a manual review to resolve a duplicate entry. When importing high volume the manual effort can quickly become unsustainable. If there is ever an expectation that all incoming addresses should be considered primary, then the choice is between not properly updating contact information to save time and resources and significant manual effort to maintain data integrity. Because of this scenario, there should be another constituent update configuration option that allows to both match to existing records and marking as primary.