Sunil,
I am in the process of migrating my customer from ITSM 6 to ITSM 7 and I have done some data analysis work to see how the fields map between the 2 versions. I have not looked at Change 5.5 but hopefully the below points will help you in what you are trying to acheive.
Data Mappings:
You will need to analyse the fields on ITSM 7 and identify the data source from Change 5.5. For e.g. these are the mappings I have for Change in ITSM 6 to go to the incident form in ITSM 7. Create a spreadsheet as below to allow you to map the fields from ITSM 7 to ITSM 5.5. Provide the users with a data dictionary for 5.5 so they can help fill in the relevant mappings.
| Field Name (DMT Incident Load Form) | Entry Mode | Input Length | Corresponding HPD 6 fields | HPD 6 Fld Length | Comments |
| Incident ID (Incident Number) | R | 15 | Change_ID_ | 15 | |
| Summary (Description) | R | 100 | Summary | 128 | input length difference |
| Notes (Detailed Description) | O | - | Description | 5000 | |
| Escalated? | O | - | Escalated_ | | |
| Status Reason | W | - | NEW ITSM 7 FIELD | | Required for different status values i.e. resolved, closed, pending. Manual data scrubbing needed. |
You will also need to map enumerated field values. For e.g.
| Data Mappings | | | |
| ITSM 6 | | | ITSM 7 |
| Urgency | | | |
| 1000-Critical | | | 3-Urgent |
| 2000-High | | | 2-High |
| 3000-Medium | | | 1-Medium |
| 4000-Low | | | 0-Low |
And Status field values which you are already aware of
| Status | |
| 0 - New | 0 - New |
| 1 - Assigned | 1- Assigned |
| 2 - Planning | 2 - In Progress |
| 3 - Scheduled | 3 - Pending |
| 4 - WorkInProgress | 4 - Resolved |
| 5 - Pending | 5 - Closed |
| 6 - Resolved | 6 - Cancelled |
| 7 - Closed | |
A lot of data analysis needs to be done and a few trial data migrations help immensely in finalising this. Every organization will have a different idea on how the target field mappings should take place, so best to check with your users. You also need to check on status history, audit trails, work logs etc as there is a big difference in the architecture of the application when you take these into consideration.
Data Migration.
I am assuming that ITSM 7 is installed on a seperate server from where Change 5.5 is installed. To move the data you can use AIE (Atrium Integration Engine) and you can specify the target form and the target field mappings. I have found it better and faster to perform any data cleansing and prepration work outside of Remedy using SQL stored procedures. However if one is comfortable with doing it within Remedy itself then that is also a possibility. Within AIE, you can specify the inetrafce_create form to push the data into.
For incident, problem and tasks, I load the data into the staging tables that are provided by the Data Management Tool (Patch 9005) and then validate, promote the data for that. The DMT does not support transaction data for change currently, but hopefully BMC will correct this in the near future.
I also used AIE for moving any audit entries direclty to the supporting audit forms.
Hope this helps.
Saby
