Keep the original calendar file until the import is checked
An exported ICS or CSV is a record of the source at that moment. Treat any normalized, split, or converted result as a working copy. This guide helps with file preparation; it cannot confirm that a receiving calendar will interpret every event exactly as the source application did.
1. Choose the job before changing the file
A calendar transfer, a spreadsheet report, a timezone-label cleanup, and a file-size workaround are different tasks. Start with the one you actually need instead of converting a file repeatedly until an import happens to work.
You need a spreadsheet view
Create a CSV report from an ICS file, then inspect the event fields before you share the table.
Convert ICS to CSVYou need an import-ready CSV
Map the known fields for the receiving calendar deliberately instead of assuming a generic CSV layout is accepted.
Prepare a calendar CSVA Windows timezone label needs review
Normalize only a known label; the goal is to preserve event times, not to shift appointments to a preferred zone.
Review timezone labelsThe import has a file-size limit
Split the file while retaining timezone definitions and related event groups, then import each reviewed part.
Split an ICS file2. Review times, zones, and all-day events separately
A displayed time can be a local time with a timezone, a floating time without one, or an all-day date. They are not interchangeable. Do not turn a floating time into a timezone-specific one just because the destination has a default timezone.
- Open a known morning and evening event to check that the hour and date remain plausible after import.
- Check an all-day event separately; it should not become a timed event that begins or ends on a neighbouring date.
- If a timezone name is unfamiliar, verify it against the source application before normalizing it.
3. Treat repeating events and exceptions as a group
A recurring meeting is often represented by a base event plus exceptions, cancellations, or overrides. Checking only the first occurrence is not enough. Preview a normal occurrence and an exception after import, especially around daylight-saving changes.
If an import preview does not make the recurrence understandable, stop and keep the original. Exporting again from the source calendar may be safer than manually recreating a pattern from a converted file.
4. Let the receiving calendar have the final preview
Before you confirm an import, use the destination's preview when available. Compare the number of events and inspect a sample from the beginning, middle, and end. If the destination offers a temporary calendar or draft import, use it before adding events to a shared or production calendar.
Count
Compare the source event count with the destination's preview or import summary.
Known event
Check title, date, time, and timezone against an appointment you recognize.
Sensitive details
Review attendees, locations, links, and descriptions before you share a calendar copy.
Keep a short recovery window after the import
After the destination accepts the file, check a few imported events before deleting the original or any working copies. If something is shifted or missing, the source export gives you a reliable comparison point.
Common questions
Can I fix an event that imports at the wrong time by changing its text?
Usually not. The event's date, time, timezone, and recurrence fields determine scheduling. Check the source export and the destination's documented import rules before changing a timezone label or recreating the event.
Does converting ICS to CSV make a calendar file ready to import?
Not automatically. CSV is often useful for review or for a destination that explicitly supports a documented CSV layout. It does not preserve every calendar feature such as recurrence or timezone definitions.
Should I share a calendar export without reviewing it?
Calendar files can contain event descriptions, attendees, locations, conferencing links, and recurring schedules. Review the fields and use a copy intended for the recipient before sharing it.
