**Data Migration Issues **
Hi @Rajat Singh @fabienne @Mridang Agarwalla
I have migrated datas from the existing self hosted zitadel to a newly hosted zitadel (both are same version). Using the below reference.
https://zitadel.com/docs/apis/resources/admin/admin-service-export-data
Now I am facing some issues,
1. SSO related configuration, default configurations will not be migrated
2. Machine users client secret and metadatas are not migrated
3. The main issue is - Human users which is not set with password but actually active in the existing instance (this active status is handled as these users are going to use only google sso which we handled in our server code) are migrated as initial user (which means unverified or inactive user) in the new instance - As the users status become initial I was not able to login using the sso as well, it showing user not found because of its inactive status.
I have migrated datas from the existing self hosted zitadel to a newly hosted zitadel (both are same version). Using the below reference.
https://zitadel.com/docs/apis/resources/admin/admin-service-export-data
Now I am facing some issues,
1. SSO related configuration, default configurations will not be migrated
2. Machine users client secret and metadatas are not migrated
3. The main issue is - Human users which is not set with password but actually active in the existing instance (this active status is handled as these users are going to use only google sso which we handled in our server code) are migrated as initial user (which means unverified or inactive user) in the new instance - As the users status become initial I was not able to login using the sso as well, it showing user not found because of its inactive status.
Export data on an instance level to ZITADEL. It can be either directly exported in the response or you can point to a file on an S3 storage, where the data should be written.
