What is the best practice to do before performing update sets?

[ChuanYanF]

Dear experts,

What is the best practices to perform an update set as in I need to customized the form and modules across different applications and therefore, the application scope will change quite frequently just like my default set will change based on the application where I cannot control which update sets is already in after all the customization I have done, I have tried to export an update set and import to my new instance but there are many errors and the customization i did before does not appearing like what I did, how do i make sure that my new environment will be exactly the same as what I customized like in my old instance? Any advice on this? I mainly deal with the risk management workspace, advanced risk, compliance, profile and some other things, how do I make sure all of this changes I did for all this application will be reflected in my new instance using import update set functions?

[Mark Manders]

You can use ServiceNow Studio (if available for your version) which will switch automatically, or you create the update set(s) for each scope you have to work in and make it your 'current' one. You can make one set (the global one) the parent of the others, so it will be moved as a batch and you will everything together and only have to commit one set. 

You can only make sure you capture everything, if you work in update sets (and really check if it's not data that you expect to be transferred, because that's not captured). Check the update sets before you move them to the next instance to see if they are clean and contain everything you expect it to contain. Make sure you don't move any logic that you created, but decided not to use.