...
In short, the Kantega SSO version is fully compatible with both Atlassian Server and Atlassian Data Center products, and configuration is saved in the same way on both types. Therefore, if you use Atlassian recommendations for importing the database and home folder from the previous installation to the new, your Kantega SSO setup should work directly. That is as long as your DNS name Base URL for the new installation is the same as the previous (for example https://my-jira.example.com).
If you need to change the DNS Base URL name for your installation, you would have to:
for a Kerberos setup, to create a new keytab file with the new DNS nameBase URL
for OIDC/SAML setups create new/change configurations in your Identity providers since the configurations point to the old DNS nameBase URL.
You could possibly also alternatively use the Kantega SSO backup and restore feature to move your configuration from the old installation to the new. This would also correctly move configuration for Kerberos/SAML/OIDC setups. But configuration for Cloud User Sync will be somewhat more work since these rely on a User directory setup that is not restored. And especially for a SCIM setup, you would have to run the SCIM setup wizard again.
...