Introduction

If you have your events or tasks in iCalendar (ICS) format, you can import them into your Calendar Module in Vtiger CRM. You can also export your calendar records in Vtiger CRM into .ics format.

Import Process

Follow these steps to import the Calendar: 

1. Log in to the CRM.
2. Click the Calendar icon on the top right. 
3. Click the List View option. 
4. Click on the Import button from the top right corner.
5. In the popup, select ics file type.
6. Click on the Select from MyComputer button.
7. Choose your .ics file to import.
8. Click Import.

• Make sure that your .ics file addresses all mandatory fields in your Calendar module.
• The Activity Type is set to Meetings, and the Assigned To value is the username that performs import.

Export Process

If you ever want to transfer your Calendar (Events and Tasks) records, export them to a .ics file.

1. Log in to the CRM.
2. Click the Calendar icon.
3. Click on the List View option in the left nav bar.
4. Click on More and select the Export option.
5. Select the .ics radio button.
6. By default, the Export all data options will be selected.
   1. Note: While exporting records in .ics format, only logged-in user data will be exported. 
7. Click on Export Calendar.

Points to remember

1. All the mandatory fields have to be mapped during import.
   1. Note: Activity Type is a mandatory field.
2. A new Activity type(say, Demo meeting) can be imported. This value will be added to the Event > Activity Type picklist value.
3. If a Task record is being imported, mention the Activity type as Task; otherwise, an event record will be created with the Activity Type value specified in the CSV file.
4. Send Reminder, Repeat, and Invite User field values can neither be imported nor exported.
5. Import fails if the Visibility field is empty or contains an improper value.

Date and Time field values

1. Start Date, Due Date, Time Start, and End time are all different fields that have to be mapped individually during import.
2. On import, the Time start and End time fields remain the same as specified in the CSV file, irrespective of the time zone configured in My Preference.
3. Date field values depend on the date format configured in My Preference. For any other format found during import, the date field value will be empty.
4. If My preference date format is mm-dd-yyyy or dd-mm-yyyy, the system can auto-detect the value from the CSV file and import the values as in My Preferences.
5. You can import values like – 21.10.2010 or 21/10/2011, whereas you cannot import values like – 8 June 2011.
   1. Note: The CSV file should always contain the Time values in 24-hour format only.
6. On import, if the date field contains wrong date values like 36-45-2016, then the value will be overwritten as 01-01-1970
7. On import, if the time field contains wrong time values, like 50:89:00, then the import fails.
   1. Note: If the End Time is not mapped/empty, then import considers it as a Task, irrespective of it being a task/event.

Related To fields

• Relate an event to more than one contact record while importing by following the below-mentioned structure.​​​
  • Contacts::::Jessie Stokes,Contacts::::Daniel Avasti
• For related to the field, if no prefix is given (say in the above example, if Contacts is not specified), then the system will search for that value in the following order - Organization, Campaign, Cases, Invoice …. Services (as mentioned in the Related To block).
• If no record is found, it will create a new record in Service with that name and relate the event to it (as the service is last in the list).
• If there exists a new custom module (with no mandatory reference fields), then a record will be created for that module.