Hi,
We are planning to perform a lift-and-shift migration of our Documentum environment from on-premises infrastructure to Microsoft Azure Cloud. As this is a lift-and-shift approach, there will be no changes to the Windows OS or software product versions—everything will remain as-is in terms of configuration and functionality.
We would appreciate your guidance on the following points and would be grateful if you could share any official documentation or best practices related to such migrations:
Hostname and IP Address Changes
Post-migration, the hostnames and IP addresses of our servers (Content Server, Application Server, Index Server, and CTS) will change in Azure
Can we update these changes directly in the configuration files and databases?
Would using migrationUtil.bat be sufficient for this purpose?
Trusted Content Services (TCS) and Encryption
We are currently using TCS, and our content is encrypted.
How will this encryption behave after the migration?
Are there any specific steps we need to take to ensure content remains accessible?
Domain Change for User Logins
Our current user login domain is ****, which will change after the migration.
Do we need to manually update all user accounts to reflect the new domain?
We are using Windows Authentication (no LDAP).
Additional Considerations
Are there any other critical factors or dependencies we should be aware of during this migration?
Licensing Requirements
Do we need to make any changes to our existing Documentum license to support this migration from on-premises to Azure?
We look forward to your expert advice and any documentation you can provide to support a smooth transition.
