Move a Google Calendar to another account and keep every event

A calendar that has to end up in another Google account is rarely a clean job. Someone is leaving the company and the recurring client reviews live on their personal calendar. A side project outgrew a private address. A work account is being shut down at the end of the month and nobody knows whether the team calendar goes with it. The word people reach for is "move", and that single word hides three different operations with three different outcomes.

Three operations sit behind the word move

The first is ownership transfer. The calendar keeps its identifier, its events, its guest lists and its sharing settings, and a different account becomes the owner. Nothing is duplicated, which is what most handovers actually need.

The second is export and import. A copy of the events is written to a file, and that file is read into a calendar in the other account. Two separate calendars exist afterwards, drifting apart from the moment the import finishes.

The third is sharing. The calendar stays where it is and the other account is given permission to read or edit it. Nothing moves at all, which is often the right answer when both accounts belong to the same person and both will stay open.

Picking the wrong one is expensive in a specific way: ownership transfer is the only route that keeps guest lists and event history intact, and it is also the route with the most preconditions. Checking those preconditions first saves an afternoon of re-inviting people.

What can and cannot be transferred

Google's help centre is explicit about the boundaries, and they decide the plan before anything else does.

The primary calendar, the one assigned automatically at first sign-in, cannot be transferred. Only secondary calendars can change hands, meaning calendars that were created deliberately, or a group calendar shared with the account. If the events that matter are sitting on the primary calendar, there is no ownership transfer to perform. They have to be exported, or moved onto a secondary calendar first and transferred from there.

Events with more than 200 guests cannot be transferred to another owner or another calendar at all. A company all-hands does not travel. It has to be recreated and the invitations sent again.

For work or school accounts, the new owner must be in the same organisation. Handing a Google Workspace calendar to a personal Gmail address is not an available path, which catches most departure handovers.

Finally, timing. After a calendar or event is transferred, the new owner receives an email with a link, and has 60 days to accept. Until they accept, the original account is still the owner. A transfer started on someone's last day, with nobody left to click the link, expires quietly.

One detail is worth knowing for the accounts that are about to be closed: deleting a Google Account also deletes every calendar it owns. Transferring ownership is the documented way to keep a calendar alive past the account that made it.

Transferring ownership of a calendar you own

Only the current owner can start this, and it runs from a computer rather than the mobile app.

1. Open Google Calendar and find My calendars on the left.
2. Click Options next to the calendar, then Settings and sharing.
3. Under "Shared with", the other account has to already be listed. If it is not, add it first.
4. Open the drop-down next to that person and choose Transfer ownership.
5. Confirm.

The account receiving it gets the email and the 60 day clock starts. Once they accept, the original account's permission level drops to "Make changes and manage sharing", which means the events stay visible and editable from both sides. For a handover inside one organisation this is usually the ideal end state: the new owner is responsible, the old owner can still fix a typo.

Events carrying a Google Meet link deserve a second look. Transferring an event also changes which video conferencing policies apply to it, so a meeting that worked for external guests under the old account may behave differently under the new one.

When ownership transfer is not available, export and import

If the calendar is primary, or the destination is outside the organisation, the route is a file.

Export runs from a computer only, never from the Google Calendar app, and requires the "Make changes and manage sharing" permission on the calendar being exported. On work or school accounts, an administrator may have restricted export entirely.

To take everything: Settings, then Import & export, then Export. A .zip file downloads, containing one .ics file per calendar. To take a single calendar: hover its name under "My calendars", open Settings and sharing, and click Export calendar for a single .ics file.

The import side runs in the destination account, from the same Import & export screen. Click Select file from your computer, pick the .ics or .csv file, then choose which calendar receives the events before clicking Import. That choice matters, because the default destination is the primary calendar. A .zip file has to be unpacked first and each .ics imported one at a time.

Two failure modes on this route are documented and easy to walk into. The first shows up as a "Feed processing error" when the public address in iCal format is used to pull the calendar out. Google's answer is to use the secret address in iCal format instead, and if no secret address is offered, the calendar cannot be exported that way at all. The second involves .csv files. Google Calendar will only read a .csv whose header row is written in English, with Subject and Start Date as the two required columns, so a spreadsheet exported from a localised tool usually has to be relabelled before the import will take.

Moving single events instead of the whole calendar

Not every handover needs the calendar. Often three recurring client reviews are the only things that have to change hands, and moving those individually avoids every precondition attached to a calendar transfer.

Two operations exist at the event level, and the distinction matters. To send an event to a calendar in someone else's account, open it, click Options, then Change owner, enter the new owner and a message, and confirm. To send an event to another calendar that the same account already owns, open the event, click Edit, use the arrow next to Calendar, pick the destination and save. The first changes who is responsible for the event. The second only changes where it is filed.

A copy is also available, from Options rather than Edit, and it behaves like a copy: two independent events that stop matching the moment either one is edited.

There is a category of event that cannot be moved at all, and it is worth knowing before an inventory is built around the assumption. Google's own reference 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. These are generated rather than authored, so they belong to the account that produced them. On an account that is closing, anything in those categories has to be recreated by hand in the destination rather than carried across.

What the file route leaves behind

An import is not a clone, and the gaps are documented rather than mysterious.

What you are moving	Ownership transfer	Export and import
Guest lists and RSVPs	Kept	Not imported
Video conferencing data	Kept, policies may change	Not imported
Recurring series from a .csv file	Kept	May arrive as separate one-off events
Works across organisations	No	Yes
Events with over 200 guests	Not possible	Possible, without guests
Two copies afterwards	No	Yes

Guests and conference data are not carried by an import. For a calendar full of client meetings, that is the difference between a handover and a list of titles and times. Recurring events imported from a .csv file can land as a run of individual events rather than a series, which makes them painful to edit later.

The last row is the one that causes trouble months later. Imported events do not stay in sync between the two accounts. Change a time in one place and the other keeps the old one. If both accounts will keep running, sharing the calendar is the honest answer rather than importing it and hoping.

Recurring events deserve one more warning. When a change is saved to an event that repeats, Google Calendar asks which occurrences the change applies to, offering this event, this and following events, or all events. During a move that question arrives at the worst possible moment, because the obvious answer looks like all events and the consequence reaches back through every past occurrence. Where a handover has a date, choosing this and following events leaves the history on the old calendar and starts the new owner's record at the boundary, which is usually what an audit trail should look like anyway.

A practical order of operations

Start by listing which calendars are actually in play, and mark each one as primary or secondary. That single column decides the route.

Add two more columns while the list is open. One for the largest guest count on any event in the calendar, since anything above 200 guests will not transfer and has to be rebuilt by hand. One for whether the destination address sits inside the same organisation, since a work or school calendar cannot be handed to an outside address at all. Three columns and a short afternoon of checking will tell you exactly how much of the job is a few clicks and how much is re-inviting people, before any of it has started.

For every secondary calendar going to an account in the same organisation, use ownership transfer, and confirm acceptance rather than assuming it. For anything crossing an organisation boundary, or anything on a primary calendar, export it, import it into a named calendar rather than the default one, and expect to re-invite guests on the meetings that still matter. For accounts that are being closed, do the transfer before the account is deleted, not after.

Then decide what the destination should look like once the dust settles. A calendar that arrived by import has no guests attached, so the first recurring meeting after the move is the moment to send fresh invitations. Keeping work and personal calendars visible side by side, rather than merged into one, is usually what people want at that point, and a desktop client that can show several Google accounts at once makes that arrangement easier to live with. The Features page lists what that looks like in practice, and the Guide walks through connecting more than one account.

What to change first

Check today whether the events you care about sit on a primary or a secondary calendar, because that answer decides whether a clean transfer is even possible. If both accounts will stay open, share instead of importing. To keep both accounts on one screen while the move settles, Caltimate connects as many Google accounts as needed and lets you pick which one new events land in.