A comma inside an event title, description, or location needs correct CSV quoting before Google Calendar import. Otherwise the importer can interpret part of that text as another field. Check the saved CSV itself rather than relying only on a spreadsheet’s neatly aligned columns.
Identify fields containing commas
Review titles such as a meeting name followed by a department, and locations containing a room and building. Google’s import guidance says a field containing commas should be enclosed in quotation marks so it is treated as one value.
Preserve the file’s column structure
Use a proper CSV export when possible instead of manually joining cell values with commas. Keep the English header row, including Subject and Start Date, intact. Review any quotation marks inside field values using the export application’s CSV handling rather than deleting meaningful punctuation.
Do not replace every comma in the whole file: separator commas between fields still have a structural purpose. Editing punctuation globally can corrupt otherwise valid event records.
Verify a representative imported event
Inspect a row containing a comma and confirm that its later date, time, and location fields remain in the expected columns. Import a controlled set into the intended calendar and examine the resulting event details. Check that the full title and description survived and that no date was interpreted as part of a location. Keep the original export for comparison. If the result is wrong, diagnose the specific row before reimporting the whole dataset. Correct quoting prevents one class of parsing error; it does not establish that the source appointments are current or that the destination contains no earlier copies.
References
Reviewed against the linked official product guidance on November 4, 2026. Features, limits, screen labels, and access can vary by account, platform, region, and organization policy.