Skip to main content

​
Importing Projects — Overview

GlidePath supports importing project data from Excel, CSV, MS Project, and Primavera P6. This guide gives an overview of the import workflow.

​
Feature Spec Reference

Module 1.7 — Import from Excel/CSV
Module 1.9 — Import from MS Project XML
Module 1.10 — Import from P6 XER

​
Supported Formats

​
Import Workflow

  1. Open Import Dialog
    • From project view, click Import or File → Import
    • Select import format
  2. Upload File
    • Drag and drop or browse to select file
    • File is validated for format compatibility
  3. Map Columns
    • Match source columns to GlidePath fields (Task Name, Duration, Start Date, etc.)
    • Preview first 5–10 rows
    • Adjust mapping if needed
  4. Review and Import
    • See summary of tasks to import
    • Check for warnings or errors
    • Click Import to create tasks in project
  5. Review Results
    • Import results dialog shows tasks added, warnings, errors
    • Gantt chart updates with new tasks
    • Review and edit tasks as needed

​
Common Import Scenarios

​
Scenario 1: Start from Excel Template

  1. Download the GlidePath Import Template (Excel file)
  2. Fill in your task data using the template columns
  3. Save and import via Import dialog
  4. All tasks created with correct field mapping

​
Scenario 2: Migrate from MS Project

  1. Export your project from MS Project as .xml format
  2. Use Import dialog → Select MS Project XML
  3. Field mapping is automatic
  4. Dependencies, constraints, and resources preserved

​
Scenario 3: Import from Primavera P6

  1. Export your project from P6 as .xer (XER format)
  2. Use Import dialog → Select Primavera P6
  3. Activity IDs, WBS, and constraints preserved
  4. Calendar and resource assignments imported

​
Import Tips

  • Validate dates — Ensure date format matches your locale (MM/DD/YYYY vs. DD/MM/YYYY)
  • Check WBS — GlidePath will auto-generate WBS if not provided
  • Test small first — Import a subset of tasks first to verify mapping
  • Review warnings — Import results may show non-critical warnings—review these
  • Link dependencies — If dependencies aren’t in import file, add them after import

​
Next Steps