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 Firebase is
JSON shaped for a Realtime Database import: an object keyed by record id rather than an array.
Firebase projects.
What changes when you convert XML to Firebase
The first repeating element is treated as the rows. Attributes are read alongside child elements and prefixed so they do not collide with a same-named tag. Nesting one level deep becomes dotted column names; deeper structures are kept as text.
Keys come from the first column. Firebase does not store arrays natively, so a keyed object is the correct shape for an import.
What carries over from XML to Firebase
Firebase can express everything XML holds about a table, so this conversion is about shape rather than loss.
Firebase wants a type for each column, and XML does not record one, so each column is typed from what its values look like. A column of digits that should stay text - a zip code, a phone number, a leading-zero id - is the usual thing to check afterwards.
The identifier 007 comes out of the Firebase 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 Firebase file goes wrong.
The quotes around Jonah "Jo" Pryce are escaped with a backslash in the Firebase.