What CSV is
CSV is a text file where each line is a row and commas separate the fields. There is no type system, no formatting and no second sheet. Every value is text until something downstream decides otherwise.
Almost every database, analytics tool and spreadsheet can read and write it, which is why exports default to it.
What reStructuredText is
reStructuredText simple tables underline the header with equals signs and align columns with spaces.
Python documentation, Sphinx projects and anything on Read the Docs.
What changes when you convert CSV to reStructuredText
Reading CSV means deciding three things the file does not state: which character separates fields, how quotes work, and what encoding the bytes are in. Tablizer sniffs the delimiter from the first few lines, handles quoted fields containing commas and newlines, and reads the file as UTF-8.
The equals-sign rule under the header is what tells Sphinx the first row is a header. Without it the table renders as data with no heading.
What carries over from CSV to reStructuredText
One property of the CSV has no home in reStructuredText, and it is worth knowing which before you convert.
reStructuredText marks its header cells differently from its data cells, so the first row is written with that marker.
CSV can be read one record at a time. reStructuredText has to be complete before it means anything, so the whole table is held in memory while it is written and a file that gets cut off part way through is not partly usable - it is unusable.
The identifier 007 comes out of the reStructuredText as 007. Reading it as a number would have made it 7, and an id that changes value is worse than one that stays text.
The role "Analyst, data" survives with its comma, in one cell rather than split across two. That is the first thing to check in any converted table, and the usual place a reStructuredText file goes wrong.
The quotes around Jonah "Jo" Pryce are left as a plain quote character in the reStructuredText.