Hello, I currently have an application (app 1) that uses Auth0.
And another application (app2) that uses AWS Cognito.
I would like to migrate my app2 to the same Auth0 tenant as app1, in order to benefit from SSO between the two.
I have already implemented silent migration scripts from Cognito to Auth0 on a test tenant.
Unfortunately, on the production tenant (app1), I did not use a custom database, and I am therefore unable to implement the silent migration.
Note that I cannot require my users to enter a new password, for either app1 or app2.
One option could be to create a custom database on the production Auth0 tenant, but to migrate app1 users with their passwords/MFA factors from the current database, this requires going through Auth0 support, making a dedicated export request, and then reimporting the users.
Auth0 cannot guarantee the date on which this export will be completed, which is unacceptable (I have new users every day).
Furthermore, I don’t need personal access to the export, knowing that all I want in the end is to transform my current username-database-password into a custom database where I can enable the “migrate users” option…
Yet again, we are sorry about the delayed response to your inquiry regarding the matter!
It can be quite difficult to migrate your current database to a new one in order to implement a custom database script to have your AWS users migrated as well. In your situation, the most viable solutions would be:
Creat a support ticket in order to request a user export so that you can migrate them to a new database connection. I understand that you have already mentioned that you do not find this approach suitable for the reasons mentioned above however the export would be the best solution and even though we cannot guarantee the exact time frame in which it will be completed, it should not take a lot of time. For more information on the matter, I would recommend to have this discussed with one of our dedicated engineers on a support ticket.
Your other option would be to migrate the AWS users by using a bulk user import job. The job can take different amounts of time to complete depending on the size of the files used, however, you should be able to import any new users that your platform received during the time the job took to be completed.
If you have any other questions on the matter or if I can help with anything else, let me know!