Excel CSV Format Differences: Export Compatible Files from Microsoft 365 and Excel 2019
Question details
The user needs to understand why CSV files exported from different Excel versions may be interpreted differently by external software.
- Product
- Microsoft Excel CSV export and WPS Spreadsheet
- Device & OS
- not provided
- Scenario
- A CSV file generated by Microsoft 365 or Excel 2019 is being imported into external software, such as a laboratory robot, and the receiving system requires consistent data formatting.
- Observed behavior
- The external software may read characters, columns, formulas, decimal values, or line endings differently depending on the CSV export settings and Excel version.
Check the receiving software documentation for its required encoding, delimiter, decimal separator, line ending, quotation mark, and column order. Prepare a small test dataset containing accented characters, decimal values, formulas, and empty fields so you can compare exports safely.
Export a UTF-8 CSV with the receiving system’s required settings
Use this method when the external application supports UTF-8 and requires a consistent delimiter and text encoding.
CSV files do not store all workbook formatting and may be interpreted according to the receiving software’s regional settings. Selecting UTF-8 and matching the required delimiter helps preserve text and column boundaries across Excel versions.
If the export dialog does not provide the exact delimiter or line-ending option required by the receiving software, generate a small sample and verify it with the target application before exporting the complete dataset.
Open the laboratory robot or receiving software documentation and record its required encoding, delimiter, decimal separator, line ending, quotation mark, and column order.
Open the workbook in WPS Spreadsheet or Excel and verify that headers, column order, decimal values, and date values match the receiving specification.
Select formula cells, use Copy, then choose Paste Special > Values so the CSV contains calculated results instead of formulas that the receiving software may not understand.
Select File > Save As, choose CSV UTF-8 (*.csv) when available, and confirm the CSV format when prompted.
In the CSV export options, select the delimiter required by the receiving system, then import a small sample file and compare every column with the original worksheet.
Compare exports and standardize regional settings
Use this diagnostic method when files from Microsoft 365 and Excel 2019 produce different columns or numeric values in the same external application.
Standardize CSV exports with WPS Spreadsheet
WPS Spreadsheet can open the source workbook, clean and standardize its columns, convert formulas to values, and export a UTF-8 CSV for testing with laboratory or other external software. Its familiar spreadsheet interface helps users migrate from Excel while preserving common workbook formats.
- 1. Open the workbook: Launch WPS Spreadsheet and select File > Open to load the Excel workbook.
- 2. Clean and verify the data: Check the headers, column order, dates, decimal values, empty fields, and special characters before exporting.
- 3. Paste formulas as values: Select formula cells, choose Copy, then use Paste Special > Values to replace formulas with their displayed results.
- 4. Export the CSV: Choose File > Save As, select CSV UTF-8 (*.csv) when available, and set the delimiter required by the receiving software.
- 5. Validate a sample import: Send a small exported CSV to the target application and confirm that every column and value is interpreted correctly.

Frequently Asked Questions
Why can the same CSV file be read differently in Microsoft 365 and Excel 2019?
Excel versions may use different available encoding options, regional settings, delimiters, line endings, or CSV handling behavior. The receiving software may also apply its own rules when interpreting the file.
Should I select CSV UTF-8 for a laboratory robot or other external device?
Select CSV UTF-8 when the receiving system supports UTF-8. If the device requires another encoding, follow its import specification and test a small file before exporting the full dataset.
Why are CSV columns shifted after import?
The exported delimiter may not match the delimiter expected by the receiving software. Commas, semicolons, tabs, quotation marks, and regional list-separator settings can all affect column boundaries.
Can formulas remain in a CSV file?
CSV exports generally store text and calculated results, not workbook formulas in a way that external software can evaluate reliably. Convert formula cells to values with Copy > Paste Special > Values before exporting when the recipient needs fixed results.
How can I test whether encoding is causing the import problem?
Create a small CSV containing accented characters and other non-ASCII text, save it as CSV UTF-8, and import it into the target software. If characters are corrupted, confirm the required encoding with the device documentation and export using that encoding.




