HEATImg is not coming over through a HEAT Load through a HAF file.
Typically, the most common cause of this issue is not using the correct SQL client driver. If the issue is not the SQL client driver, then the truncation error typically indicates that the image is too large for the field size, which causes truncation of the binary code for the specific image (to fit the field size). (The error typically will not show again for this image since the data was truncated, but the image would no longer be intact).
One method to resolve this issue is to insert the image file from the backup HEAT database into the new Production HEAT database. This requires access to both HEAT databases where both are online. In the example SQL script below, use your current HEAT database and backup database, respectfully in <current database> and <backup database> -
INSERT INTO <current database>.dbo.HEATImg SELECT * FROM <backup database>.dbo.HEATImg;