Balancing ServiceNow data retention with innovation
I think it’s really important in that
planning phase when you’re starting to look at replatforming to figure out, one, what
are your organization’s constraints around data? Do you have to keep your change management
records for three years? Understanding that is gonna be key. But then if you take old data from
a customized system and try and put it into a new, clean system, what often happens is you’re
just carrying over customizations. So, there’s a couple of different ways that
we encourage. We encourage folks not to bring that old data, because there was a
reason you were getting away from it. And there’s a couple of different mechanisms. Of
course, you can store it in an SQL database somewhere so folks still have access to it.
You can also take that ticket data—especially if you’re an ITSM Pro customer of ServiceNow—you
can actually import ticket data into performance analytics. So you still have your data and
your analytics there. But you’re not pulling in all those custom fields and muddying up your
clean tables that you’re trying to get to.
https://www.youtube.com/watch?v=rJhFtqSzBVY