Migrate from SMART Project Control to monday Work Management

SMART Project Control Programs act as top-level grouping containers for related Projects. monday.com has no native Program object; we map Programs to monday.com Workspaces or, where multiple Workspaces are impractical, to a top-level Board whose Groups represent individual Projects. If the customer uses Portfolio-level rollup reporting, we flag this as a monday.com Dashboard rebuild requiring separate Board-level widgets rather than native hierarchy.

Projects migrate as monday.com Boards. Project name, start date, finish date, status, and calendar assign to the Board name and top-level Group header fields or custom date columns. Project-level custom properties map to typed monday.com columns. We resolve the Board-level status column mapping (Active/On Hold/Complete) during scoping. Projects must import before their child Activities so that board structure is established before item creation.

monday.com has no native baseline concept. We store the latest approved Baseline as a static JSON reference or date-tuple in a Custom Column on each Board (e.g., Baseline Start Date, Baseline Finish Date, Baseline Name). Secondary Baselines are documented in a Board-level Notes section. Post-import, the customer can manually compare current Activity dates against baseline reference columns in monday.com dashboards. We flag that monday.com does not compute schedule variance natively.

Activities are the core migration unit, mapping directly to monday.com Items within a Board Group. Activity name becomes Item name, start and finish dates map to Date columns, duration maps to a Numbers column, and status maps to a Status column. Predecessor-successor relationships (FS, SS, FF, SF) convert to monday.com dependency links between Items. We build the dependency graph from the source relationship export and recreate it using monday.com's native Dependency column.

WBS Elements define hierarchical accountability in SMART Project Control. Where monday.com Groups correspond to WBS level-1 or level-2, we map WBS Elements to Groups. For deeper WBS levels, we create Subgroup Items with a WBS Code custom column to preserve the hierarchical path. The customer selects the WBS mapping strategy during scoping based on board nesting preference.

Named Resources (labor, material, equipment) migrate as monday.com People column assignments on Items. Resource name maps to the Person; resource role and unit-of-measure map to a Text or dropdown column. monday.com does not support a resource pool with rates, capacity curves, or unit-of-measure; we preserve role name and rate as custom fields but note that capacity-based resource leveling does not migrate. For projects with named-resource assignment history, we populate People assignments on the matching Activities.

CBS cost levels and cost accounts map to monday.com Numbers columns or custom field types. Time-distributed cost data (period-by-period spending) converts to a series of period-bucket columns (e.g., Jan 2026 Cost, Feb 2026 Cost) on each Activity Item. Cost account codes migrate as a Text column. We flag that S-curve cumulative cost histograms require reconstruction in monday.com Dashboard widgets using the period-bucket data rather than a native chart type.

Custom activity, project, and resource fields export from SMART Project Control with their current values and types. We map to monday.com custom column types by type: date pickers, numbers, text, dropdown, checkbox, and dependency. Picklist values require explicit value mapping during scoping to ensure exact matches on the monday.com side. We flag any CBS or earned-value-derived custom fields that reference SMART Project Control's calculation engine and must be rebuilt as monday.com formula columns.

Cumulative S-curves export as time-phased data rows per Project. On import, we load these as data table rows in a dedicated monday.com Board (one board per Project for cost curves). Post-migration, the customer rebuilds the visualization in monday.com Dashboards using line or area widgets pointing at this data board. We deliver a written specification for the dashboard rebuild including widget type, data source board, and axis mapping. This is documented, not migrated.

Critical path and float values in SMART Project Control are derived from its native CPM engine. monday.com calculates dependency chains visually but does not compute critical path or float natively. We preserve the computed critical path as a checkbox or tag column (Critical = Yes/No) from the source export so that the flag is visible on each Activity Item. The actual CPM recalculation happens in monday.com's own dependency engine post-import, which may produce different critical path results. We document this variance explicitly for the customer's schedule team.

Portfolio-level rollup reporting across multiple Projects — earned value summaries, cost rollups, schedule variance by Program — does not have a monday.com equivalent. We extract the portfolio rollup data as a structured reference export. The customer rebuilds cross-board rollup dashboards using monday.com's Dashboard widgets (count, sum, formula) pulling from the migrated Board data. We deliver a written dashboard specification with recommended widget layout, data source boards, and aggregation logic.

SMART Project Control's predictive bottleneck alerting and forecasting engine have no monday.com equivalent. We export the current alert rules and forecast thresholds as a written specification document. The customer rebuilds these as monday.com Automations (e.g., when a date column is within 3 days of today, notify assigned person) or as AI Work Management alerts if they are on monday.com's Enterprise AI tier. This is documented, not migrated.