How can I locate secondary email addresses in a report

[JRivette]

We have connected the Knowledge Base to our customer portal. In doing so the tracking code we needed to embed on our website now feeds information to HubSpot via a range of non HubSpot based forms. In doing so it is appending any email address and other information to the contact who is logged in at the time and embedding much of this as a secondary email address.

We have since turned off the ability for non hubspot created forms to create contacts but now need to cleanse the data. How can I locate the secondary email address of a contact and export in a report so i can cleanse the data and reimport back to clear these incorrect secondary email addresses hubspot has created?

Regards,

Justin

[karstenkoehler]

Hi @JRivette,

If your plan is to clean upand reimport, then you could simply use this option when exporting contacts from the contact index page: https://knowledge.hubspot.com/import-and-export/export-records#export-records

Best regards!

[JRivette]

OK thank you this has exported the additional email. I am however struggling to import and remove the additional email addresses. When I remove them from the file and then reimport the record remains. Is there a character or specific value I should be entering in the reimport file to trigger hubSpot to overwrite and remove the adidtional emails?

[karstenkoehler · Accepted solution]

@JRivette as far as I know, this is currently not possible via import, see also this previous reply by a community manager: https://community.hubspot.com/t5/CRM/Secondary-email-removal/m-p/657395/highlight/true#M134539

Unless you're open working with the HubSpot API and developing a private app for this, your best course of action is likely going through these one by one manually. (Don't shoot the messenger.)

[JRivette]

OMG 🙄. Luky we caught this early and only 2,000 contacts were effected. Its hard to believe that there is no function for this to import or reach these fields with a workflow. Somtimes Hubspot is great but it often lacks depth in the development at the expense of geting a the broad features built.

Thankyou however for your response. I often find your feedback for other users on point and very helpful - be that not what I wanted to hear.

Regards,

Justin