# How automatisation bulk import several million user ( bulk import- attribut required)

**URL:** <https://community.auth0.com/t/how-automatisation-bulk-import-several-million-user-bulk-import-attribut-required/183865>\
**Category:** Integration Help\
**Created:** [March 13, 2025, 7:26pm UTC](https://community.auth0.com/t/how-automatisation-bulk-import-several-million-user-bulk-import-attribut-required/183865 "2025-03-13T19:26:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![virginie.hugnet](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/virginie.hugnet/32/71837_2.png) [@virginie.hugnet](https://community.auth0.com/u/virginie.hugnet)\
**Post date:** [March 13, 2025, 7:26pm UTC](https://community.auth0.com/t/how-automatisation-bulk-import-several-million-user-bulk-import-attribut-required/183865/1 "2025-03-13T19:26:59Z")

</div>

Hello,

I have sereval million users to import in bulk… the 500ko limitation is restrictive, and when I create a script to automate the splitting and sending of user-imports jobs… the custom\_password\_hash and email (email is optional on my database, my unique identifier is the username) seem mandatory, whereas this is not the case when I import a small file via the management API jobs or via extension… how should I proceed, please?

Thank you, Best regards, Virginie

---

<div class="post-metadata">

**Author:** ![nik.baleca](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/nik.baleca/32/68749_2.png) [@nik.baleca](https://community.auth0.com/u/nik.baleca)\
**Post date:** [March 17, 2025, 7:02pm UTC](https://community.auth0.com/t/how-automatisation-bulk-import-several-million-user-bulk-import-attribut-required/183865/2 "2025-03-17T19:02:57Z")

</div>

Hi @virginie.hugnet

When importing users, the `email` attribute is required as stated by [this](https://community.auth0.com/t/importing-user-profiles-that-do-not-have-an-email-attribute/113889) knowledge article.

For you to be able to import these users, you would need to assign a dummy email as stated by the article in order complete the import.

However, when creating an `user-imports job`, there is a parameter called `upsert`. When this is set to `true`, an email is required. You can try passing it as false as seen in our [documentation](https://auth0.com/docs/api/management/v2/jobs/post-users-imports).  
In the case of users which have their password hashed in a different algorithm than the standard one Auth0 uses, bcrypt), the `custom_password_hash` property will be required in the file.

You can read more about Bulk User Import Schemas [here](https://auth0.com/docs/manage-users/user-migration/bulk-user-import-database-schema-and-examples).

As an alternative, you can configure [automatic user migration](https://auth0.com/docs/manage-users/user-migration/configure-automatic-migration-from-your-database) by configuring database action scripts in your connection. Please keep in mind that for you to be able to implement this, you would need to have a Professional plan active on your tenant.

If you have any other questions, feel free to leave a reply!

Kind Regards,  
Nik
