Recently, we did an upgrade from Tridion Docs 14 to 15. As is typically the case, there is some iteration to migrate/upgrade the existing CM database, validate, and then often we will go back and "refresh" by migrating the old environment database again, for various reasons (to pick up delta of content changes, to correct any issues found, etc.).

With Docs 15, we moved to SSO, which means all of the user configuration had to be updated after the database migration, to convert users from the older, independent SDL logins to new SSO logins integration with our Microsoft ecosystem. But then this creates an issue in the above described situation, where we do a database "refresh", as this can wipe out all of the updated SSO users, resulting in needing to redo all of them.

I'm not sure if there is a way to do this, since user data is closely coupled with the CM database (creation dates, modified by, etc.), but if it were possible to separate the user data out from the CM database (either another database or maybe an export/import mechanism of some sort), this would solve the issue of having to redo all of the user accounts manually.