Update set transfers

When an update set is completed, you can transfer it between instances to move customizations from development, through testing, and into production.

Transferring via ReleaseOps

ReleaseOps automates deployment of changes across your pipeline, increases predictability and reliability of deployments, and reduces the risk of releasing changes to production. See ReleaseOps.

Transferring via IP access control

If IP address access control is active on the source instance or a different datacenter from the target, complete these steps before transferring an update set.

1. Contact Customer Service and Support to find out the IP addresses of all application nodes supporting your instance.
2. On the source instance, navigate to System SecurityIP Address Access Control, and add the IP address as an exception.

Transferring via an update source

If IP address access control is enabled on the source instance, set up the target instance as an exception. See Set up the source instance for an update set.

Transferring via an XML file

You can unload an update set as an XML file and then transfer it to another instance, see Save an update set as a local XML file.