The file carries one version, not a continuously connected calendar
Importing an .ics file into Ora is a one-off action with a preview. If somebody later changes an event in the source calendar, that file does not carry the update into your plan. Check when it was exported and which information is current before relying on an old time.
ICS import is an Ora Pro feature. This guide covers reviewing a file: importing does not establish an ongoing connection to its source calendar. Provider connections are separate routes: Google Calendar still awaits real-account end-to-end acceptance; Outlook also awaits Microsoft configuration and provider acceptance. They are not presented as validated synchronization.
The ten o’clock appointment now starts at eleven
This invented example begins with a file received Monday for a Wednesday meeting from 10:00 to 10:30. You review the preview and import it. On Tuesday, the organizer announces 11:00 to 11:30 instead. The information changed after the file; do not assume the imported copy already shows eleven.
Keep the latest communication as a reference and compare the planned event with the confirmed time. A matching meeting name is insufficient: date, time, zone and duration matter too. This is not a completed account or synchronization test.
Before importing again, inspect the current plan
Do not repeatedly import in the hope that a file resolves the change automatically. Ora documents deduplication by UID + DTSTART + TZID, not guaranteed reconciliation of every external edit. A changed start can alter that combination.
First identify the old version and pending change. If importing a new file, read its preview and conflicts before accepting. If correcting through another available route, inspect the final plan and avoid retaining two commitments representing the same meeting.
- Check the preview’s date and time zone.
- Compare its time with the organizer’s latest reference.
- Review capacity and overlaps: a valid file does not create room in the day.
- After accepting a decision, reread the plan that was actually saved.
What can be omitted from import
Ora documents files up to 2 MB and 2,000 events. Import skips recurring events, all-day events, custom zones and ambiguous or nonexistent daylight-saving times. Events are clipped at midnight; capacity and overlapping appointments can block import.
Review both what the preview includes and what it omits. A weekly series existing in the source calendar does not establish that this one-off import will create it. Inspect the specific reason for missing data before manually rebuilding it or relying on it in your day.
Two references for separating formats
Google Calendar help explains its own event-import workflow. Structured publishes guidance for duplicate imported events. Checked on 24 October 2026, these sources establish no equivalence between their connectors, requirements or remedies and Ora’s.
When comparing, ask what arrives once, what stays connected and what requires review after the source changes. The file format alone answers none of those questions.
Decide from the preview, not the filename
Ora is a visual planner with spheres capped at twenty-four hours. Its demo needs no registration, and demo edits remain in that tab. The demo does not prove that you imported a calendar into a real Pro account.
Read current capabilities and terms before choosing a route. If you only need to check an appointment today, start by comparing its current confirmed time with your plan; importing does not mean staying connected to the source.