Move events from one calendar to another when work and home mix

The mess usually starts with a default. New events land wherever the app decided, so a dentist appointment sits on the work calendar and a client review sits on the personal one, and neither is visible to the person who needs to see it. Weeks later there are forty events in the wrong place and no obvious way to sort them without opening each one.

Moving events between calendars is not difficult in any of the major apps. What makes it frustrating is that each app hides the control somewhere different, bulk moves work in only some of them, and a small set of events cannot be moved at all no matter how the question is asked. Getting those three facts straight first turns an afternoon of clicking into about ten minutes.

Move, copy and change owner are three different operations

Three verbs get used interchangeably and produce different results.

Move relocates the event. One event exists afterwards, on the destination calendar, and the original calendar no longer shows it. This is what most sorting jobs need.

Copy duplicates it. Two events exist afterwards, and they stop matching the moment either one is edited. Copies are useful for a template, and a liability for anything whose time might change.

Change owner hands the event to a different account. Responsibility moves, not just filing. This is the operation for a handover, and the only one of the three that sends email to another person.

The failure people report most often is a copy that was meant to be a move. A meeting gets duplicated onto the shared calendar, the time changes a week later, and the shared copy keeps showing the old slot while everyone insists the calendar is correct. Deciding which of the three verbs applies before touching anything prevents that entirely.

Moving one event in Google Calendar

For a move between calendars the same account owns, the control lives in the edit screen rather than a right-click menu.

Open Google Calendar on a computer, select the event, click Edit, click the arrow next to Calendar, choose the destination, and save. The dropdown lists only calendars the account can write to, so a destination that is missing from the list means the permission on that calendar is read-only rather than editable.

The copy operation sits elsewhere, which is a useful accident. Select the event, click Options, choose a calendar to copy it to, and save. Because move and copy are in different menus, they are hard to confuse once the difference is known.

Sending an event to a calendar in someone else's account is the third operation. Select an event you own, click Options, then Change owner, enter the new owner and a message, and confirm. Two limits apply. An event with more than 200 guests cannot be transferred to another owner or calendar at all, and the new owner has 60 days to accept the transfer before it lapses, with the original account remaining the owner until then.

Bulk moves in the Calendar app on a Mac

Google Calendar in a browser has no multi-select, which is why sorting forty events there is miserable. The Calendar app on a Mac does, and it is the fastest route for a cleanup even when the events themselves live in Google.

Apple documents four ways to change an event's calendar:

• Double-click or force click the event, then choose a calendar from the colour-coded pop-up menu in the top-right corner of the event window.
• Drag the event onto a calendar in the calendar list. If the list is not visible, choose View, then Show Calendar List.
• To move several at once, Command-click each event to select them, Control-click one of the selected events, then choose Calendar and the destination.
• To copy rather than move, select the events, choose Edit then Copy, select the destination calendar, and choose Edit then Paste.

The third option is the one that turns the job into minutes. Switch to Month view, Command-click the ten personal appointments sitting on the work calendar, and reassign all of them in one menu. Because the app writes back through the account's sync connection, the change appears in Google Calendar on every other device shortly afterwards.

For moving an entire calendar's contents rather than a selection, Apple points to export and import instead. Choose File, then Export, then Export to write a single calendar out as an .ics file, then File and Import to read it into another calendar. Two details matter: importing a calendar file removes the event's previous custom colour, and Apple's separate calendar archive format, the .icbu file produced by File, Export, Calendar Archive, is a restore rather than a merge. Importing an archive replaces all current calendar information, so it belongs in a backup workflow and never in a tidy-up.

Outlook on the web, and why subscribing is not moving

Outlook on the web handles the same file. Choose Add calendar, then Upload from file, browse to an .ics file, pick which calendar receives the events, then import and save.

Microsoft is explicit that this is a snapshot. An imported .ics gives the events as they stood at the moment of import, and the calendar does not refresh them afterwards even if the original owner changes something. Subscribing from the web is the live alternative, but it is a slow one. Microsoft notes that changes to a subscribed feed can take more than 24 hours to appear, and that updates typically happen roughly every six hours.

That gap is the reason a subscription cannot stand in for a move. Anything whose time might change on the day it happens, which describes most meetings, should not be read through a feed that may be six hours behind. Subscriptions suit fixed schedules: holidays, term dates, a sports fixture list.

Route	Multiple events at once	Guests survive	Result
Google Calendar edit screen	No	Yes	One event, moved
Google Calendar Options, copy	No	Partly	Two independent events
Mac Calendar, Command-click	Yes	Yes	Events moved in place
Export and import an .ics file	Yes	No	Copies without attendees
Subscribe to a feed	Yes	No	Read-only, refreshed slowly

The fourth row is the one that surprises people. Google states that when an event is imported, guests and conference data for that event are not imported, so the file route trades attendee lists for speed. For a batch of personal appointments that costs nothing. For client meetings it is the wrong trade.

The events that refuse to move

Some events will not move by any method, and knowing the list in advance prevents a long search for a missing menu item.

Google's reference for the operation behind a move states that only default events can be moved, and that birthday, focus time, events created from Gmail, out of office and working location events cannot be. These are generated rather than authored. A birthday comes from a contact record, an out of office block comes from a different object type, and an event created from a flight confirmation in Gmail belongs to the mail that produced it.

The practical consequence is that a calendar can never be made perfectly tidy by moving things. Where those generated events are cluttering the view, the answer is visibility rather than relocation. Turn the relevant calendar off in the sidebar, or group calendars into sets so that the work view and the personal view show different combinations. Hiding is reversible in one click, while a move is not.

A second group resists the file route rather than the menu. Events carrying a Google Meet link keep the link when moved inside the app, but transferring an event also changes which video conferencing policies apply to it, so a meeting that admitted external guests under one calendar may behave differently under another. Any event with more than 200 guests is blocked from transfer outright and has to be recreated with fresh invitations. Between those two rules, the large recurring all-hands is usually the one event on a calendar that has to be rebuilt rather than relocated, and it is better to find that out while planning than halfway through.

Recurring series and the question after Save

Moving a recurring event raises a question at the worst moment. After a change is saved, Google Calendar asks which occurrences it applies to: this event, this and following events, or all events.

The right answer follows the reason for the move.

• A single occurrence sitting in the wrong place, usually because it was created separately, takes this event.
• A change of arrangement from a given date, such as a standup that becomes a team-wide meeting, takes this and following events.
• An original setup that was simply wrong, such as a series created on the personal calendar from the start, takes all events.

Choosing all events reaches backwards through every past occurrence, which is the outcome nobody expects and the reason to read the dialog rather than dismissing it. Choosing this and following events repeatedly is also worth avoiding, because each split leaves another series behind and after three of them no one can tell which series is live.

When an event genuinely belongs in two calendars

Sometimes the goal is not to move an event but to have it in two places: a shared team calendar showing that the slot is busy, and a private calendar holding what the meeting is actually about.

Copying by hand is the wrong tool for that, because the two copies drift the first time the time changes. Two better options exist. Sharing the calendar itself gives one set of events visible from both accounts, staying in sync because there is only ever one event. Or the event can be written to both calendars at creation time, with one entry carrying the detail and the other showing only that the time is taken.

That second pattern is worth setting up once rather than maintaining by hand. A desktop calendar that can register a single event to several calendars, including a public and a private version of the same slot, removes the whole class of problem this article describes: events stop landing in the wrong calendar because the right destinations were chosen as the event was entered. The Features page lists what that covers, Entering events shows how a single line of text becomes an event with its destination already set, and Travel time covers the related case where moving an event between calendars also changes how much travel sits around it.

What to change first

Find the default calendar that new events land in and change it to the one you use most, because that single setting causes most of the misfiling. Then do the backlog in one pass with Command-click in the Calendar app on a Mac rather than one event at a time in a browser. If the same event genuinely needs to appear on two calendars, Caltimate can write it to both at once instead of leaving two copies to drift.