Migrate from Project Central to monday Work Management

Project Central Projects map to monday.com Boards. The Project name becomes the Board name. Project Central's project-level description or summary field maps to the Board description text. We create one Board per Project during migration. Board privacy settings default to workspace visibility; if the source Project had restricted member access, we configure Board-level privacy during migration.

Project Central Tasks map to monday.com Items. Task name becomes Item title. Task description maps to the Item's Text column if populated. Task due date maps to a Date column. Task assignment (Owner) maps to a Person column with the monday.com Team Member resolved by email match. Parent-child task relationships in Project Central (subtasks) map to monday.com Subitems nested under the parent Item.

Project Central's configurable Status workflows (Agile or Waterfall stages) map to monday.com Status columns. We extract the distinct status values from the source, create a corresponding Status column with matching labels, and map Task status values during migration. If the source uses custom status labels (e.g., Not Started, In Progress, Under Review, Done), we replicate those labels in monday.com rather than renaming to default values.

Project Central custom fields map to monday.com column types: Text fields to Text columns, numeric fields to Numbers columns, date fields to Date columns, dropdown-style fields to Dropdown columns, and boolean fields to Checkbox columns. We extract the full list of custom fields during discovery and configure the matching column types before migration begins. Custom field validation rules (required, format) map to monday.com column prerequisites where the platform supports them.

Project Central Tags map to monday.com Labels (applied directly to Items) or to a Multi-Select column depending on how the customer uses tags. Tags used for project-wide categorization map to Labels; tags used as task-level attributes (e.g., priority, type, department) map to Multi-Select columns. The customer chooses the strategy during scoping. We preserve the full tag taxonomy and apply all tags to matching Items during migration.

Project Central's configurable Views for Agile methodology map to monday.com Board Views: Board view (Kanban) for sprint-style task boards, Timeline view for Gantt-style dependency visualization, and Calendar view for date-based task visibility. We configure the equivalent monday.com view during migration and map Tasks to the correct view grouping (typically by Status column for Kanban, by Assignee for team-based views).

Project Central's Waterfall-style views (sequential task dependencies, milestone tracking) map to monday.com's Timeline view with start and end date columns. If the source uses dependency fields, we configure monday.com's Dependency column to preserve predecessor-successor relationships. The Timeline view groups items by Project or Group depending on the source view structure.

Project Central stores no native attachments; documents live in SharePoint and are referenced via links. We map these links to monday.com URL columns on each Item. The URL column preserves the original SharePoint link so that clicking opens the document in SharePoint as before. If the customer's migration also involves moving SharePoint content to a different document management system (e.g., monday.com Workdocs, Google Drive, Box), we flag this as a separate document migration scope during discovery.

Project Central task Owners map to monday.com Team Members. We resolve owners by email match against the monday.com workspace user list. Any Project Central Owner without a matching monday.com Team Member goes to a reconciliation queue for the customer to provision before record import. Team Members without corresponding owners in the source are not created as part of migration.

Project Central activity logs record task-level changes (status changes, assignment changes, date updates). We map these to monday.com Item Updates (the activity feed on each Item). If the source logs are high-volume and contain audit-level detail, we may recommend preserving them as a separate document rather than flooding the Item timeline; the customer decides during scoping.

Project Central may contain time-tracking data depending on the customer's configuration. If present, we map time entries to monday.com's Time Tracking column (available on Pro and Enterprise) or to a Numbers column with hours stored as decimal values. We flag time entry presence at the scoping stage because monday.com's native Time Tracking requires Pro tier or above.

Project Central supports task dependencies in some configurations. If the source data contains predecessor-successor relationships, we map these to monday.com's Dependency column (Pro and Enterprise). The Dependency column enables automatic schedule adjustment when a predecessor task shifts. We flag this feature requirement at scoping because it requires Pro or Enterprise tier on monday.com.