Best practice to move data from one instance to the next in ServiceNow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-07-2020 02:17 PM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-08-2020 11:23 PM
Hi,
The best way to move data like configuration changes from one instance to another is through update sets.
However, you can try to use the Export to XML feature (click here for more details) for that specific table and import the XML into the other ServiceNow instance, usually it's the best method when you have a huge amount of records.
You can refer the below documentation link as well for more info.
Thanks,
Pooja M
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-08-2024 10:03 AM
Which is the most efficient way to move large amounts of data between instances?
A. Export to Data Package
B. Export to XML
C. Update Sets
D. Export to Zip
What will be the correct answer