Next you have to map DOORS Module Attributes to Codebeamer Tracker fields.

By default only the object Id, Summary and Description are mapped automatically, all other Attributes need manual mapping.

For choice attributes, choice values also have to be mapped to Codebeamer ALM's choice options (missing choice options can be created via New, if necessary). For example, DOORS Attribute Priority mapped to Codebeamer Field Business Value:

If there are lots of DOORS choice values, that all need to be mapped to new target choice options, you can automatically map all of them at once:

If you want to import an attribute, but there is no appropriate target tracker field yet, you can add a new tracker field, based on the DOORS attribute definition, via New

For example, map DOORS Attribute Status to a new custom field named DOORS Status:

If there are lots of DOORS attributes, that need to be mapped to new target fields, you can also use the Attributes Import all function, to automatically maps all attributes,

To new target fields, whose name and type are derived from the attribute.

You can also Ignore all attributes, whose name starts with a selected prefix.

DOORS modules can also have special attributes, whose values are computed upon access via the DOORS Extension Language (DXL).

At the end of the Attributes mapping, you should also decide, whether to import or not:

Unless you have specific reason, Attachments should always be imported, because this includes Pictures and OLE objects embedded in the DOORS requirements text.

If you want to make a clean cut and only import the current head revision of the DOORS module, then you should not import Users, Discussions and History.

If you want to migrate from DOORS to Codebeamer including the past, then you should at least import Users and History.