Migrate from Project KickStart to monday Work Management

Each Project KickStart Project becomes a monday.com Board. We map the Project name to the Board title, Project description to the Board description or a Welcome column, and Project cost and complete rate to custom number and progress columns. The source Project ID is preserved in a reference text field for audit. monday.com's Board-level permissions (private vs public, team access) are configured during migration based on the Project's team scope in Project KickStart.

Project KickStart Phases map to monday.com Groups within the target Board. We create one Group per Phase in the same order as the Project KickStart outline, preserving the Phase name and any Phase-level Notes as Group descriptions or a dedicated text column. Phase-level milestones can be expressed as date columns or milestone icons within the Group header in monday.com.

Project KickStart Tasks map to monday.com Items within the corresponding Group. We map task name, planned start date (Date column), planned end date, assigned owner (People column), cost (Number or Currency column), and complete rate (Progress column). Custom task fields in Project KickStart map to custom columns in monday.com, which are created during schema preparation. Task-level Notes migrate as Updates on the Item.

Project KickStart SubTasks nest under Tasks. monday.com's subitem feature (available on Standard and above) handles this natively. We map SubTask name, dates, assignee, and completion rate to the subitem's corresponding columns, preserving the parent-child relationship via the subitem's parent link. If the destination monday.com plan is Basic (no subitem support), we flatten SubTasks into Items with a name prefix for disambiguation and flag this constraint during scoping.

Project KickStart Goals are a platform-specific planning concept with no direct monday.com equivalent. We preserve Goal text as a multi-line text custom column on the Board or as a text column on the Project-level Item. Customers should verify that the destination plan allows sufficient custom column capacity. Stakeholders should understand where this planning context lands post-migration; we document the Goal landing location in the migration report.

Project KickStart Obstacle and Risk entries map to a Risk custom column (text with label or a dedicated Status tag group) on the Board. We preserve title, description, and any linked tasks as a text reference. If the customer uses a separate risk tracking board in monday.com, we can create a dedicated Risk Board and link Items via the connect boards column, though this is a configuration option reviewed during scoping.

Project KickStart Task Assignees (team member names) map to the monday.com People column on Items and subitems. We resolve assignees by name or email match against the monday.com workspace User list. Assignees without a matching monday.com User go to a reconciliation queue for the customer's admin to provision before Item import resumes. We flag duplicate names (two different people with the same name) during scoping.

Project KickStart explicit finish-to-start and start-to-start task dependencies are reconstructed using monday.com's native dependency column. We resolve the task ID pairs from both systems, set the dependency direction in monday.com (blocking item links to dependent item), and verify the dependency graph produces the expected schedule order in the Timeline view. Cross-board dependencies (dependencies pointing to Items on a different Board) require either merging those Projects into one Board or using the connect boards column, which we flag and resolve during scoping.

Project KickStart file attachments linked to Tasks or Projects migrate to monday.com File columns on Items or as file attachments on Item Updates. File path references from Project KickStart exports are resolved against the source file store; if files are stored locally on a Windows machine not accessible post-migration, we flag this as a data-loss risk and recommend the customer consolidates file locations before migration. monday.com's storage limits apply (20GB on Standard, 100GB on Pro) and we flag if estimated attachment volume exceeds plan capacity.

Project KickStart Comment Logs on Tasks migrate to monday.com Updates on the corresponding Item, preserving author name, timestamp, and text content. Updates are posted in chronological order. If Project KickStart Comments have attachments, those migrate as Update attachments in monday.com. We note that monday.com's Update model differs from a threaded comment system; we do not restructure comments into threads if the source did not use them.

Project KickStart Project Templates contain the outline structure, phases, placeholder tasks, and default values. We export the template as a Project, migrate it to monday.com as a regular Board, and the customer's admin duplicates the Board as a monday.com Template from the Board settings. We do not recreate automations or column configurations from Project KickStart templates as code; we document the template structure for manual rebuild in the handoff report. monday.com's 200+ template library is also available as a reference for standardizing the rebuilt template.

Project KickStart pushes tasks and calendar events to Act! CRM and Microsoft Outlook via a proprietary integration that does not store those records in Project KickStart's own data store. These external sync records are outside the migration scope and cannot be extracted from Project KickStart. We do not attempt to migrate Act! contacts or Outlook calendar entries as part of this migration; the customer configures the monday.com Outlook and calendar integrations separately post-migration.