Google Calendar export: choose the scope and hand off a dated copy

For a computer-based Google Calendar export intended for another Google account. First decide whether the recipient needs a saved event copy or ongoing shared visibility. Google says imported events do not stay in sync between accounts; its import guide points to calendar sharing when synchronization is wanted. Resolve the sharing permissions separately before choosing that route. Google, “Export from a different Google Account”.

Choose what to export

1. Identify the source account and calendar, the intended recipient and the purpose. Google requires Make changes and manage sharing permission for export. Seeing a calendar, or having a lesser editing role, does not establish that requirement. Work or school administrators may restrict export; if blocked, ask the administrator rather than assuming ownership or changing sharing settings. Export is available on a computer, not the Calendar app. Export prerequisites.
2. Select the needed scope before using the export control:

Intended scope	Documented computer route	File
One calendar	Under My calendars, point to its name → More → Settings and sharing → Calendar settings → Export calendar	.ics
All calendars covered by the export permissions	Settings → Import and export → Export	.zip containing individual .ics files

These routes come from Google's “Export a single calendar” and “Export all calendars”. Do not equate every visible or subscribed calendar with permission to export it. For a one-calendar handoff, choose that scope so unrelated calendars are not included.

Prepare the destination and handoff

Before an authorized import, identify the receiving Google account and destination calendar. Google's computer import route is Settings → Import & Export → Select file from your computer, then choose the calendar and Import. The default destination is the primary calendar, so an unspecified destination is a reason to pause. For a ZIP, extract the individual ICS files and import the intended files separately. Google, “Step 2: Import events into Google Calendar”.

Google's import guidance also says guests and conference data are not imported. CSV imports may turn repeating events into separate one-time entries. Neither statement proves that an ICS transfer preserves every other field, recurrence exception or time-zone interpretation. If retaining invitation relationships, conferencing or exact recurrence behavior is essential, resolve that requirement before treating this as a complete migration. A downloaded file alone establishes no successful restoration or notification.

As an editorial handoff practice, record the actual export date, source-calendar scope and intended destination only after those facts are known. Label the file as a dated copy; later source edits do not become synchronized changes through this import route. Confirm privately which files the recipient is authorized to receive. Keep exports, event details, guest addresses and secret calendar links out of public reports. A proposed handoff is not evidence that a file was exported, sent or imported.

Stop with a specific question if the export permission, destination, recipient authorization or required retained information is unresolved. This procedure supplies no live account action, repeat-import/duplicate handling rule, cleanup guarantee or cross-product migration recipe.

Evidence and refresh

Google Calendar Help export and computer-import pages were inspected 2026-10-05T05:11:12Z. No publication/update date was visible. The export source uses English (UK); the import source uses English. Relevant sections are linked above. Recheck before use if menus, permissions, organization policy or needed fields differ, and by 2026-11-05T00:00:00Z.

The author manually checked twelve synthetic reader decisions against these instructions and sources. These were editorial boundary checks, not calendar tests. No account, export file, import result, synchronization, invitation or roundtrip fidelity was observed. A distinct internal checker reopened both official pages and checked six additional decision boundaries on 2026-10-05T05:14:03.837864Z. Author and checker share the site operator; these source and document checks supply no formal independent review. Useful feedback names the exact revision, unclear step, interface/context and public source or observed result, without private calendar data.

Format: source-based procedure under the calendar contribution standard [current article]. No event fixture or temporal calculation is claimed.