Event import and export: the setup order that holds up

The import itself takes about a minute. The trouble starts afterwards, when a few hundred events land in the calendar used every day, carry the same color as everything else, and cannot be told apart from what was already there. At that point the choice is between deleting them one at a time or living with duplicates.

Almost all of that cleanup comes from making decisions in the wrong order. The file format gets chosen before the destination, or the destination gets chosen in a dropdown at the last second. This guide puts the decisions in a sequence that holds up, then walks through the common routes on Google Calendar and the Calendar app on a Mac.

Decide whether this is a copy or a connection

Before opening any settings page, answer one question: should the events in the destination change when the source changes?

If the answer is yes, a file is the wrong tool. An exported file is a snapshot of the moment it was made. Google's own help page says so directly:

Tip: Imported events don't stay in sync between your 2 accounts. If you want your calendars to sync, share your calendar with the other account. Source: support.google.com

A meeting moved from Tuesday to Thursday in the original account stays on Tuesday in the imported copy. For two accounts that both stay in use, sharing the calendar or adding both accounts to one calendar app keeps a single source of truth. Import and export earn their place in three situations only:

• Moving house. Leaving an account or a device for good.
• Bulk entry. Getting a spreadsheet of dates into a calendar once.
• Keeping a copy. A file on disk in case an account becomes unreachable.

If the job is not one of those three, stop here. Everything below assumes it is.

Create a landing calendar before importing anything

The single decision that prevents most cleanup is where the events go. On Google Calendar, if no destination is chosen during import, events go into the primary calendar. On a Mac, the Calendar app asks which calendar to add the events to at the end of the import, and the default is easy to accept without reading.

The fix is to create a new, empty calendar first and use it as the landing spot. Name it for what it holds and when it arrived, for example "Imported 2026-09 old work account". Apple's instructions include this step too: if needed, create a new calendar for the events before importing.

A landing calendar does three things for you:

• It can be shown alone, which makes checking the result quick.
• It can be deleted as a unit. If the import went wrong, deleting that one calendar removes every event that came in with it, and nothing else.
• It postpones the merge decision. Once the events look right, there is time to decide whether to move them into an everyday calendar or keep the landing calendar with a better name and color.

When moving several calendars, create one landing calendar per source calendar. Merging a work calendar and a personal calendar into one landing spot means splitting them apart again by hand later.

Choose the scope, then the format

Scope is limited by what the source app can produce.

Google Calendar offers two export paths, both on a computer only. Settings, then Import & Export, then Export downloads a .zip file. Inside is one .ics file per calendar. To import those back into Google Calendar, the .zip has to be opened and each .ics imported separately. The second path exports a single calendar: under My calendars, open that calendar's Settings and sharing, then choose Export calendar.

Two conditions apply to Google exports. The account needs the permission "Make changes and manage sharing" on the calendar being exported. On work and school accounts, an administrator can restrict exporting altogether, in which case the option is unavailable.

Calendar on a Mac exports one calendar at a time to .ics through File, then Export, then Export, after selecting the calendar in the sidebar. It also offers File, then Export, then Calendar Archive, which writes every calendar in the On My Mac section to a single .icbu file.

The formats behave differently enough that picking one is a real decision:

Format	Best for	Watch for
.ics	Moving one calendar, sending events to someone	Guests and conference data are not imported into Google Calendar
.csv	Bulk entry from a spreadsheet into Google Calendar	Headers must be in English; repeating events may arrive as separate one-off events
.icbu	A full copy of On My Mac calendars	Importing replaces current calendars instead of adding to them

The last row deserves emphasis. Apple's page puts it in capitals:

WARNING: Importing a calendar archive file replaces all of your current calendar information and data. Source: support.apple.com

An .ics import adds. An .icbu import swaps. Restoring an archive made last month removes anything created since then.

Route one: Mac calendars into Google Calendar

This comes up when a Mac has accumulated years of events in On My Mac calendars that never belonged to any account.

1. In the Calendar app, click the name of the calendar to move.
2. Choose File, then Export, then Export, and save the .ics file.
3. In Google Calendar in a browser, create a landing calendar for it.
4. Open Settings, then Import & Export, then Select file from your computer.
5. Pick the .ics, set the destination to the landing calendar, and click Import.

Repeat once per calendar. Three calendars on the Mac mean three exports and three imports, each into its own landing calendar.

One side effect to plan for: Apple notes that importing a calendar file removes an event's previous custom color. If colors were being used to mark event types inside a single calendar, that information does not survive. Separate landing calendars, each with its own color, are the nearest substitute.

Route two: one Google account into another

Typical cases are consolidating a personal account or taking private events out of an account that is about to be closed.

Export from the old account while signed in to it on a computer. Sign in to the new account, create landing calendars there, and import.

Decide what leaves before exporting. The account-wide export bundles every calendar into the .zip, and once they are files, it becomes harder to judge which events belong to which part of life. If a work calendar sits alongside personal ones, export the personal calendars individually instead.

Then plan for what does not travel. Google's help states that guests and conference data are not imported. Recurring meetings arrive without their attendee list or video link, as events that only the new account can see. For meetings that involve other people, asking the organizer to invite the new address produces a live invitation that stays current. The imported copy is fine for personal blocks and history.

Keep the old account open for a week or two after the move. If something turns out to be missing, it can still be exported.

Route three: a spreadsheet into Google Calendar

For exam dates, delivery schedules, or event runs kept in a spreadsheet, .csv is the shortest path. Google requires English headers in the first row. Only Subject and Start Date are required. The optional headers are Start Time, End Date, End Time, All Day Event, Description, Location, and Private.

Some habits make this go smoothly:

• Put text containing commas in quotation marks. Google's help calls this out for fields like Description. Unquoted commas shift every following column.
• Use True or False for All Day Event and Private, as the help page shows.
• Keep repeating events out of the file. A .csv has no column for a recurrence rule, and Google warns that recurring events imported from .csv may show up as a series of one-time events. Twenty separate Monday events are twenty edits when the time changes. Create the recurring ones by hand, once.
• Import a handful of rows first, into the landing calendar, including one all-day event and one timed event. Confirm those before sending the rest.

The date example in Google's help uses the month first, as in 05/30/2020, with times written like 10:00 AM. If the spreadsheet stores dates differently, check the first few imported events against the sheet before trusting the whole batch.

Checking the result in five minutes

With only the landing calendar visible, go through the result in a fixed order:

1. Count. An .ics file is plain text. Searching it for BEGIN:VEVENT gives the number of events it contains. The imported total should be close.
2. Times. Look at a few events with people in other time zones. They should sit at the same local time they did in the source.
3. All-day events. Confirm they occupy one day, not two.
4. Repeats. Open one weekly event and see whether it is a series or a single occurrence.

If the count is far off, go back to the file before importing again. Rather than importing on top of the first attempt, delete the landing calendar, create a fresh one, and import the corrected file into that, so the result is never a mix of two attempts.

If all four look right, decide what happens to the landing calendar. Moving events into an everyday calendar is possible in both apps, event by event. With hundreds of events, it is usually quicker to keep the landing calendar and simply rename and recolor it.

Making copies a routine

Export as a backup is worth doing for some calendars and not others. Apple points out that calendars in accounts such as iCloud or Exchange are stored on the provider's servers, which removes the need for manual backup and restore. Copies matter most for On My Mac calendars and for accounts that may become unreachable, such as a work account tied to a job.

Three decisions keep the routine small:

• Frequency. Match it to how much changes. A calendar that gains a few events a month needs one export a month. A copy meant as insurance against losing access can be quarterly.
• File names. Put the date first, then the source: "2026-09-15 work.ics". Files then sort in order without extra effort.
• Retention. Keep the latest three and delete older ones. Old snapshots have little use once newer ones exist, and a folder of forty near-identical files invites restoring the wrong one.

What to change first

Before the next import, create a landing calendar and import into it, nothing else. If the underlying goal is seeing several accounts side by side every day, a desktop calendar that connects to each account avoids making copies at all; the Features page lists what that looks like, and Compared with other calendars sets the options out side by side. For lists too short to justify a .csv, entering events as plain sentences is covered in the Caltimate guide.