Data that is not migrated

Due to differences in structure, function, and processes, some data in IBM® Rational® DOORS® is not migrated to IBM Rational DOORS Next Generation.

Some data structures and processes in Rational DOORS have no functional equivalent in Rational DOORS Next Generation. The Jazz platform, on which Rational DOORS Next Generation is built, provides alternative ways to do similar functions. For example, Jazz provides alternative capabilities for team collaboration, view filters and sorting, suspicion, baselines, access control, and security. You can use the Migration Metrics utility during the analysis phase of the migration to determine which data is impacted.

Rational DOORS Next Generation does not support rich text outside of the Primary Text attribute. Although the information is contained in the exported migration package, it is ignored during the import operation. This lack of support impacts the following Rational DOORS attribute types:
  • User attributes of type “Text” that contain OLE.
  • User attributes of type “String” or “Text” that contain rich text styles, such as bold and italics.

Links between objects in modules that are in the same migration package are migrated. Links between objects that are in separate packages are not migrated.

These data types are not migrated:

These Rational DOORS add-ons and integrations have no equivalent capability in Rational DOORS Next Generation. Metadata for these capabilities might be included in migrated modules, objects, and attributes, but it is not supported in Rational DOORS Next Generation. During the analysis phase, you can identify this metadata by using the Migration Metrics utility. This analysis helps you decide whether to remove the metadata during the preparation phase.

Note: This list is not exhaustive and you might have your own integration ecosystem that needs consideration.
Related concepts:
Migration process phases
Related tasks:
Getting migration metrics

Feedback