An update on secondary calendar lifecycle changes and a new API

Since that announcement, we’ve received valuable feedback that to properly manage this new lifecycle, customers need better programmatic tools to handle secondary calendar data before it gets deleted.

To ensure you have the time and tools necessary to manage this transition smoothly, we are making two important updates:

In the coming months, we’ll introduce a new endpoint in the Calendar API that will allow developers to programmatically transfer the ownership of secondary calendars. This endpoint will require the Calendar administrator privilege.

The API will mirror the existing capabilities in the Admin console—transferring secondary calendars within the same organization without requiring confirmation by the receiving user—and introduces the additional flexibility to transfer individual calendars.

The new API endpoint will be available for integration by June 2026. An announcement and technical documentation will be published when the API goes live.

To give your teams ample time to adjust their workflows and integrate with the new API endpoint, we are officially pushing back the enforcement date for the secondary calendar lifecycle changes for paid accounts.

The new policy—where secondary calendars are permanently deleted upon the deletion of the owner's account—will now take effect on October 5, 2026, for paid accounts.

Until then, we will run a regular process for orphan calendars that auto-assigns ownership to a user who has “Make changes and manage sharing” access. This process will stop on October 5, 2026. Instead, make sure to ask the owner to transfer relevant secondary calendars to a colleague before they leave - or make sure an administrator executes the transfer using the Admin console or the new API endpoint.

Note that the changes to the secondary calendar lifecycle will still take effect on April 27, 2026, for users with personal Google accounts.

Secondary calendars owned by an organization must be owned by a user within that same organization, and ownership transfers are restricted to users in the same domain. However, you can continue to share calendars with users outside your organization—including with high-level permissions such as "Make changes and manage sharing"—provided your organization policies allow it.