Is it possible to modify users' DNS records in their email addresses during the migration from Confluence on-premise server to the cloud?
For example.
The internal directory contains users with email addresses user@ААА.com.
The domain was confirmed to be MMM.COM.
I will want to migrate the instance to the cloud and I also want to create users with new DNS records like user@МММ.СОМ during migration.
Changes in the database is not considered.
Hi Rolands,
Yes, it is possible. When performing a migration from server to cloud, the users are created with whatever email addresses are associated with their accounts in the source server. The way in which you do so will depend on what your migration method is.
If you're migrating using the Jira Cloud Migration Assistant -- The emails will have to be updated before you run the migration tool. This can be done manually through the UI but depending on how many users you have to update, this could take quite some time.
If SQL queries are out of the question for you, you could also possibly use the REST api and script out the updates. If the users are all part of the Internal directory, and not being synched to an external AD, then you should be able to do this step ahead of time. If they're tied to an external directory, then when the user directory in Jira syncs, it will override any changes you make.
If you're migrating with a site export/import -- You could run a sed command against the entities.xml file in the export to change all of the emails before running the import into the cloud. This method though is only available if your migration meets certain criteria. Site imports into cloud are trickier in general, and will almost certainly require an open ticket with Atlassian support, as there's no visibility into the status of the import from the end user. If you're looking to do a migration this way, I would suggest opening a ticket with Atlassian ahead of time.
Sorry, I just realized you were migrating from Confluence, not Jira. The same applies.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for detail explanation.
I suppose, the REST API is a good idea and will be more preferable for me.
I will explore this way. I mean, I will look the appropriated REST API request.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.