How to Import .CSV Files to Your Timeline


This article explains how to import a .CSV file into a Propared Timeline.

1. Create the .CSV File

Export your data to the .CSV file format using a spreadsheet application, such as Microsoft Excel or Apple Numbers.

Notes: Propared will automap any column header names that exactly match the field name in Propared. Otherwise, column information can be mapped manually to the Propared field of your choice. However, it is recommended that you format the column headers in your file to match Propared's fields as best as possible.

The field names that are standard to the Propared application are: Start Date, Start Time, End Date, End Time, Name, Location, Assigned Team, Categories, Departments, Notes

Download a .CSV Task Import template!

2. Navigate to the Timeline and click the "Task Import" Button

3. Choose the .CSV file you just Created

4. Map Your Fields

Field Mapping Guide

After selecting a file, review the Field Mappings (left side of the window). Click the dropdown arrow to select which Task field should be matched to each column from your CSV file.

Click the Ignore first row checkbox to avoid importing the column headers as a Task record. You can also use the next/previous arrows to scroll through each row/record, and see a preview (right side of the window) of how they will appear as Tasks in your Timeline after import.

5. Task Import Notes

A few other things to remember when importing Tasks to your Timeline from a .CSV file:

Required fields

  • At a minimum, we require the Task Name field.
  • All other fields are optional.

Listing multiple values in a single field

  • If you have multiple values within a single field, they must be separated by either a comma (,) or a semi-colon (;).

Notes field

  • You can map more than one column to the Notes field.
  • The Notes field is searchable, so it's a good place to map any extra data you want to import, but for which we don't have a dedicated field.

Team Member & Location matching

  • For the Team and Location fields, we'll search your existing Contacts, and attempt to match them by their name.
  • PLEASE NOTE:  The Contact Name must match verbatim, but it is NOT case sensitive (i.e., we ignore the letter case).
  • For any Contacts we cannot match, we'll save that value into the Notes field.

Date & Time format (notation)

  • We use your personal date and time format preferences (found in the Settings screen) to determine if dates should be validated using Month-Day-Year versus Day-Month-Year.
  • If we encounter any unexpected issues for the date or time (e.g., non-chronological datetime or unsupported format/notation), we'll import whatever values we can, and tag the Task with an import error.
  • See below for a detailed list of supported datetime formats/notations.

Import errors

  • For Tasks with date or time info we had trouble importing, we'll automatically add the Category Tag IMPORT ERROR.
  • After importing, you can filter your timeline by the Category Tag IMPORT ERROR, and review each task to see what didn't map correctly.

6. Supported Datetime formats (notation)

Date:  March 5 (current year is assumed) 

  • 3/5
  • 3-5
  • and any combination with or without preceding zeros

Date:  March 5, 2014

  • 3/5/14
  • 3/5/2014
  • 3-5-14
  • 3-5-2014
  • and any combination with or without preceding zeros

Time:  6:30 AM

  • 6:30am
  • 6:30 am
  • 630a
  • 630 a
  • 630
  • 6:30
  • and any combination with or without preceding zeros
  • NOTE:  a/am is case insensitive

Time:  6:30 PM

  • 6:30pm
  • 6:30 pm
  • 630p
  • 630 p
  • 1830
  • 630 pm
  • and any combination with or without preceding zeros
  • NOTE:  p/pm is case insensitive
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.