The Import/Export mechanism was developed so that you could get element documentation data into or out of a 3rd party application (like Excel or a database or word or notepad or

)
The comma separated file format (.CSV) is an ASCII, human readable file, where one row of text represents one record in the element documentation database. CR/LF in the multi-line Descriptor field does not fit this file format well. CR/LF means a new RECORD in a .CSV file, not a new line in one of its comma separated fields.
So when you have a CR/LF in the descriptor field, those characters cannot be part of the export. Say you had the following in your element documentation database in DirectSOFT
Element:
X0
Nickname:
Pump1
WiringInfo:
ABC123XYZ
Descriptor:
Line1
the text in the exported .CSV file would be
X0,Pump1,ABC123XYZ,Line1
followed by other records in your documentation database:
X3,Pump10,XYZZY,Descriptor for X3
C11,MotorStarter5,,Descriptor for C11 that goes on and on for all 6 rows of 16 characters... the end
But say your descriptor for X0 was a multiline field with user entered CR
Descriptor:
Line1
Line2
Line3
.CSV can NOT do
X0,Pump1,ABC123XYZ,Line1
Line2
Line3
it must do
X0,Pump1,ABC123XYZ,Line1 Line2 Line3
where it replaces the CR/LF with a space on the same line in the .CSV file
Try adding spaces (instead of hard coded carriage-return) in the element documentation editor to cause the word to properly wrap at the right place so that the characters show up. Then, when you export, (hopefully) you'll get something like
X0,Pump1,ABC123XYZ,Line1 Line2 Line3
then when you import it, the text shows up properly.