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 XML is
XML marks up data with nested named tags and optional attributes. It is verbose, strict about being well-formed, and can carry a schema that says what shape a document must have.
Enterprise integrations, government data feeds, RSS, SOAP services and older document formats.
What changes when you convert CSV to XML
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.
Each row becomes an element with one child per column. Header names are rewritten where they have to be, because an XML tag cannot start with a digit or contain a space, so a column called 2024 Sales becomes _2024_Sales.
What carries over from CSV to XML
One property of the CSV has no home in XML, and it is worth knowing which before you convert.
XML has no header row. The column names are repeated as keys on every record instead, which is why the result is bigger on disk than the table it came from.
The identifier 007 comes out of the XML 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 XML file goes wrong.
The quotes around Jonah "Jo" Pryce are written as the HTML entity " in the XML.