Beginning in R5.0.2, some LDAP-to-Domino attribute mappings have changed. The following table summarizes how the behavior of the LDIF migration tool has also changed as a result. For more information about the attribute mapping changes in R5.0.2, see the release note "Schema changes in R5.0.2" under the Documentation updates chapter.
| attribute | R5.0 and R5.01 | R5.0.2 |
| middleName | Imported to the MiddleInitial field | Not imported. In R5.0.2, middleName is no longer included in the schema by default. |
| roomNumber | Imported to OfficeNumber field | Not imported. In R5.0.2, roomNumber maps to roomNumber. The import tool no longer imports the room number attribute, however. This is a known problem. |
| textEncodedORAddress | Imported to X400Address field | Not imported. In R5.0.2, textEncodedORAddress is no longer included in the schema by default. |
| mhsORAddress | Imported to X400Address field | Not imported. In R5.0.2, mhsORAddress is no longer included in the schema by default. |
| street | Imported to OfficeStreetAddress | Not imported. In R5.0.2, street maps to the new, hidden field street. The import tool no longer imports the street attribute, however. This is a known problem. |
| postalAddress | Imported to OfficeStreetAddress, OfficeCity, OfficeState, OfficeZip, OfficeCountry | Not imported. In R5.0.2, postalAddress maps to the new, hidden field PostalAddress. The import tool no longer imports the postalAddress attribute, however. This is a known problem. |
| homePostalAddress | Imported to HomeStreetAddress, HomeCity, HomeState, HomeZip, HomeCountry | Not imported. In R5.0.2, homePostalAddress maps to the new hidden field HomePostalAddress. The import tool no longer imports the homePostalAddress attribute, however. This is a known problem. |