Moving update sets from higher release to lower release Description<!-- 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 When customers upgrade, they typically test it out in a lower instance like dev or test, before upgrading their production instance. In this period any update sets being worked upon in the development instance might need to be moved to production prior to their upgrade. Question: Is it okay to move this update sets from the lower instance on a higher release to the higher instance with lower release, in such cases? Answer In general it is not recommended to move update sets from a lower instance with a higher release to a higher instance with lower release. Example If you have a dev instance with Madrid and prod is still in London, your update sets which are in progress in Madrid might have newer code changes which might not have the required dependencies in London. Additional Information Please refer to this community article discussing the same here.