What Happens to Google Calendar Events When an Employee Leaves (and How to Transfer Them)

By Patronum

November 13, 2026

Read Time: 6 mins

What Happens to Google Calendar Events When an Employee Leaves (and How to Transfer Them) image

What happens to events when an account is suspended or deleted?
What changed for secondary calendars in October 2026?
Which transfer route should you use?
How do you transfer a leaver’s calendar for a planned departure?
What if the exit is urgent?
How do you remove a former employee from other people’s events?
What if events were never transferred?
How Patronum handles calendars at offboarding
FAQ
Sources

If you suspend or delete an account without handling its calendar, the meetings it organized stay on guests’ calendars with no organizer who can change or cancel them, and booked rooms stay blocked. For a planned departure, transfer the user’s secondary calendars and future events in the Admin console before you suspend the account.

Need to take a former employee off other people’s meetings instead? Jump to removing a former employee from calendar events.

What happens to events when an account is suspended or deleted?

The events carry on without anyone able to manage them as organizer. Google says that if you delete or suspend a user without managing their events, the events lose an organizer who can update or cancel them, and they can block meeting rooms and resources (Google). The account state decides what you can still do:

Account state	What happens to their calendar
Suspended	Events stay in Calendar and only super admins can modify them. Events stay visible on invitees’ calendars, and new invitations to the user are blocked (Google). Owned secondary calendars are suspended too.
Deleted	Secondary calendars and their events are deleted, and no further transfers are possible. The primary calendar comes back only if you restore the user within Google’s restore window (Google).
Deleted, with auto-cancel on	Google cancels the user’s future events 21 days after deletion. This doesn’t apply to users deleted before you turned it on.

So the super-admin exception matters while the account is suspended. Once it’s deleted, Google says organizer-less events can’t even be found from the Admin console.

What changed for secondary calendars in October 2026?

Secondary calendars now follow their owner. On 5 October 2026, Google began an extended rollout so that when a user is suspended, the secondary calendars they own are suspended as well, and when the user is deleted, those calendars are deleted. Google’s advice is to transfer ownership before the account is suspended or deleted (Google Workspace Updates).

That turns a team calendar one person happened to create into a leaver risk. Treat it as a separate job from the leaver’s own meetings:

Secondary calendars: for planned departures, transfer secondary calendars before suspension, following Google’s lifecycle guidance. We haven’t verified how the transfer behaves after the owner’s suspension.
Primary-calendar events: Google’s Admin console transfer works on an undeleted user, so you can run it before deletion. Doing it before suspension is still the cleaner order.

Which transfer route should you use?

Use Secondary calendar transfer for calendars the leaver owns and Events transfer for their meetings. The other routes cover narrower cases.

Route	Who can run it	What it moves	What it doesn’t
Admin console: Events transfer	Admin with the Calendar privilege	Future, non-private events on the primary calendar with at least one guest or resource	Past events, private events (canceled), secondary calendars, users on litigation hold
Admin console: Secondary calendar transfer	Admin with the Manage Calendars privilege	All of the user’s secondary calendars, to a user in the same organization	Anything outside your organization
Transfer while deleting the user	Super admin	Primary calendar data, with an option to release booked resources	Secondary calendars (transfer those first)
The employee, before leaving	The calendar owner	Secondary calendars and single events they own	The primary calendar
Admin console: Events cancellation	Admin with the Calendar privilege	Cancels future events and frees resources, without notifying guests	Can’t be undone

How do you transfer a leaver’s calendar for a planned departure?

Work through these while the account is still active.

Transfer secondary calendars. Go to Menu > Apps > Google Workspace > Calendar > Manage Events & Calendars > Secondary calendar transfer. Enter the From user and To user, then click Transfer Secondary Calendars. Google moves them one at a time, so a long list takes a while. Google’s on-screen note says the original owner can still change calendar settings and manage sharing after the transfer, so review sharing on each moved calendar.
Transfer or release the events. In the same area, click Events transfer and enter the leaver’s username. Check Transfer events to other user, enter the new owner and click Transfer Events. To free rooms without keeping the meetings, check Release resources instead.
Wait, then check. Google says the transfer starts about 10 minutes later and can last 15 minutes. The leaver’s events then appear as a new secondary calendar in the new owner’s calendar list.
Check video meetings. Meet settings follow the owner of the calendar an event sits on, and Google’s Meet help says a meeting link on a non-primary calendar can stop working when its creator leaves (Google Meet Help). Open a few transferred recurring meetings and confirm the link and organizer.
Cancel what nobody needs. Events cancellation removes future events without sending notifications. Google warns it can’t be undone.
Optional: turn on auto-cancel. Under Manage Events & Calendars > Events of deleted users, check Silently cancel future events of deleted users and click Save.

Google Admin console Calendar settings page Manage Events & Calendars with Events cancellation, Events transfer, Events of deleted users set to ON, and Secondary calendar transfer — Manage Events & Calendars in the Google Admin console (Apps > Google Workspace > Settings for Calendar). Silently cancel future events of deleted users is ON.

If you’re deleting the user anyway, a super admin can also transfer primary calendar data in the delete dialog under Data in other apps, with the option to release resources booked in the user’s events. Do the secondary calendar transfer first.

Litigation holds change the plan. Google says events of a user on litigation hold don’t transfer, so agree the route with whoever owns the hold.

What if the exit is urgent?

Contain access first. Suspend the account straight away and handle the calendar afterward; a blocked room is a smaller problem than a hostile leaver who can still sign in. Expect owned secondary calendars to be suspended with the account. A super admin can still modify the suspended user’s events, and Events transfer or Events cancellation can follow. The immediate offboarding guide covers the full order.

How do you remove a former employee from other people’s events?

There’s no bulk remove-attendee option among the Admin console’s calendar event management tools. When the leaver was a guest rather than the organizer, their address stays on each event’s guest list. A suspended user doesn’t get new invitations, so the harm is mostly clutter and confusion in recurring meetings.

Your options:

Ask each organizer to remove the guest from their own events.
Script it against the Google Calendar API, which needs development time and testing.
Use a tool that does it as part of offboarding. Patronum’s offboarding policy has a Remove user as an attendee option (Patronum).

What if events were never transferred?

You’ll need event IDs. Google’s cleanup page has you open the event in Google Calendar, use Options > Troubleshooting Info and take the part of the Event field before the underscore, then delete the event from each invitee’s calendar or by ID with the Calendar API (Google). To free a room, delete the orphaned event from the room’s own resource calendar.

How Patronum handles calendars at offboarding

Patronum is a Google Workspace management platform whose offboarding policies can transfer a leaver’s primary and secondary calendars, delete all or only future events, remove the leaver as an attendee and remove them from shared calendars (Patronum). Transfers go to the policy’s executor, the account Patronum moves data to, which can be the leaver’s manager (Patronum). That makes the attendee cleanup, the hardest part to do natively, the same for every leaver.

You scope a policy to an offboarding organizational unit, a Google Group or all users, with conditions such as End Date or Suspended. Policies run hourly by default (Patronum). We haven’t tested the order in which actions run inside a single policy, so don’t rely on one policy to transfer secondary calendars before it suspends the account. For a planned exit, run the calendar transfer while the account is active (for example, from a policy scoped to an offboarding OU) and suspend afterward.

For the full leaver sequence, see the Google Workspace offboarding process and the employee offboarding checklist.

FAQ

Can I transfer a former employee’s past calendar events?

The Admin console’s Events transfer operation moves only qualifying future events from the primary calendar. Transferring ownership of a secondary calendar is a separate operation; don’t apply the primary-calendar restriction to it. If you need past meetings for records, look at Vault coverage and exports with whoever owns retention.

Can the employee transfer their own calendars before leaving?

Yes, for secondary calendars and single events they own. Google says the new owner has 60 days to accept, must be in the same organization, and events with more than 200 guests can’t be transferred this way (Google Calendar Help). Start early in the notice period.

If your team offboards more than a few people a month, manual calendar cleanup gets missed. See how Patronum’s offboarding policies transfer calendars, clear future events and remove leavers from other people’s meetings as part of each exit.