locked
SCSM: Identify the possibility of import / export incidents from one SCSM installation to another RRS feed

  • Question

  • SCSM: Identify the possibility of import / export incidents from one SCSM installation to another
    Tuesday, August 29, 2017 1:38 PM

Answers

  • Hi,

    Is this a one off transfer/migration or is something that needs to be done on an on going basis?

    And does it need to be done by a SCSM administrator or is it being done by an analyst.

    Here are some options to consider:

    1. It maybe possible using Orchestrator for individual jobs on an adhoc basis. This would be analyst initiated somehow and it would take basic information across. However, I do not have any examples of doing this.

    2. If you were doing it as a one off process, a SCSM Admin could export all Incidents to a csv file and then import them into the new instance (Google search on export and import should find examples). Getting a full audit history of the old incident would be difficult and I would suggest is better saved as an attachment to the incident or added to a text field (note most text fields have a 4000 char limit).

    3. If you want to transfer incidents on an on-going basis, we here at Xapity created Xapity Transfer to do exactly this. It transfers an incident to the new instance, completes the original IR when the transferred one completes, allows a view into the transferred IR to check status, and allows analysts to post comments into the transferred IR.

    Regards

    Glen


    Web: www.xapity.com  |   Twitter: @xapityapps  |   Facebook: xapityapps


    Tuesday, August 29, 2017 8:30 PM

All replies

  • Hi,

    Is this a one off transfer/migration or is something that needs to be done on an on going basis?

    And does it need to be done by a SCSM administrator or is it being done by an analyst.

    Here are some options to consider:

    1. It maybe possible using Orchestrator for individual jobs on an adhoc basis. This would be analyst initiated somehow and it would take basic information across. However, I do not have any examples of doing this.

    2. If you were doing it as a one off process, a SCSM Admin could export all Incidents to a csv file and then import them into the new instance (Google search on export and import should find examples). Getting a full audit history of the old incident would be difficult and I would suggest is better saved as an attachment to the incident or added to a text field (note most text fields have a 4000 char limit).

    3. If you want to transfer incidents on an on-going basis, we here at Xapity created Xapity Transfer to do exactly this. It transfers an incident to the new instance, completes the original IR when the transferred one completes, allows a view into the transferred IR to check status, and allows analysts to post comments into the transferred IR.

    Regards

    Glen


    Web: www.xapity.com  |   Twitter: @xapityapps  |   Facebook: xapityapps


    Tuesday, August 29, 2017 8:30 PM
  • How about the issue, is there anything to update?
    Please remember to click “Mark as Answer” on the post that helps you.

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, September 11, 2017 9:35 AM