Move update set from a standalone instance to a domain separated instanceDescription<!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Overview Is it possible to capture an update set in a standalone instance and commit it on an instance with domain separation? Please note that when using update sets it is recommended that they are developed in the same instance release and the environment they are intended for and this is documented. Documentation link given below. https://docs.servicenow.com/csh?topicname=get-started-update-sets.html&version=latestIn this scenario, the update set will be captured in a non-domain separated instance and must be applied to a domain separated instance only. Our recommendation in this scenario would be to manually create the objects however if the customer wishes to pursue the update set route please they must test this thoroughly. They can reach out to the Professional Services team via their accounts manager for assistance required in achieving the above requirement.