Implementing Servicenow. Experiences?

redtidings
Kilo Explorer

Hi all,

We have just been greenlighted to go to Servicenow over the next few months.

I would be very interested to gain insight from current users on how the implementation has gone.

We are a multi-site entity moving from multiple platforms to Servicenow.

My specific situation is moving from Altiris 7, which was disabled some time ago (not at my request).

I have records for both hardware and software assets (not as up to date as they were thanks to the disabling of my lovely working product)

Are these easy to import into Servicenow? (formats needed etc)

The decision to move has been taken on the continent and project lead is there too (subbed out to contractors) so want to know how this has been implemented in your organisation.

Keen to here feedback on Servicenow training courses as well.

Thanks for taking the time to read the post.

Mike

2 REPLIES 2

tdf
Kilo Expert

SN has a very powerful import tool called Import Sets (Import Sets - ServiceNow Wiki).   The Wiki goes into all of the details, but to over-simplify you identify a data source (anything from an Excel spreadsheet up to a direct connection to a SQL database), create a transform map where you tell the system how to translate the incoming data into the appropriate tables, and then you test and execute.   You can also schedule them to be run periodically to keep your data fresh.   Obviously in your case you don't need it, but a more common on that we see in use is the SCCM plugin which is a collections of import sets that run periodically to bring in asset data from SCCM and place them in the correct SN tables.



I'm thinking after you get your base data loaded using import sets you will want to use some sort of discovery tool (ex. SCCM) to keep it fresh and updated.  



Happy to help if you have any other questions,



-tim


Thanks Tim, sounds like the importing will be ideal for my situation