It would be great if we could choose which fields are mandatory for importing contacts (initially), in addition to those that are already pre-defined in Hubspot.
Thanks for clarifying and explaining your usecase @LMarsden! That makes sense! I was curious about the Contacts creator because I wanted to know if the preference is @JHannus's preference is for the property requirements to apply to import as well? In your situation, would you want region to mandatory for both the contacts creator and in import?
We've heard some folks view import as a way to get data into HubSpot that is not constrained by the same requirements as the Contacts creator, so we want to make sure we are supporting those needs as well.
Hi @JHannus , Shiva here from the Import/Export team. Could you share a bit more context about why this would help? Do you have mandatory fields defined in the Contacts creator (i.e. Settings -> Objects -> Contacts -> Customize the 'Create contact' form)?
Hi @JHannus , Shiva here from the Import/Export team. Could you share a bit more context about why this would help? Do you have mandatory fields defined in the Contacts creator (i.e. Settings -> Objects -> Contacts -> Customize the 'Create contact' form)?
@shivamuthiah it's not for individual contact creation but for importing that it would be useful. In our instance, we have 2 regions we serve and all of our workflows hinge off of the region selected. When contacts are imported without the region, sometimes we have issues with who is assigned & who starts getting emails (add in GDPR too and it's an issue).
Thanks for clarifying and explaining your usecase @LMarsden! That makes sense! I was curious about the Contacts creator because I wanted to know if the preference is @JHannus's preference is for the property requirements to apply to import as well? In your situation, would you want region to mandatory for both the contacts creator and in import?
We've heard some folks view import as a way to get data into HubSpot that is not constrained by the same requirements as the Contacts creator, so we want to make sure we are supporting those needs as well.
@shivamuthiah yes exactly, I need it added to importing. We already have this field and a few others added to the contacts creator. As the admin, I can tell people it's required to select these fields when importing new contacts in bulk, but it would be FAR more helpful to data quality to make them mandatory in importing!
Please tell me this rising to the top of the department's list. As an Enterprise super admin with just the bare bones of our B2B brands in our ecosystem, we need this. I should be able to dictate our corporate standards for good data.
Hey there. This idea is essential. Considering data quality, no system permits importing a complete "trash list" and then spending hours cleaning it up. Mandatory fields lose their significance when users import files, which is why this feature is indispensable. For every company, there's the choice to establish mandatory fields; the bare minimum includes email, type, name, and surname. If the admin designates certain fields as mandatory, users uploading files must adhere to these requirements and create files accordingly.
Is there any news on this item? Not being able to control what gets imported creates a LOT of bad data, or data not up to quality requirements.
As the others posters have noted, some basic restrictions, optionally set by the superadmin, would go a long way. "Idea submitted" status after 4 years and 117 upvotes on something as crucial as this is quite frankly disappointing.
Yes please! We so need this! My sales team continue to bulk import contacts without the fields we would usually require as part of the Create Contact and Create Company forms. I am dealing with so much data that is incomplete, missing the fields we need for compliance purposes and for campaign purposes.
This would be a useful feature to enforce people include certain properties when importing contacts. A common use case is making sure that when the marketer goes to a trade show that they include lead source = events and lead source detail = trade show name. Ideally I could enforce that users have to fill out these two properties when adding in new contacts to the database.
Additionally, it would be sensible to enforce this for all Contact creation methods e.g. when a user sends a tracked and logged email to a prospect and a Contact is created automatically
