iCal on a MacBook: what it is called now and where events live

Searching for iCal on a MacBook usually means one of three things. A new Mac has no app by that name and the old one is nowhere in the Applications folder. An old .ics file is sitting on a drive and needs to open somewhere. Or a set of instructions written years ago refers to iCal and nothing on screen matches. All three have the same root: the app still exists, it was renamed, and the events were never really stored inside it in the first place.

That second point is the one worth reading carefully, because almost every migration problem on a Mac comes from assuming the events live in the app.

The app was renamed, not removed

iCal shipped first as a free download for Mac OS X Jaguar on 10 September 2002, then came bundled with the system as iCal 1.5 in Panther. It kept that name for a decade. With the release of OS X Mountain Lion in July 2012 it was renamed Calendar, and that is still its name. Apple's current documentation for it is the Calendar User Guide for Mac, whose version menu runs from macOS High Sierra up to macOS 27 Golden Gate.

So on any MacBook bought in the last decade, the app to open is Calendar. It is in the Applications folder and in Launchpad under that name, and an app called iCal is not going to appear in either place, which is why it looks missing. Spotlight is worth knowing about here for a different reason: the guide lists it as a way to create an event, by clicking the Spotlight icon in the menu bar, entering something like "Movie tonight at 7pm," and clicking Add on the suggested calendar event.

Two habits from the iCal era still work. The keyboard driven flow is intact, and the file formats are unchanged, which matters more. An .ics file exported from iCal in 2009 imports into Calendar today, because the format was never Apple specific. It is the iCalendar format defined in RFC 5545, which is also what Google Calendar, Outlook and almost every booking system speak.

That single fact is what keeps old calendar data from being stranded. The name changed. The container did not.

Where the events actually live

Calendar on a Mac is a window onto accounts. The events are stored by whichever account owns the calendar they sit in, and the app displays them. Apple's guide is explicit about how accounts get added: choose Calendar, then Add Account, then pick a provider such as iCloud or Google, or choose Other CalDAV Account and enter the details by hand.

For a CalDAV account the guide lists three ways in. Automatic, for when only an email address and password are needed. Manual, for when a user name, password and server address are needed. Advanced, for when a user name, password, server address, server path and port number are needed, with checkboxes for SSL or Kerberos v5 authentication. Most people never see the second and third options, but they are the reason an employer's calendar server can still be added when it is not one of the named providers.

The exception is the On My Mac section of the calendar list. Calendars created there belong to the machine rather than to an account. They sync with nothing, they do not appear on a phone, and they do not follow a login to a new Mac.

Where the calendar lives	Appears on other devices	Survives a new MacBook
iCloud account	Yes, on devices signed into the same Apple Account	Yes, after signing in
Google or other CalDAV account	Yes, anywhere the account is added	Yes, after adding the account
Subscribed calendar by URL	Only where the subscription is added	Only if the URL is added again
On My Mac	No	No, unless exported and imported

The practical rule that falls out of this table: before moving anything, click through the calendar list on the left and note which group each calendar sits under. Anything under On My Mac is the only data at genuine risk.

Checking which account an event belongs to

There is a faster way to audit this than reading the sidebar. Open an event and look at the calendar field in the event window. It names the calendar, and the calendar's position in the sidebar names the account. Events that were created years ago on a machine that never had iCloud enabled tend to be sitting in a local calendar with a name nobody remembers choosing.

Colour is a weak signal here and worth distrusting. Two calendars in different accounts can carry the same colour, and imported events lose their previous custom colour, so colour will not tell reliably which account is which after a migration.

If the sidebar shows an On My Mac group, the work is small but it is real. Export those calendars before the old Mac goes anywhere. If it shows only account groups, there is nothing to migrate: sign in on the new machine, add the same accounts, and the events arrive.

Exporting and importing, exactly as Apple documents it

The guide separates two operations that are easy to confuse, and the difference matters.

To export a single calendar's events, choose File, then Export, then Export, and pick a location. That produces a .ics file containing that calendar.

To export everything at once, choose File, then Export, then Calendar Archive, and pick a location. That produces a .icbu file, and a calendar archive is the only format that holds all calendars in one file.

Importing runs both ways from File, then Import, or by dragging the file into Calendar. For a .ics file, select the calendar to add the events to and click OK. The guide notes that importing a calendar file removes the event's previous custom colour.

For an archive file the warning is much stronger, and it is the single most expensive mistake in this whole area. Importing a calendar archive file replaces all of your current calendar information and data, and it also removes every calendar's previous custom colours. An archive is a restore, not a merge. Bringing an old MacBook's archive into a Mac that already has a working calendar does not add the old events to it. It overwrites what is there.

When the goal is to combine old and new, export individual calendars as .ics files and import those instead. It is slower per calendar and it is the safe direction.

Why the old name keeps turning up

The word iCal did not disappear from the Mac when the app was renamed, which is why the search term is still common in 2026.

It survives in the file extensions. A calendar file is .ics and a calendar archive is .icbu, and neither abbreviation was reworked around the new name. It survives in the standard itself, since the format is called iCalendar in RFC 5545 and every tool that speaks it uses that word somewhere in its documentation. It survives in a decade of third party instructions, help pages and forum answers written while the app was still called iCal, most of which are still accurate about menus and shortcuts.

It also survives in the way other apps label their export buttons. A booking system offering to add an event to a calendar frequently labels the option iCal, meaning a .ics download rather than a specific app. Clicking it on a Mac hands the file to Calendar, which is the behaviour the label implies even though the name is a decade out of date.

None of this needs correcting. The useful takeaway is that a page mentioning iCal is not necessarily out of date about anything except the app name, so instructions from that era are usually worth following rather than discarding.

Three ways to get old events onto a new Mac

The right method depends entirely on the audit of the sidebar, and doing them in the wrong order is how data gets lost.

Signing in is the first and the one that covers most cases. Add the same accounts on the new MacBook through Calendar, then Add Account, and every calendar owned by those accounts appears with its events. Nothing is copied, because nothing needed to be: the account was always the storage.

Exporting per calendar is the method for anything local. One .ics file per calendar under On My Mac, imported on the new machine into a calendar chosen at import time. It is the only method that merges cleanly with calendars that already exist, and the only cost is that custom colours are not preserved.

Restoring an archive is the last resort and belongs on a machine with nothing in Calendar yet, such as a freshly set up Mac before any account is added. It carries every calendar in one .icbu file, and it replaces all current calendar information and data on arrival. Used first, on an empty Calendar, it is efficient. Used second, on a Mac that already has a working schedule, it is destructive.

A useful order, then: sign in and add accounts, check what is missing, and only then decide between per calendar imports and a restore.

What the built in app does, and where it stops

Two features are worth knowing before deciding whether anything needs to change.

Quick Event handles plain language. Click the Create Quick Event button in the toolbar and type a description of the event. The guide's own examples are Party Feb 6, Soccer Game on Saturday from 11am-1pm, and Vacation in Bahamas Mon-Fri. Typing in Month view works too, since double clicking a day and entering something like Dinner at 6-7 sets the duration from the text.

Travel time is in the event window as a pop up menu, and this is where the built in app stops short. The guide states plainly that travel time does not update automatically when locations change. So a trip entered on Monday for a meeting across town keeps whatever figure was chosen at the time, even after the location is edited. On a schedule where back to back meetings sit in different places, that stale figure is exactly the thing that causes a late arrival, which is why handling travel time as a calculated block rather than a manual estimate is one of the few genuine reasons to look past the bundled app.

One more setting is worth switching on before judging the app, because it is off by default and it changes how events behave. Time zone support lives in Calendar, then Settings, then Advanced. With it on, an event can carry its own time zone, and choosing Floating keeps an event from moving when the calendar is viewed in a different zone. For anyone taking calls across zones, that one checkbox removes a whole class of mistake.

Neither of these is an argument for replacing Calendar. Sentence style entry and a travel time field cover a good deal of daily use. They are the two places to test against anything else, because they are the features used every day rather than the ones compared on a page.

What to change first

Open Calendar, look at the sidebar, and find out whether an On My Mac group exists. If it does, export those calendars as .ics files now, before the old MacBook is wiped or sold, and keep the archive option in reserve since it overwrites rather than merges. Once the accounts are in place, the next thing worth testing is how the event gets in at all, since typing or speaking the event is the part that repeats dozens of times a week, and Caltimate is one of the Mac calendars to line up against the built in app when that becomes the bottleneck.