Document toolboxDocument toolbox

Import Roadmap Data from Other Platforms

Owned by Jaramy Conners
Last updated: Oct 23, 2024
5 min read

Import from Asana to Strategic Roadmaps

Export from Asana to CSV

In Asana, users have the option to export a CSV of their data by project or by tasks assigned to a user.

CSV Changes for Strategic Roadmaps

When opening the CSV it will contain the data from your Asana project. Please note you will have to format it differently in order to make it compatible with Strategic Roadmaps. 

Mandatory Changes

The following changes must be made to the CSV file:

  1. That the first column is called "Item". Must contain the title of the feature or project task.

  2. That there are separate columns for both start and end date.

  3. There there are columns called "bucket" and description. Neither need to be filled out.

For more information on formatting including examples, please download a free template from our templates page.

Import to Strategic Roadmaps

Once changes have been made the CSV can be imported to Strategic Roadmaps.

See the importing tutorial for further steps.

Import from Excel to Strategic Roadmaps

In this guide, we'll walk through the 5 easy steps to follow when preparing an Excel roadmap for import into Strategic Roadmaps.

Step 1 - Identifying Data Pivots

The first step in the transition is identifying the data pivots in the Excel roadmap:

  1. The tasks being tracked

  2. The owner of the task

  3. The months that the task is being completed in

  4. The colour of the task to indicate status

Step 2 - Formatting the Data

The next step is to format the data in the spreadsheet by putting the pivot data identified in the previous step into separate columns for import into Strategic Roadmaps columns.

The roadmap spreadsheet should now have:

  • an Owner column identifying owner of each item (e.g., Jerry, Elaine)

  • a Status column identifying the status of each item (e.g., In progress, Completed).

Step 3 - Adding Real Dates

The next step before the import is adding real start and end dates for each date range represented in the spreadsheet using colored cells. The added dates should be formatted as Numbers, and the format should be consistent across all items.

The roadmap spreadsheet should now have:

  • A Start Date and an End Date column containing the start and end dates of each date range represented in the spreadsheet using colored cells

  • Dates in the columns formatted as Numbers using a consistent format (e.g, 01-Dec-16)

NOTE: For the import to Strategic Roadmaps to be successful, each item in the Excel roadmap must have a Start and End Date. Even if you don't know what an item's dates are, add a best-guess date. You can always change this once the date is in Strategic Roadmaps.

Step 4 - Removing Extra Cells

Remove the Month Header Row

Now that you've added real dates, you can remove the month header row at the top of the spreadsheet.  

Remove Owner Names

You should also remove the owner names that are above the listed items, delete any empty rows, and add Item as the row header (in the same row as Owner, Status, Start Date, and End Date).

The roadmap spreadsheet should now have:

  • an Item column for the items in the roadmap

  • Owner and Status columns with appropriate values

  • Start Date and End Date columns, containing the start and end dates of each item, formatted as Numbers, and using a consistent format. 

  • No blank rows or cells

Step 5 - Importing to Strategic Roadmaps

Finally, save the Excel file as a CSV and import it into Strategic Roadmaps following the instructions in Import items from CSV.

Import from Pivotal Tracker to Strategic Roadmaps

Exporting from Pivotal Tracker to CSV

The first step in the import is exporting data in a Pivotal Tracker roadmap to a CSV.

  1. Go to the Settings tab and select Export CSV.

  2. Select the stories and epics you want to export, then click the Export button.

  3. Save the CSV file and open it in a spreadsheet application (for example, Excel).

For more details, go to Pivotal Tracker's exporting walkthrough.

Making Changes to the CSV

There are some mandatory changes you must make to the CSV before the import, as well as some optional and advanced changes.

Mandatory Changes

The following changes must be made to the CSV file:

  1. Title -> Item

  2. Iteration Start -> Start Date

  3. Iteration End -> End Date

Optional Changes

The following changes can also be made but are not mandatory:

  1. Delete Created at

  2. Delete Accepted at

  3. Delete Deadline

  4. Delete URL

  5. Delete Owned By

  6. Delete Comment

Advanced Changes

If Strategic Roadmaps will be regularly updated from Pivotal Tracker, we recommend renaming the ID field in the CSV to ExternalID. Strategic Roadmaps uses this field to match existing items so they're updated instead of overwritten.

Importing the CSV into Strategic Roadmaps

Once changes have been made the CSV, you can start the import to Strategic Roadmaps. For details, see our article on importing data from CSV into Strategic Roadmaps.

Import from Rally to Strategic Roadmaps

Exporting from Rally to CSV

The first step in the Rally import is exporting data in a Rally view, such as the User Stories Summary, to a CSV.

  1. In the Actions menu select Export to CSV.

  2. Save the CSV file and open it in a spreadsheet application (for example, Excel).

For more details, go to Rally's  exporting walkthrough.

Making Changes to the CSV

There are some mandatory changes you must make to the CSV before the import, as well as some optional and advanced changes.

Mandatory Changes

The following changes must be made to the CSV file:

  1. Name -> Item

Optional Changes

The following changes can also be made if desired but are not mandatory:

  1. Delete Plan Estimate

  2. Delete Task Estimate Total

  3. Delete To Do

  4. Delete Parent ID

Advanced Changes

If Strategic Roadmaps will be regularly updated from Rally, we recommend renaming the ID field in the CSV to ExternalID. Strategic Roadmaps uses this field to match existing items so they're updated instead of overwritten.

Importing the CSV into Strategic Roadmaps

Once changes have been made the CSV, you can start the import to Strategic Roadmaps. For details, see our article on importing data from CSV into Strategic Roadmaps.

Import from Trello to Strategic Roadmaps

Exporting from Trello to CSV

The first step in the import is exporting data in a Trello board to a CSV file.

  1. On the Trello menu, click Print and Export, then click Export CSV.

  2. Save the CSV file and open it in a spreadsheet application (for example, Excel).

For more details, go to Trello's exporting walkthrough.

Making Changes to the CSV

There are some mandatory changes you must make to the CSV before the import, as well as some optional and advanced changes.

Mandatory Changes

The following changes must be made to the CSV file:

  1. Card Name -> Item

  2. Card Description -> Description

  3. Due Date -> End Date

Optional Changes

The following changes can also be made if desired but are not mandatory:

  1. Delete CardID

  2. Delete ListID

  3. Delete Board ID

  4. Delete Last Activity Date

Advanced Changes

If Strategic Roadmaps will be regularly updated from Trello, we recommend renaming the CardID field in the CSV to ExternalID. Strategic Roadmaps uses this field to match existing items so they're updated instead of overwritten.

Importing the CSV into Strategic Roadmaps

Once changes have been made the CSV, you can start the import to Strategic Roadmaps. For details, see our article on importing data from CSV into Strategic Roadmaps.

Import from VersionOne to Strategic Roadmaps

Exporting from Version One to CSV

The first step in the import is exporting the data in the project to a CSV file. 

  1. In the project's Reports menu, click Project Burndown.

  2. Open the menu in the upper-right corner of the report and click Download CSV.

Making changes to the CSV file

The following changes must be made to the CSV file:

  • The first column in the CSV (Item) must contain the title of the feature or project task.

  • The file must contain separate columns for Start Date and End Date.

  • The file must contain a Bucket field and a Description field. Both fields can be left blank.

Importing the CSV into Strategic Roadmaps

Once changes have been made the CSV, you can start the import to Strategic Roadmaps. For details, see our article on importing data from CSV into Strategic Roadmaps.