Export an iCloud calendar to Outlook without losing the invites

The usual reason for this search is a new job. Personal life sits in iCloud because that is where a Mac and an iPhone put it, work has arrived in Outlook because that is what the company runs, and neither one knows about the other. The first double booking happens within a fortnight, normally on an evening that was already promised to somebody.

The advice on this subject is unusually stale, because the answer changed. For years the only way to see iCloud events in Outlook on a Mac was a chain of public links and web sessions, and most of the guides still describe that chain as if it were the only option. There is now a direct account setting, and knowing which of the routes applies saves an hour of following steps that no longer match the screen.

Export and sync are different requests

Worth separating before any menu gets opened, because the word export covers two jobs with different answers.

Moving a fixed set of events is a transfer. A calendar from a finished project, a schedule someone else needs to keep, a record of last year. The right output is a file, it stops being accurate the moment the next edit happens in iCloud, and that is acceptable because nothing is expected to change.

Seeing iCloud events next to work events, permanently, is not a transfer. Any file based method fails at this within days, and the failure is quiet: the events sit in Outlook looking correct while the originals move in iCloud. What this job needs is a connection, where iCloud stays the owner and Outlook displays what it holds.

A quick test settles it. If the events will ever change again, a file is the wrong answer.

The direct route in Outlook for Mac

Microsoft's current documentation states that Outlook for Mac now provides a direct option to sync iCloud calendars, which removes the need for the older workaround of subscribing to a public iCloud calendar through Outlook on the web. The steps it gives are short.

1. Go to Tools, then Accounts, and select Add an Account.
2. Type the iCloud address and select Continue.
3. Select Sign In to set up the account.
4. If the provider was not detected, use the "Not Google, IMAP, Office365, Yahoo" link at the top of the window and choose iCloud from the list.
5. Select Calendar in the navigation pane to reach the iCloud account's events.

Two conditions are worth knowing before starting. The account has to be added as an account rather than as a subscription, so this applies to an iCloud calendar the person signing in actually owns, not to somebody else's. And the sign-in may ask for an app specific password. Apple documents these as passwords used to sign in to an Apple Account from applications made by other developers, generated at account.apple.com under Sign-In and Security, available only on accounts protected by two-factor authentication. Apple also notes that supported applications reading iCloud Mail, Calendar and Contacts can be authorised with the Apple Account itself instead, so whether the extra password is needed depends on the build of Outlook in front of you. Having one generated in advance turns a failed sign-in into a paste.

This is the route to try first. If the version of Outlook on the machine offers it, everything below becomes unnecessary.

The public link route, and why it still exists

Microsoft's guidance for legacy Outlook for Mac explains the older chain and the reason for it: Outlook for Mac does not support the CalDAV or CardDAV internet standards, which is why adding an iCloud email account does not bring the calendar with it. CalDAV is the protocol iCloud calendars speak, so the calendar has to arrive by another road.

That road runs through the web, and Microsoft documents it in five steps.

1. Sign in to iCloud in a browser and open Calendar.
2. Select the share button next to the calendar and make sure Public Calendar is enabled, which reveals the calendar's address.
3. Select Copy Link.
4. In another window, sign in to Outlook on the web, open Calendar, and choose Add calendar, then From internet.
5. Paste the address, give the calendar a name, and save.

The calendar then appears under Other calendars in Outlook on the web, and because the same account is signed in to Outlook for Mac, it appears there too. Microsoft notes that this can take a few minutes and that Outlook for Mac may need restarting before the calendar shows up. The account signed in on the web has to be the same account that is in Outlook for Mac, which can be a work or school account or any Outlook address.

Apple describes the sharing side from its own end. In Calendar on a Mac, selecting Public Calendar for an iCloud calendar lets anyone view it, and Apple states that people who subscribe to a public calendar can view it but cannot change it. That is the cost of this route, and it is the same cost as any subscription: the calendar is visible in Outlook and editable only in iCloud.

The security point is easy to miss in the middle of the steps. Making a calendar public creates an address that shows the events to anyone holding it, without a sign-in. On a personal calendar that includes a home address and the name of a doctor. Sharing only a specific calendar, rather than the one everything lands in by default, keeps the exposure narrow.

The file route, and the file that will not work

When the goal really is a transfer, Apple's Calendar application produces the file, and there is one trap in the menu.

For a single calendar, Apple documents selecting the calendar in the list and choosing File, then Export, then Export. The result is a calendar file ending in .ics, and Apple states that events can be exported to an .ics file only from this command.

For everything at once, the command is File, then Export, then Calendar Archive, which produces a file ending in .icbu. This is where people go wrong, because it looks like the thorough version of the same thing. It is a local backup, not a transfer format, and Apple's warning about the receiving end is blunt: importing a calendar archive file replaces all current calendar information and data. Handing an .icbu file to a colleague is handing them something that would overwrite their calendar rather than add to it, and Outlook cannot read it at all.

So the file to produce is .ics, one calendar at a time. On the Outlook side, Microsoft documents uploading it through Add calendar, then Upload from file, choosing the file, selecting which calendar receives the events, and importing.

Apple documents one side effect of moving events by file that surprises people on return trips: importing a calendar file removes the event's previous custom colour. Events arrive wearing the colour of whichever calendar they land in.

There is one case where the web based routes cannot work at all, and it is worth checking early. A calendar listed under On My Mac is stored on that Mac and is not in iCloud, so it will never appear in the iCloud interface in a browser and cannot be published from there. Apple's own framing makes the distinction clear: with a calendar account such as iCloud or Exchange the calendars are held on the provider's servers and kept up to date across devices, while exporting and importing is how calendars in the On My Mac section get backed up, restored or moved. For those calendars the file route is the only route, and the more durable fix is to move the events into the iCloud calendar first so that everything afterwards has one source.

Import against subscribe, in Microsoft's own words

Microsoft's documentation draws the distinction more clearly than most guides, and it is the sentence that decides which route to pick.

When an .ics file is imported, the result is a snapshot of the events at the time of import, and the calendar does not refresh those events afterwards even if the owner changes them. When a calendar is subscribed to by address, Outlook connects to it and updates as the owner makes changes. Microsoft adds that the update can take more than 24 hours, although updates should happen approximately every three hours, and that for a published calendar the frequency depends on the recipient's provider.

Applied to iCloud, that means a subscribed calendar is right for a schedule that keeps moving, with the understanding that it is accurate to within hours rather than minutes. A meeting moved ten minutes ago in iCloud is not a meeting Outlook can be trusted about.

Which route fits which job

Route	Direction	Editable in Outlook	Stays current	Fits
Add the iCloud account in Outlook for Mac	Two-way account	Yes	Yes	The owner of the iCloud calendar, on a current version
Public link, subscribed via Outlook on the web	One-way view	No	Yes, within hours	Older Outlook builds, or a calendar to display only
Export .ics, upload from file	One-way copy	Yes	No	A finished calendar handed over once
Calendar Archive .icbu	Local backup only	Not supported	No	Backing up a Mac, nothing else

What none of these routes carry

Every method moves less than the calendar holds, and the losses fall in predictable places.

Invitations are the important one. A subscribed calendar shows a meeting as a block of time, so responding to it, adding a guest, or joining from the entry is not possible on the Outlook side. Only the account route, where iCloud is added as a real account, keeps the event interactive. Anyone whose reason for connecting the calendars is to accept invitations from one place needs the account, not a link.

Attachments, alarms set on the original device, and per-event colours are unreliable travellers. Apple names the colour loss explicitly for imported files, and a subscription shows the colour assigned by the receiving application rather than the original.

Time zones are the quiet failure. A calendar file stores timestamps, and events created while travelling, or all-day events that sit against a date boundary, are where a one hour or one day shift appears. Checking half a dozen known appointments after any import takes two minutes and catches it before somebody misses a call.

The gap that no calendar file has ever carried is the unbooked time. Two appointments an hour apart on opposite sides of a city are two entries in every format above and most of an afternoon in life. A calendar that treats the travel between appointments as part of the commitment surfaces that while the time is being chosen, which is the only moment it can still be fixed. How the applications on the Mac differ on this point is set out in this comparison.

What to change first

Try Tools, then Accounts, then Add an Account, and see whether iCloud appears in the provider list. If it does, add the account and delete whichever public link chain is currently in place, because a subscribed copy is where the two calendars start disagreeing. If it does not, use the public link route with one narrow calendar rather than the one that holds everything, and keep the .ics export for calendars that are finished. A Mac calendar that holds an iCloud account and a work account in one window is described in Caltimate.