When deploying a new Orchestrator instance for testing or for replacing an existing instance, you most likely will want to clone the existing configuration.
Orchestrator objects such as workflows and configurations can be cloned easily either by import/export of packages or direct Orchestrator synchronization. But, REST hosts can be problematic, especially when they involve authentication. The VMWare KB article 2133883 gives some idea of the problems, which is caused by passwords being encrypted using tokens unique to each Orchestrator instance. But sadly, the KB article is incomplete and does not offer a proper resolution.
Example error, typically thrown in the vCO server.log:
This document attempts to pick up where that KB article left off. The processes documented in this article have been tested thoroughly for hours on end so that you won't need to experience the same headaches.
These processes have been tested successfully on VMWare Orchestrator 5.5.3 and 6.0.4. Your mileage may vary if you attempt these instructions with other Orchestrator versions.