Data Migration Approach | 10 Years | X Tool to ServiceNow

[nowGurukul_SN]

Hi Community.

There are requirements to migrate past 10 years of data from X tool to ServiceNow as part of greenfield ITSM implementation. We need to move all Open tickets, Closed history, Knowledge Articles, User Accounts, SLA Configurations, and Attachment data etc.

If you have such experience , what will you recommend a level design or migration approach ?

Your thoughts will be appreciated.

[Tanushree Maiti]

Hi @nowGurukul_SN 

This data is foundation data and source of truth data of your greenfield implementation and must be migrated first.

• user data, including roles, groups, and locations. // Use LDAP Integration for user and group , use import set /transform map in order to get rid of redundant data.
• Migrate baseline assets and CIs to populate the CMDB before migrating tickets.
• Do not migrate raw SLA logs from the old tool. Rebuild the SLA definitions natively in ServiceNow to align with your new ITSM Standard/Professional capabilities.

Open/Closed ticket: Attempting to migrate 10 years of history is a leading cause of performance degradation and technical debt 

• Closed Ticket: load closed tickets into an archived data store or a read-only custom table to reference for reporting and auditing
• Open ticket :  Migrate in an "In Progress" state directly to active ServiceNow tables. Suppress standard SLA processing and notification triggers during this load

Attachment : Use a scripted API (e.g., REST API to ServiceNow's Attachment API) to extract legacy binaries and link them to the newly imported ticket records