An update set captures supported configuration changes so you can move them between instances. Make a named in-progress set current before working, then inspect its captured changes before marking it complete. Business records such as incidents and imported assets are not a general-purpose payload of a configuration update set.
In the target instance, retrieve the set and preview it. Resolve collisions, missing dependencies, and other preview problems before committing. Complete in the source does not mean deployed in the target. Keep related configuration together with clear ownership and test evidence. The simulator captures a small set of configuration definitions and their descriptions. It teaches the lifecycle and review boundary, but it does not connect to a second hosted instance or reproduce every application-scope migration mechanism.