Migrate from Project Insight to monday Work Management

Project Insight Projects map to monday.com Boards. The project name, description, status (Active/Completed/On Hold), start date, and target end date transfer to the board's name, description, and date columns. Project Insight's portfolio and program groupings map to monday.com Workspaces, where each Workspace contains boards representing individual projects or related project clusters. We run the Projects report first in the export sequencing to establish the board creation list before any item-level data loads.

Project Insight Tasks map to monday.com Items. The task name, description, start date, end date, estimated hours, and status transfer to the item's name, description, and date columns. The task hierarchy (parent-child relationships) exports from Project Insight as a flattened path or indent structure that we use to create Subitems in monday.com, preserving the WBS tree. We apply the same dependency resolution sequence used in Project Insight by setting monday.com Dependency columns after the item creation batch completes.

Project Insight's parent-child task relationships export as a hierarchy report with indent levels. Tasks with a parent ID become Subitems of the parent Item in monday.com. We resolve the parent item's monday.com ID at migration time using the Project Insight task ID as a cross-reference key stored in a temporary column, then update each Subitem's parent reference before the batch closes.

Project Insight predecessor-successor task relationships (Finish-to-Start, Start-to-Start, Finish-to-Finish, Start-to-Finish) export via the dependency report. These map to monday.com's Dependency column (available on Pro plan and above). We translate the constraint type and lag days into the dependency column value and note which items had cross-project dependencies that may require the customer to configure board linking in monday.com post-migration.

Project Insight Resources (name, role, email, availability percentage, allocation) map to monday.com Users. We extract the resource list from Project Insight's resource management report and match by email to the monday.com workspace members. Resources that have no matching monday.com user go to a reconciliation queue for the customer's admin to provision before the migration batch runs. The resource's allocation percentage migrates as a numeric custom column for display in monday.com's Workload view on Pro+.

Project Insight time entries (linked to Project and Task, with hours, date, resource attribution, and description) map to monday.com's native Time Tracking column on Pro plan and above ($19/seat/month). If the destination monday.com account is on Standard or below, time entries migrate as a numeric custom column labeled Hours Tracked with date and resource attribution stored in separate columns. We confirm the destination plan tier during scoping to set the correct target column type.

Project Insight custom fields at the project level (available on Pro plan and above) map to monday.com custom columns within the board. Each named custom field in Project Insight becomes a typed column in monday.com: text fields map to Text columns, numeric fields to Numbers columns, date fields to Date columns, and dropdown selections to Dropdown or Status columns. We confirm the source account is on Pro or higher before attempting this mapping; Free-tier accounts do not expose custom field definitions or values in the export.

Project Insight custom fields at the task level map to monday.com custom columns at the item level. Same type-mapping logic applies as with project-level custom fields. Task-level custom fields that use a picklist in Project Insight map to monday.com Dropdown columns with the same option values. If the source account is on the Free tier, this mapping is skipped because task-level custom fields are not available.

Project Insight scheduling constraint types (ASAP, Finish No Earlier Than, Finish No Later Than, Start No Earlier Than, Start No Later Than) export as a text field per task. monday.com has no native scheduling constraint model. We carry the constraint type as a text or dropdown custom column labeled Constraint Type on each item. We flag which items have hard deadline constraints (Finish No Later Than, Start No Later Than) so the customer's project manager can review and reapply scheduling logic in monday.com's Timeline and dependency configuration post-migration.

Project Insight Portfolios and Program groupings export as a portfolio-to-project association table. Each portfolio becomes a monday.com Workspace, and the associated projects become Boards within that Workspace. We create the Workspace first, then create Boards within it using the association table. If the customer uses multi-level portfolio hierarchy, we flatten it to a single Workspace level with a naming convention that preserves the hierarchy (e.g., Portfolio Name > Program Name > Project Board).

Project Insight does not include file attachments in its report export output. Any documents, images, or linked files attached to Projects or Tasks will not be carried over in the standard migration. We recommend running a parallel file migration: a direct download from Project Insight followed by upload to monday.com's native file storage or a connected third-party storage integration (Google Drive, SharePoint, Dropbox). We can coordinate the sequencing so that file links are restored alongside the record migration using monday.com's file upload API after the item batch completes.

Project Insight project statuses (Active, Completed, On Hold, Archived, Cancelled) map to monday.com Status column values. We configure the Status column options to match the source project's status vocabulary before migration. Tasks inherit their parent project's status influence where applicable, though monday.com task status is managed independently at the item level.

Project Insight task statuses (Not Started, In Progress, Completed, On Hold, Cancelled, Deferred) map to monday.com Status column options. We create a status group in monday.com that mirrors the source task status vocabulary and map the source status value to the matching option. If the source vocabulary contains statuses with no direct monday.com equivalent (e.g., Project Insight-specific terms), we map to the nearest semantic match and flag for customer review.