You have a customised production ITSM 6 that has been running some time.
Your data is important!
You need to migrate this data to a developing ITSM 7 implementation with minimal down-time
and minimal data-loss.
 |
 |
Data Cleansing
|
|
ITSM 6 allowed type-in values in fields that must now be referentially correct.
This presents a huge problem: a high number of records cannot be inserted unless the
look-up value is translated, adjusted, or cleaned!
|
|
Complexity
|
ITSM 7 is much more complex that all previous ITSM releases.
It is basically a new product and
not an incremental update to ITSM 6.
|
|
Diary Entries
|
ITSM 7 no longer uses diary fields, instead using separate records
to represent each ITSM 6 diary entry.
|
|
Core Fields
|
The core fields such as Submitter, Submit Date,
Status History can not be migrated - losing valueable data.
|
|
|
|
|
A fixed price engagement!
|
|
No changes to either ARS server.
|
|
Mapping sessions using
complete trees of customer selected records, remigrated on demand.
|
|
Migration at API speed, multithreaded across multiple machines, over a weekend.
|
|
Post production support.
|
|
Customer provided value translations in any format;
Updates incorporated promptly.
|
|
|
|
