I was wondering about the manual intervention required on this part:
Initial Steps Prior to Environment Transfer
3. Stop the scheduler service in the destination environment. This will ensure no scheduled executions begin (in DEV environment) during the transfer.
Surely TX can automatically control the TX Scheduler Service via the service account created for that purpose?
4. Ensure no execution packages are running in the destination environment.
Surely TX can talk to the TX Server Service in Prod (Destination) and agree to pause the migration until any running execution packages have completed, then pause the TX Scheduler Service and complete the migration?
Just thinking aloud, I'm fairly new to TX, but happy to discover why this couldn't be achieved.