If you have only Android+ devices, there may be some chance of migrating without requiring re-enrollment, provided all the required steps are done properly. But even so ,all your devices will likely display warning message about incorrect certificate(s), and manual confirmation to go ahead to connect to the migrated server is needed for each device. I did something similar a few years ago for Android 4.x devices. I'm not sure there are any new changes in newer Android versions that make such migration easier, worse or even impossible.
Soti professional service team may have smarter way to help you out.
Only Android 5 units today enrolled whit Android+, test server that has been migrated is only running whit 7 units.
The production server has not been migrated yet but are running 1500 devices whit Android 5, spread out all around the country.
So re-enrollment may be a big challenge.
The server guys did keep OldCompany.org open and will be routed to the NewComapny.org and then hit the Secondary Agent Adress that is set to OldCompany.org.
Not sure if this is working, however new enrollmenst over internet as on their guest ssid or whti SIM card is working, units are enrolled whit new add device rule, however it is only using OldComapny.org connection, it tries NewCompany.org but no connection.
Checking network we are not finding any drops on the unit when tracing.
I'm awaiting confirmation for a session whit Soti but it is not confirmed yet.
What platform(s) of devices do you have in your server? How many devices of each platform are enrolled before the migration?
In general, domain name cannot be migrated without device re-enrollment in most cases. Have you talked to anyone in Soti about what you want to do?