Google Calendar Ownership Changes: Developer Guide

What changed

Until 2026, deleting a Google account often left its secondary calendars intact. Shared team calendars, project calendars, and Google Classroom calendars could continue to exist as "orphans" -- no owner, but still accessible to subscribers. According to Google's November 2025 announcement, every secondary calendar now has a single, dedicated owner.

The important rollout detail is that the deletion behavior is split. Personal Google accounts start losing orphan calendars on April 27, 2026. Google Workspace accounts do not switch to deletion until October 5, 2026, and Google says orphan Workspace calendars continue through an auto-assignment process until that date when another user already has Make changes and manage sharing access. If your integration creates calendars on behalf of users, or your organization relies on calendars created by former employees, you still need to act before the enforcement date that applies to you.

Timeline

The March 2026 update pushed the Workspace deadline from the originally planned date to October 5, giving admins more time. Personal account enforcement starts April 27 as scheduled.

What breaks

Shared team calendars

Once the policy is enforced for the relevant account type, a team calendar created by a departing employee is deleted when their account is removed unless ownership was transferred first. Every subscriber -- colleagues, bots, integrations -- loses access. Events, attachments, and meeting notes vanish. For Workspace accounts, Google says the current auto-assignment behavior continues until October 5, 2026.

Google Classroom calendars

Classroom calendars are secondary calendars owned by the teacher who created the class. After the lifecycle policy takes effect for that account type, deleting that teacher's account can also delete the Classroom calendar unless ownership is transferred first.

Service account-created calendars

If your app creates calendars using a service account or a dedicated "bot" user, those calendars are owned by that account. Once lifecycle enforcement applies, disabling or deleting that owner account can mean losing every calendar it created unless you transfer ownership first.

Suspended accounts

Suspending a user (without deleting) preserves their calendars. Only super admins can modify events on suspended accounts. This is the safe path for temporary offboarding.

The new ownership transfer API (June 2026)

Google is launching a new Calendar API endpoint that allows programmatic ownership transfers. According to the March 2026 blog post, the API will:

• Transfer secondary calendars within the same organization without requiring confirmation from the receiving user
• Support transferring individual calendars (not just bulk transfers)
• Require the Calendar administrator privilege
• Restrict transfers to users within the same domain

Until the API launches, use the Google Workspace Admin console to transfer calendars manually: Admin console > Apps > Google Workspace > Calendar > Data transfer.

Audit your calendars now

Find calendars owned by accounts that might be deleted. The CLI can list all calendars for any connected account:

# List all calendars for the connected account
nylas calendar list --json | jq '.[] | {id: .id, name: .name, is_primary: .is_primary}'

# Example output
# {
#   "id": "cal_abc123",
#   "name": "Team Standup",
#   "is_primary": false
# }
# {
#   "id": "cal_def456",
#   "name": "Project Phoenix",
#   "is_primary": false
# }

Cross-reference non-primary calendar owners against your user directory. Any calendar owned by a departing user needs an ownership transfer before you delete their account.

For Workspace admins

# Manual transfer path (until June 2026 API):
# Admin console > Apps > Google Workspace > Calendar > Data transfer
# Select source user, destination user, and which calendars to transfer

# After June 2026: use the new Calendar API endpoint
# POST /calendars/{calendarId}/transferOwnership
# (endpoint details TBD when Google publishes documentation)

Developer checklist

1. Audit calendar creation -- Find every place your app creates secondary calendars. Which account owns them?
2. Use a persistent service account -- Don't create calendars under individual user accounts if those users might leave
3. Build transfer into offboarding -- Before deleting a user account, transfer their secondary calendars to another owner
4. Watch for the June 2026 API -- When the ownership transfer endpoint launches, integrate it into your user lifecycle automation
5. Suspend before deleting -- Suspending preserves calendars. Delete only after you've confirmed all calendars are transferred
6. Handle cross-domain limits -- Ownership can only transfer within the same domain. Multi-domain Workspace setups need extra planning

How this affects multi-provider apps

Google isn't the only provider changing calendar behavior. Microsoft deprecated EWS for Exchange Online (October 2026), and Apple's CalDAV has always required app-specific passwords. If your app works with multiple calendar providers, hardcoding provider-specific ownership logic creates maintenance burden.

# The CLI abstracts provider-specific calendar operations
# Same commands whether the account is Google, Outlook, Exchange, or iCloud

# List events
nylas calendar events list --days 7

# Create an event
nylas calendar events create \
  --title "Team Standup" \
  --start "2026-04-07 09:00" \
  --end "2026-04-07 09:30" \
  --participant alice@company.com \
  --participant bob@company.com

Provider-side ownership rules still apply to the underlying calendar, but your code doesn't need to handle the differences.

Frequently asked questions

When do orphan Google Calendars get deleted?

April 27, 2026, for personal Google accounts. October 5, 2026, for Google Workspace accounts. An orphan calendar is one where the owner's account has been deleted and no new owner was assigned.

What is the new ownership transfer API?

Google is launching a Calendar API endpoint in June 2026 for programmatic ownership transfers. It requires Calendar administrator privilege and restricts transfers to users within the same organization.

What happens to a shared calendar when the owner is deleted?

For personal Google accounts, the calendar and all its events are permanently deleted starting April 27, 2026. For Google Workspace accounts, that deletion behavior starts October 5, 2026. Until then, Google says orphan Workspace calendars continue through auto-assignment when another user already has sharing-manager access. Transfer ownership before deleting the account to prevent data loss.

Does suspending an account delete calendars?

No. Suspending a Google Workspace user preserves their calendars. Only super admins can modify events on suspended accounts. Suspend first, transfer calendars, then delete.

Next steps

• Manage Google Calendar from the CLI -- create events, check availability, manage calendars
• Manage calendar from the terminal -- the cross-provider calendar guide
• EWS to Graph migration guide -- another provider-side deprecation affecting calendar developers
• Manage Outlook calendar from the CLI -- Microsoft 365 calendar management
• Give AI agents email and calendar access via MCP -- connect Claude or Cursor to your calendar
• Full command reference -- every flag and subcommand documented