Support / Import, export & print
Import a Schedule from Excel or CSV
If your schedule lives in a spreadsheet, you can import it as a full CPM schedule with logic. For a handful of rows, pasting from Excel is quicker.
Excel workbook (.xlsx)
The workbook needs a sheet named Tasks. Optional sheets named Dependencies, Calendars, and Baselines add logic, calendars, and baseline dates.
The Tasks sheet's first row holds column names. Two are required:
| Column | Required | Example |
|---|---|---|
wbs_code | Yes | 1.2.3 |
name | Yes | Pour L2 slab |
parent_wbs | No | 1.2 |
planned_start | No | 2026-11-02 |
duration_days | No | 5 |
constraint_type | No | SNET |
The Dependencies sheet has one row per link, with predecessor_wbs, successor_wbs, the relationship type, and lag.
The easiest way to get the exact layout is to export any schedule with Export ▾ → Excel and use that workbook as your template. It has every sheet and column the importer reads.
CSV
A .csv file uses the same column names as the Tasks sheet. CSV has one sheet, so it can't carry dependencies or calendars. Add logic after importing.
Import
- Create a new project or open the one you want to fill.
- File ▾ → Import schedule and choose the
.xlsxor.csvfile. - Read the Import trust report for anything skipped.
Importing replaces the project's entire schedule.
Tips
- Use
YYYY-MM-DDdates. - Every task needs a unique
wbs_code. - After importing, run Analysis ▾ → Validation to find activities without logic.