Data Migration - Missing fields

kaan · ‎02-14-2017

Hi all,

We are moving to a new instance (re-implementing the whole system) and need to migrate a bulk of tickets. So far we did XML import-export from lists since it preserves sys_id, original dates, work notes, and attachments. However, there are many field types we changed, and these fields either migrated the wrong data or didn't migrate at all. How can we fill these missing/wrong fields? Any scripting method?

Is there a better way to do this migration? I know we can use scripts with transform maps but that causes issues with the attachments. Our goal is basically move the tickets without losing attachments, work notes, and dates?

Thanks!

Chuck Tomasi · ‎02-14-2017

Hi Kaan,

Migrate the data you can via XML. That will create the original records. For the fields that have changed types, export those to Excel and a "key" field like number, name, sys_id, or something else that you can use to coalesce on an import transform map. Now you have the original data minus the changed fields, and can import the new data from Excel with the new field types and match them to the existing records you imported with XML.

View solution in original post

Chuck Tomasi · ‎03-02-2017

Aside from cloning, I have not found a good way to migrate the work notes, comments, or other journal fields from one instance to another. In my experience, they are often just "nice to have history" rather than data you can actually report on and script against.

markherring · ‎08-30-2018

Hello,

Yes you can use ITSM Bridge to migrate tickets between ServiceNow instances and it will preserve the SysIds, dates, work-logs and attachments. You will need ITSM Bridge v3.9 - see itsmbridge.com

HTH

Mark