Surely, the images were placed in the appropriate places. Shouldn't it recognize that there are images in a post and then BBCode wrap them to where XF placed the new images?
Thank you for reporting this issue. We need a little more detail to look into this. The importer turns image tags and Invision attachment markup into images and attachments, but copies plain text addresses as-is, so we need to know what the original Invision post contained.
Can you share the raw content of one affected post from the Invision database (the 'post' column of forums_posts), with the domain obscured if needed? We need to see whether the URLs are inside <img> tags or are plain text.
Did these images display as images in Invision before the import, or as plain text links there too?
Do the URLs point to files in the Invision 'uploads' directory that are also listed as attachments of that post in Invision, or to images stored elsewhere?
Which Invision version did you import from, and was this 2012 content originally migrated into Invision from another platform?
This is an automated assessment. A member of staff may review and update it.