Migrate your SMART Project Control data

Programs act as top-level grouping containers in many project controls schemas. We preserve the Program-to-Project parent-child relationships by mapping them to equivalent portfolio or program objects in the destination, or by linking Projects directly and noting the grouping in a metadata layer.

Projects are the primary migration unit. Core project-level attributes — name, start and finish dates, status, calendar — migrate 1:1. We flag any project-level custom properties for field-level mapping before writing to the destination.

Baselines store the approved schedule snapshot and are referenced by earned value and variance calculations. We migrate the latest approved baseline as a static schedule copy. Secondary baselines are migrated as historical records with a note on their sequencing relationship in the target system.

Activities are the core scheduling unit with dates, duration, logic relationships, and calendars. Standard activity fields migrate cleanly. We rebuild predecessor and successor relationships using the destination's native linking syntax.

Work Breakdown Structure elements define hierarchical accountability. Where the destination uses a flat activity structure or a separate WBS object, we map accordingly and flag any element-level custom fields for explicit mapping.

Labor, material, and equipment Resources — including roles, rates, and unit-of-measure — migrate as named resource definitions. We verify resource pool deduping across the export to avoid duplicate rate entries on the destination side.

Cost CBS levels and cost accounts are mapped to the destination's cost coding schema. Time-distributed cost data is converted to activity-level cost assignments or period bucket records depending on destination support.

Custom activity, project, and resource fields are exported with their current values and types. We require explicit mapping instructions from the customer to ensure picklist values, date formats, and numeric precision are handled correctly at the destination.

Cumulative S-curves are exported as time-phased data rows per project. On import, we convert them to the destination's native reporting format — either as data table rows or as computed metrics — and flag any loss of granularity.

Critical path and float values are preserved when the destination calculates them natively. If the target platform derives critical path from its own scheduling engine post-import, we document the expected float behavior so the customer can validate after cutover.