Best practice to move data from one instance to the next in ServiceNow

[PN2]

I recall a community post where a member said that it is best practice to move data from Production to Test; then to Dev but to move code from Dev to Test, to Production. I can't seem to find that post now. 

Can someone provide best practice to move data from one instance to the next? For example, is it recommended to add departments into Production, then export to xml and import into lower level environments (Dev and Test)?

Thanks in advance.

[MrMuhammad]

Two types of changes are there we usually do in Servicenow one gets captured in the Update sets and the other doesn't

Below information is Copied Chuck Tomasi's response regarding the data capture from another post. 

In short, the update set captures the system configuration changes you make to the system. This includes, but is not limited to:

• Tables
• fields
• form layout
• list layout
• business rules, client scripts, script includes, and other scripts
• workflows
• system properties

What it does NOT capture is your transactional data like

• Incidents
• Users
• Groups
• Email

In my opinion the best way is to move all the system configurations changes that is captured in the update set from lower instance to Higher. DEV -> TEST -> PROD.

For transactional data changes if you are importing data from external source like AD then you can go from Higher instance to Lower but if you are creating data manually inside Servicenow I will suggest to move from lower instance to Higher via xml import. 

Thanks & Regards,

Sharjeel

[PN2]

Hi Muhammad,

That's what I was wondering - about the transactional data. Thank you for your input. Do you operate this way as well?

[MrMuhammad]

Hi,

Well in my case our user data is coming from AD and we have weekly clone down in place so users data flows from PROD to SUB PROD. Groups are being created locally so we use to create in DEV and then move to Higher instances via xml export.

Please mark my response as CORRECT and HELPFUL if it answered your Question.

Thanks,

Sharjeel

[Ankush Jangle1]

Hello,

This will Help you

https://hi.service-now.com/kb_view.do?sysparm_article=KB0546788

Breakdown of Basic Process

The basic process for getting an update set from the stage of development to production is the following:

Development instance

1. Proceed to create an update set on the development instance
2. Make changes and customizations. Use meaningful names and descriptions in your update sets. 
3. Mark it as Complete.

Test instance

1. First, log in to the test instance and retrieve the update set from the development instance.
2. Next, commit to retrieved update set on the test instance and proceed to test the customizations. Always run a preview just prior to committing an update set.
3. In case of any issues in the test instance, return to the development instance and create another update set.

Production instance

1. Locate the production instance, log in, and retrieve the update set from the development instance. In case the update set needs to be fixed, be sure to complete the fixes in another update set, and retrieve both update sets.
2. Next, commit the update set on production, or if it requires a fix, commit both in the order they were made. 

Don’t delete any update sets, unless you have merged update sets. Prior to committing, consider merging update sets that you’re going to promote together. Once they are merged, delete the original sets to avoid later confusion.

Mark it Helpful/Correct if it Helps you