A Google Calendar CSV import needs recognizable English column headers. Translating those headers into another language can prevent fields from being recognized even when the event text itself is valid. Prepare the file structure separately from the language used in titles and descriptions.
Start with the required columns
Google’s import guidance requires Subject and Start Date. Subject supplies the event title. Start Date supplies its starting calendar date. Check these exact header names before troubleshooting the contents of every row.
Add only useful supported fields
The documented optional headers include Start Time, End Date, End Time, All Day Event, Description, Location, and Private. Keep each header aligned with the corresponding data column. Do not assume an arbitrary spreadsheet column becomes a supported Calendar property.
Use Google’s documented date and time examples to check the representation accepted by the importer. An attractive spreadsheet display can conceal different underlying values or a locale-specific CSV export.
Check the actual CSV output
Inspect the saved text file, including its first row, separator, and representative event rows. Confirm that a title containing a comma has not shifted later fields into the wrong columns. Use a controlled import into the intended calendar and review the resulting dates and times before processing a larger migration. Keep the original file unchanged as a reference. Imported events are copies, and guests or conference information are not imported. A correct header row solves field recognition; it does not by itself verify event accuracy, eliminate existing duplicates, or establish continuing synchronization with the source spreadsheet.
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.