Data Import & Export

How to Import Azure DevOps Epics, Features, and Tasks from Excel or CSV

Emma Brown Oct 1, 2026 868 views

Question details

The user wants to import a hierarchical project structure containing epics, features, and tasks into Azure DevOps using a spreadsheet or CSV file.

How to Import Azure DevOps Epics, Features, and Tasks from Excel or CSV

Product: Excel / Azure DevOps
Device & OS: not provided
Scenario: Creating an Azure DevOps project hierarchy with accurate parent-child relationships in bulk.
Observed behavior: The user needs to correctly map work-item types, identifiers, and parent-child relationships in a spreadsheet to successfully import them into the system.

Before you start

Ensure you know the exact Work Item Types customized in your Azure DevOps project, as spelling mismatches in your Excel or CSV file will cause the import to fail.

Solution 1Recommended

Prepare and Import Work Items via CSV File

Using a CSV file is a highly reliable method to import hierarchical work items like epics, features, and tasks directly into the Azure DevOps web portal.

This method does not require any specialized add-ins and works seamlessly regardless of the spreadsheet software you use to prepare the data. You must carefully map parent-child links using ID columns.

Set Up CSV Column Headers

Open your spreadsheet software and create headers for 'ID', 'Work Item Type', 'Title 1' (for Epics), 'Title 2' (for Features), and 'Title 3' (for Tasks).

Enter Hierarchical Data

Fill in the rows. Leave the 'ID' column blank for new items. Stagger your titles across Title 1, Title 2, and Title 3 to implicitly define the parent-child relationships.

Save as CSV

Go to 'File' > 'Save As', and select 'CSV (Comma delimited)' as the file format to save your worksheet.

Import into Azure DevOps

Log in to your Azure DevOps web portal, navigate to 'Boards' > 'Work Items', click on 'Import Work Items', and upload your prepared CSV file to publish the hierarchy.

Prepare and Import Work Items via CSV File

Mapping Tip: You can also use 'Parent ID' as a column header to explicitly link tasks to features and features to epics if you prefer flat title columns.

Solution 2

Use the Azure DevOps Office Integration Excel Add-in

If you are using Microsoft Excel on Windows, you can use the official Azure DevOps add-in to build and publish tree lists.

Easily Prepare Azure DevOps CSV Imports with WPS Spreadsheet

WPS Office provides a fast, lightweight, and highly compatible spreadsheet tool that is perfect for formatting, structuring, and exporting CSV files for Azure DevOps imports.

1. Open a Blank Spreadsheet: Launch WPS Office, select 'Spreadsheet', and click 'Blank' to start a new file.
2. Design the Hierarchy Columns: Type 'Work Item Type', 'Title 1', 'Title 2', and 'Title 3' into the first row to set up your Epic, Feature, and Task structure.
3. Populate Your Project Data: Enter your Azure DevOps data into the respective columns, ensuring child items correctly fall under their parent items in the subsequent rows.
4. Export to CSV: Click 'Menu' in the top-left corner, go to 'Save As', choose 'CSV (Comma delimited) (*.csv)' from the dropdown, and save the file.
5. Upload to DevOps: Take this neatly formatted CSV file and import it directly into your Azure DevOps Boards portal.

Perfect compatibility with Microsoft Excel (.xlsx) formatsSeamlessly export clean, error-free CSV files for Azure DevOps importsLightweight application that handles large datasets smoothlyFree to use with a clean, familiar, and intuitive user interface

microsoft office alternative - wps office

Frequently Asked Questions

Why are my parent-child relationships not linking during the Azure DevOps CSV import?

This usually happens because the hierarchy columns are misaligned. Ensure you are either staggering your titles correctly across 'Title 1', 'Title 2', and 'Title 3' columns, or explicitly mapping relationships using a 'Parent ID' column.

Can I update existing Azure DevOps work items using a CSV file?

Yes. To update existing work items, include the 'ID' column in your CSV and populate it with the current Azure DevOps work item IDs. Any changes made in the CSV will overwrite the existing data upon import.

Where can I find sample data structures for complex Azure DevOps imports?

For detailed import guidance, advanced mappings, or troubleshooting complex hierarchies, you can find sample structures and ask specific questions in the official Azure DevOps Tech Community.

Excel & Data Problems