Data Migration - Missing fields

[kaan]

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 · Accepted solution]

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.

[Chuck Tomasi]

If I have answered your question, please mark my response as correct so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list.

If you are viewing this from the community inbox you will not see the correct answer button.   If so, please review How to Mark Answers Correct From Inbox View.

Thank you

[kaan]

Thanks Chuck. You saved me hours.

[kaan]

Hi Chuck - After I migrated the data via XML, some of the work notes didn't get migrated.

The ones that got migrated have the wrong date/time associated to them. Importing [sys_journal_field] table via XML didn't seem to correct this.

Is there a way to migrate the work notes (with the right date/time associated) from the old instance?

Thanks again.