MS Project sync
Synchronize WBS codes, durations, and milestones between MS Project and 4D.io via direct CSV or Project Online integration.
Teams can export project plans from MS Project as CSV or connect directly to Project Online to pull schedule data into 4D.io. Upon import, WBS codes are preserved and used as the primary reference for aligning tasks with model elements. This ensures traceability from high-level scheduling hierarchies down to individual floors or systems in the model.
Updates flow both ways: if you adjust a duration or add a milestone in 4D.io—such as marking concrete pour completion—the change can be pushed back to MS Project after validation. Conflicts, like duplicated WBS codes or inconsistent dates, are flagged clearly before syncing. This avoids manual corrections and keeps both planning and simulation tools authoritative in their respective workflows.
The sync includes critical path indicators and early/late start dates where supported by the source format. Field mappings are customizable, letting you choose which outline levels or task types (e.g., milestones vs. work packages) should drive model timelines. This makes the tool adaptable to different organizational standards, from lean scheduling to traditional Gantt-heavy planning.
