ndjson
to JSON. To keep the same user IDs, you must remove the auth0| prefix
from all imported user IDs.The import process automatically adds the auth0| prefix
to the imported user IDs. If you do not remove the auth0|
prefix before importing, the user IDs return as auth0|auth0|...
user.user_metadata.name
, or it can be a JavaScript expression like user.user_metadata.name || user.name
. Expressions will be evaluated during the export runtime. The column name value is how the value will be represented in the export.
You can click the Add Default Fields button to automatically select the default fields and populate their column names (this is also a good way for you to visualize how parameters/expressions will appear).
You can remove extraneous attributes/expressions by clicking on its associated trash can icon.
Under Settings, you can:
X
is the number of users you’re exporting).
You can download the file containing your users when the export is complete; you may need to use a third-party extraction tool if you run Windows 10 or lower.
user_metadata
and app_metadata
with the User Import/Export Extension.
connection|id
. If the same user Id exists in multiple connections, your update will fail.email_verified
attribute to multiple users and set the value to true
.
users-import
endpoint allows you to upload your updated user profile file and update several users in one job. Navigate to the Create import users job endpoint.
Add your user file to the users parameter and add the database connection ID of the database you want to update.
The upsert value should be true
to update the already existing user information.
To add your updates, select Try or use Postman to import the users.
Use the job_id
to verify the status with the jobs
endpoint.