# Enforcing required fields during an import

**URL:** <https://community.hubspot.com/t/enforcing-required-fields-during-an-import/46452>\
**Category:** CRM\
**Tags:** enterprise\
**Created:** [November 4, 2021, 4:39am UTC](https://community.hubspot.com/t/enforcing-required-fields-during-an-import/46452 "2021-11-04T04:39:09Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![RyanAbilar](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/ryanabilar/32/105439_2.png) [@RyanAbilar](https://community.hubspot.com/u/RyanAbilar)\
**Post date:** [November 4, 2021, 4:39am UTC](https://community.hubspot.com/t/enforcing-required-fields-during-an-import/46452/1 "2021-11-04T04:39:09Z")

</div>

Hi team,

I noticed that required properties are not respected during an import. I realized this specifically in the “Email” property when I checked how much contacts we have right now without the said data. Surprisingly! We have quite a huge amount which is extremly alarming. So I looked deeper and found out that a huge chunk of these records were created from imports. Out of curiosity, I tried to create an import file with only one record that do NOT have an email address in it. And yes. The record was created even without the email address and even if the property is ‘required’ during a single record creation via the UI.

Is there a way to enforce required fields during an import? I have already restricted imports to very limited users only in our org. Still, the chance of getting these records being created in the CRM is inevitable.

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [November 4, 2021, 6:07am UTC](https://community.hubspot.com/t/enforcing-required-fields-during-an-import/46452/2 "2021-11-04T06:07:26Z")

</div>

Hi @RyanAbilar,

This is unfortunately not supported, however other users have already requested the same in the HubSpot Ideas section of the community: [Mandatory fields on imports](https://community.hubspot.com/t5/HubSpot-Ideas/Mandatory-fields-on-imports/idi-p/369629)

The product team reviews these submissions based on popularity, so I’d recommed upvoting and commenting with your use case.

Best regards!

---

<div class="post-metadata">

**Author:** ![RyanAbilar](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/ryanabilar/32/105439_2.png) [@RyanAbilar](https://community.hubspot.com/u/RyanAbilar)\
**Post date:** [November 4, 2021, 6:40am UTC](https://community.hubspot.com/t/enforcing-required-fields-during-an-import/46452/3 "2021-11-04T06:40:11Z")

</div>

Thanks Karsten

---

<div class="post-metadata">

**Author:** ![NHettige](https://avatars.discourse-cdn.com/v4/letter/n/e36b37/32.png) [@NHettige](https://community.hubspot.com/u/NHettige)\
**Post date:** [January 11, 2022, 4:58am UTC](https://community.hubspot.com/t/enforcing-required-fields-during-an-import/46452/4 "2022-01-11T04:58:45Z")

</div>

This is definitely needed to maintain proper control! I hope the development team would take this up soon.

---

<div class="post-metadata">

**Author:** ![JessieS](https://avatars.discourse-cdn.com/v4/letter/j/b5e925/32.png) [@JessieS](https://community.hubspot.com/u/JessieS)\
**Post date:** [September 18, 2024, 7:18pm UTC](https://community.hubspot.com/t/enforcing-required-fields-during-an-import/46452/5 "2024-09-18T19:18:44Z")

</div>

+1 for a customer