Firstly it is always best to avoid HTML in your data especially divs. There is plenty CSS from what I can see and I’m guessing none of those styles would be used in the final blog. So it would result in a lot of inert code, not good practice and it is best to spend time getting that right now than having to fix it later.
There is a free edition of CSV 2 POST and Easy CSV Importer. Both plugins are to be upgraded again this year so they are well supported. They can create posts using any .csv file including yours as it is right now. However I recommend renaming the columns, removing spaces and special characters and uppercase.
As for comments. A separate file is advised, import them last and yes that file would need to have a pageid column. Other approaches are possible but add a little more complication.
As for data meant for custom fields. If you happen to have lists or media and they can be scraped individually. It is recommended. Even if you need to create columns named “imageone,imagetwo,imagethree,…” and so on. That allows the plugins to import images one at a time, creating proper WordPress media but also handling them in any way we want. It is usually a big plus to create the media because it offers opportunity to use gallery plugins etc.
Same for lists, I think I seen one in the sample file. If possible add list items to the .csv only and not the ul li HTML. It means the data can be used in various ways during importing i.e. creating tags or even building better lists. The mentioned plugins can still extract keywords from the final content and create tags. But if the data is organized we can tell the plugins which columns we want included as tags rather than the extraction process which is less accurate and requires more processing.
Processing is a big issue if creating thousands of posts, especially on low cost hosting. WordPress developers creating CSV importers apply measures to avoid the user causing themselves problems. Sometimes that protection can seem like a fault so developers never win. I have created a book site with one million books, easy. But only because there were no custom fields or media. These things that are advantages in a CMS like WordPress are complications when mass importing. But complications worth dealing with properly and so I highly recommend to anyone reading this. To seek advice, get recommendations on their .csv file before building the live site and try various .CSV importers.