How to convert an XML export to Excel
Turn an older XML export into an Excel workbook, choose a useful layout, and check that nested records, dates, and numbers survived the conversion.
You have an old XML export, but your manager needs a spreadsheet they can sort, filter, and review. XML stores information in tagged, sometimes nested structures, so the main job is not just changing the file type. You also need to check that the records and values make sense in Excel.
You can convert the file in a browser, then review the resulting workbook before sharing it. These steps help you spot common issues such as nested data, dates that appear as text, or IDs that lose leading zeros.
Convert the XML export to Excel
- Open the converter. Use Data Converter, select your XML export from your device, and choose Excel as the output format.
- Convert the file. Start the conversion and save the resulting workbook to your device. The file is processed in your browser, not uploaded to a server.
- Open the workbook in Excel. Check the worksheet names and headings first. Confirm that each column has a clear label and that the rows contain the kind of records you expected.
- Check several records against the XML. Compare a few rows near the beginning, middle, and end of the export with the source. Look at names, dates, amounts, and any identifiers that must stay exact.
- Save a reviewed copy. Keep the original XML unchanged. Save the checked workbook under a separate name, such as
manager-review.xlsx, so you can return to the source if anything looks wrong.
Before sharing the workbook, ask what the manager needs to do with it. A short table with one row per record is usually easier to sort and filter than a worksheet that mixes summaries, details, and nested lists.
Check how the XML is organized
Repeating records
Look for a tag that repeats for each item, such as <order>, <employee>, or <product>. In a manager-friendly sheet, each repeated item usually belongs on its own row, with fields such as ID, date, and status in separate columns. Check that the workbook has not combined separate records into one cell or split one record across unexpected rows.
Nested details
An XML record can contain child tags, such as an order with several line items. That information does not always fit naturally into one flat table. Check whether the converted workbook keeps the details in a useful structure, puts them on another worksheet, or leaves them difficult to scan. Do not assume that a row count in Excel represents the number of top-level records in the XML.
Attributes and namespaces
Some XML values appear as attributes inside a tag rather than as separate child tags. Older exports may also include long namespace labels or technical fields. Check whether important values are present, and remove unnecessary technical columns from the copy you share. Keep the original workbook intact until you are sure which fields are safe to omit.
Check dates, numbers, and identifiers
Spreadsheet programs may interpret values differently from the system that created the XML. Review a few examples from every important column before relying on totals or filters.
- Dates: Confirm that dates display in the expected order and are recognized as dates if you need to sort by time. A date shown as plain text may sort alphabetically instead of chronologically.
- IDs and codes: Check long numbers, account codes, postal codes, and values beginning with zero. These may be treated as numbers, displayed in scientific notation, or lose leading zeros. IDs are labels, not quantities, so preserve them as text when needed.
- Amounts: Check the decimal places and signs in prices, balances, and percentages. A value such as
12.50should not silently become12.5if the trailing zero has meaning for the report. - Empty values: Check whether blank fields mean “not provided,” “not applicable,” or something else. Avoid replacing blanks with zero unless zero is genuinely the right value.
- Text and special characters: Look for names with accents, symbols, or punctuation. Compare them with the source file if characters look missing or changed.
If Excel has changed an identifier, do not rely on formatting alone to restore information that is no longer there. Reconvert from the original XML and check whether the value is preserved, or import the XML through Excel's data tools and treat the identifier field as text.
When the workbook needs a different layout
If the converted workbook does not arrange nested records into useful rows, Excel for Windows has an XML import route that lets you inspect the available tables. In Excel, choose Data › Get Data › From File › From XML, select the source file, then use the preview to choose or transform the data before loading it. The exact options can vary by Excel version.
Use that route when you need to select a particular repeated record or combine related details into a table. Check the preview carefully: expanding a nested list can create several rows for one parent record, which may repeat the parent fields. That can be correct for line-item reporting, but it can also make totals look too large if you count each row as a separate order.
For a very large export, check the worksheet's row and column limits before sharing it. Excel worksheets support up to 1,048,576 rows and 16,384 columns. If the data exceeds a worksheet limit, keep the full source file and ask whether the manager needs a filtered extract, a summary, or a different data format.
The Data Converter works with the file in your browser. The XML export and converted workbook stay on your device, so review the saved copy before attaching it to an email or placing it in a shared folder.
