Teamup supports the import of events from other calendar applications, spreadsheets, databases, and text files. Currently, supported import formats are iCalendar files (*.ics files) and CSV files (text files with comma-separated values).
This article discusses how to import data into your calendar, the iCalendar data format, and the CSV data format.
Note that the import feature is meant for a one-time transfer of data from a third-party application to Teamup. It can also be used to migrate calendar data from one Teamup calendar to another Teamup calendar. It does not offer ongoing synchronization. If you need an ongoing synchronization between Teamup and another calendar source, please read about iCalendar feeds.
How to import calendar data
To use the import feature, go to Settings > Import Events. The import feature is only available to calendar administrators.
Supported import formats
Teamup supports two import formats: iCalendar files (*.ics files) and CSV files (*.csv files).
- iCalendar files are based on the universally supported iCalendar format created by the Internet Engineering Task Force. Virtually all calendar products support the import and export of calendar data in the iCalendar format, including Microsoft Outlook, Google Calendar, Apple Calendar, and Teamup. The iCalendar format is well suited to migrate calendar data from a third-party calendar product to Teamup.
- The CSV format represents data as a comma-separated list of values. CSV stands for Comma-Separated Values. It is a text-based format with the first row defining all the field names and the following rows containing the data records. See the example below. The CSV format is widely supported by spreadsheet tools and database tools. It is commonly used to exchange data between computer systems and is more generic than the iCalendar format. For example, the CSV format works well to prepare calendar data in a spreadsheet tool like Excel and then import it into Teamup.
Which format to choose?
Each format has advantages and limitations. It is important to choose the right format if you need to import data into Teamup.
Choose the CSV format:
- If you need to migrate calendar data from one Teamup calendar to another Teamup calendar we highly recommend using the CSV format. It supports the migration of data without any loss of information because it supports Teamup-specific features like multiple sub-calendars per event, custom fields, and the migration of an entire calendar in one file.
- For the backup of Teamup calendar data.
- For the import of calendar data from ERP and CRM systems. Such systems often don’t support the iCalendar format and therefore the CSV format is the only option.
- If you need to compile or edit calendar data in a spreadsheet tool like Excel.
Choose the iCalendar format:
- If you need to import calendar data from third-party calendar products like Google Calendar, Microsoft Outlook, Apple Calendar, or similar.
Supported sources for data
The import tool currently supports two sources for data: Files stored on your computer and files accessible from a link (URL). The second option can be convenient as many calendaring applications support the export of data through iCalendar feeds, which are links (URLs). If a feed is available for the application you are importing from, simply copy and paste this feed URL into the import tool.
The iCalendar data format
If you plan to migrate calendar data from a third-party calendar product, we recommend that you check if it supports the iCalendar format. If you need to import calendar data from another Teamup Calendar, we highly recommend using the CSV format.
Step 1: Export data from the source calendar
Export the data from the source calendar in the iCalendar format and store it as a file with the .ics extension.
Here are instructions on how to export data for a few widely used products:
A few important notes when exporting data from another Teamup calendar:
- When exporting in the iCalendar format, each sub-calendar will be exported to its own file. All files are put into a ZIP archive file when downloading.
- Note that .ics files do not keep the custom field values in separate fields. Instead, custom field values are appended to the text in the Description field.
Step 2: Import data into your Teamup calendar
Import the exported file(s) into the destination calendar:
- Create a new Teamup calendar if you haven’t done so yet.
- Go to Settings > Import. This requires administration permission.
- Import each sub-calendar separately from the respective ics file and name it accordingly. Please note that each import will create a new sub-calendar. It is not possible to import *.ics files into existing sub-calendars.
The CSV data format
A CSV file (comma-separated values) stores tabular data in plain text. By default, the delimiter between fields is the comma character. Also supported delimiters are the semicolon (“;”) and the pipe character (“|”). The import tool automatically detects the used delimiter.
If you plan to migrate calendar data from another Teamup calendar, see here how to export the data.
The first line of a CSV file is a list of field names, separated by the delimiter character. Subsequent lines are data records; in our case, these represent calendar events.
Example 1: Simple CSV file
Subject,Start Date,Start Time,End Date,End Time,All Day Event,Location,Who,Description Project Meeting,02/12/2016,2:00pm,02/12/2016,4:00pm,False,Conf. Room A,"John, Mark", Linda in Paris,02/15/2016,,02/15/2016,,True,Paris,Linda, Team Meeting,02/15/2016,9:00am,02/15/2016,11:00am,False,Conf. Room B,"Linda, John",
Supported fields in CSV format
The following table defines the supported field names and their format.
|Subject||No||Event title. Up to 255 characters in length.|
|Start Date||Yes||Start date of event. The required date format depends on the configuration of the date format for the calendar (see the Date & Time configuration of your calendar). Supported formats are “12/31/2016”, “31/12/2016” and “31.12.2016.”|
|Start Time||No||Start time of event. 12 hour and 24 hour date formats are supported, for example “2:30pm” and “14:30.”|
|End Date||No||End date of event. For supported formats see above.|
|End Time||No||End time of event. For supported formats see above.|
|All Day Event||No||The All Day Event flag defines if an event is an all-day event or an hourly event. Supported values are “True” and “False.” If no value or an unsupported value is specified, “False” is used by default.|
|Location||No||Location of event. Up to 255 characters in length.|
|Who||No||Participants of event. Up to 255 characters in length.|
|RRule||No||Recurrence rule according to RFC 5545 iCalendar. An example is “FREQ=WEEKLY;COUNT=3” for an event that repeats weekly for three times. Please note that Teamup supports only a subset of the recurrence rules as defined by the specification. To learn about supported rules, we recommend creating some repeating test events using Teamup in the web browser. Then, export the test events in CSV format to see how the recurrence rules are represented.|
A list of datetime values that represent exceptions to the recurrence rules specified above. Example: “7/13/2023 00:00:00,7/27/2023 00:00:00”.
Name of sub-calendar into which the event is to be imported. Up to 100 characters in length.
Note that events can be imported into an existing calendar. If no sub-calendar exists with the specified name, a new sub-calendar will be created.
If an event is assigned to multiple sub-calendars, then this field must contain a list of all sub-calendars separated by the pipe character (“|”).
Conf. Room Newton|Auditorium
|Description||No||Description of event. Up to 16,000 characters in length. Simple formatting of the text is supported following the markdown approach. See Common Mark specification for a 2-minute introduction to markdown formatting.|
|<Custom Field Name>||No|| Teamup supports custom event fields. Custom event fields are user defined fields added to calendar events. Currently, three types of custom event fields are supported: Single line text, single choice, multiple choice.
The import of values for custom fields is supported and works identically to the standard event fields. See example 3 below.
Please proceed in the following way:
Example 2: File with multi-line event description
"Subject","Start Date","Start Time","End Date","End Time","All Day Event","Location","Who","Description" "Project Meeting","02/12/2016","2:00pm","02/12/2016","4:00pm","False","Conf. Room A","John, Mark","" Linda in Paris,02/15/2016,,02/15/2016,,True,Paris,Linda,In case of emergencies I am reachable by email. "Team Meeting","02/15/2016","9:00am","02/15/2016","11:00am","False","Conf. Room B","Linda, John","## Meeting Agenda * Project review * Next steps * Next meeting " "","02/12/2016","","02/12/2016","","True","","","Minimum record values"
Example 3: File with custom fields
This example shows the import of custom field Project Type, which is a multiple-choice field. Three choice values are imported for this field:
"Subject","Start Date","Start Time","End Date","End Time","All Day Event","Project Type" "Project Meeting","02/12/2016","2:00pm","02/12/2016","4:00pm","False","Research, Internal, Not Billable"
Important notes about the CSV import
A few important details to know about the CSV import:
- The destination sub-calendar for imported events can be specified either in the CSV file itself or in the import tool for all imported events. CSV files support an optional field “Calendar Name” that can be used to specify the sub-calendar into which an event is imported. If the field “Calendar Name” is not present or not set, then the sub-calendar into which events are imported must be specified in the import tool.
- A CSV file can contain events for multiple different sub-calendars. This makes it possible to export an entire calendar with multiple sub-calendars into one file and use that file to restore the data in another calendar.
- If a sub-calendar specified as the import target does not exist, it is created.
- If a sub-calendar for an event is specified both inside the CSV file and in the import tool, the sub-calendar specified in the CSV file has priority.
- The order of fields does not matter. However, it is important that all lines, including the header line, use the same field order.
- Field values can span multiple lines.
- Field values must be wrapped in quote characters (“…”) if the field values contain the field delimiter (comma, semicolon, or pipe character) or span multiple lines. Otherwise, quotes are optional.
- If a field value contains the quote character, it must be escaped by doubling it, e.g. a field value of
"The importance of the "" character"
- will be imported as
The importance of the " character
- When importing data into an existing sub-calendar, existing events will not be updated. Instead, new events will be created. Please note that the import tool supports an option “CLEAR DATA BEFORE IMPORT”.