You can transfer your events from a different calendar application or Google Account to Google Calendar.
When you import an event, guests and conference data for that event are not imported.
Step 1: Export eventsExport your events as a file that you can import into Google. Choose one of these options:
Export from another calendar applicationYou can export your events from most calendar applications, such Outlook Calendar or Apple Calendar.
For more help, check your calendar application's help center or try to use the words “export calendar” in your search.
Your file is stored on your computer where your downloads are usually saved or in the place you chose when you exported.
Export from a different Google AccountIf you have more than one Google Account, you can export your calendars from one account and import them into another.
Tip: Imported events don't stay in sync between your 2 accounts. If you want your calendars to sync, share your calendar with the other account.
Step 2: Import events into Google CalendarAfter you export your events, you can import them into Google Calendar. You can import with ICS and CSV files on a computer.
If you have a .zip file, find it on your computer and open it. You'll find .ics files for each of your calendars. Take the individual files out of the .zip file, and import each .ics file individually.
If you import repeat events from a .csv file, they might not show up that way. They'll be on your calendar as a series of one-time events.
Advanced: Create or edit .csv or iCal files before you import Create or edit a .csv fileYou can import .csv (comma separated values) files into Google Calendar. If you get an error when you import a .csv file, you might be able to fix the formatting.
Open a .csv file or create one with a spreadsheet editor like Google Sheets.
The first row of your new spreadsheet includes headers like “Subject” and “Start Date.” To import into Google Calendar, the headers must be in English. For the correct headers you need to import into Calendar, go to the list below.
Each row below the header row represents an event. For example:
Subject
Start date
Start time
Final exam
05/30/2020
10:00 AM
When you're done, save the file as a .csv file. Then, to import the file into Google Calendar, follow the steps in “Import events into Google Calendar.”
Format headers & events in .csv filesOnly the first 2 headers in this list are required. The rest are optional.
Important: The headers must be in English as shown in this article. If any event details have commas (like the location example given), you can include them with quotation marks around the text.
Subject
Final exam
Start Date
05/30/2020
Start Time
10:00 AM
End Date
05/30/2020
End Time
1:00 PM
All Day Event
True
. False
.False
Description
"50 multiple choice questions and two essay questions"
Location
"Columbia, Schermerhorn 614"
Private
True
.False
.True
These examples would create the following event:
iCalendar files are a standard calendar format used to transfer calendar data. If you get an error when you import an iCalendar file (.ics), you might be able to fix the formatting.
The first line in an iCalendar file must always be the header BEGIN:VCALENDAR
. Other header information, such as VERSION:2.0
and "PRODID:<
{enter ID information here}>"
, must follow this header. The last line of the file must be the footer END:VCALENDAR
. Between these lines, enter all the events in the calendar. Each event must be between BEGIN:VEVENT
and END:VEVENT
lines.
If you must manually edit an iCalendar file, make sure that each file contains the header and footer. If you're not sure where your header ends, copy and paste the text until one line above BEGIN:VEVENT
. This location is where your header ends and your event data starts.
Here's what an iCalendar file looks like. An iCalendar file can also have more information, but these are the required parts.
BEGIN:VCALENDAR
VERSION:2.0
PRODID:<
{enter ID information here} >
{Other header information}
BEGIN:VEVENT
{Event details}
END:VEVENT
BEGIN:VEVENT
{Event details}
END:VEVENT
END:VCALENDAR
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.3