Migrate from ITM Platform to monday Work Management

ITM Platform's Portfolio sits above Programs in the hierarchy and groups strategic alignment tags, KPIs, and health metrics. monday.com does not have a native Portfolio equivalent. We map Portfolios to monday.com Workspace-level containers and, where the portfolio contains more than 20 programs, we create a top-level Board Folder to hold the collection of Program boards. Strategic alignment tags and KPI metadata migrate as custom columns on a designated Portfolio Overview board rather than native workspace properties.

Each ITM Platform Program contains multiple Projects under a shared strategic theme. We create one monday.com Board per Program, with the Program name as the Board name and Program-level custom fields (manager, start date, strategic alignment tags) as custom columns on the Board header. The Board inherits the Portfolio's Workspace container, establishing the hierarchy in monday.com's organizational model.

ITM Platform Projects are the primary work container with custom fields, budget, status, and owner. In monday.com, each Project becomes a Group within its parent Program Board, with the Group name matching the Project name. Project-level custom fields (project_code, budget_actual, project_type) map to monday.com custom columns on the Group. Multiple Projects under one Program share the Board but are isolated in separate Groups, preserving the portfolio hierarchy without requiring a separate Board per Project.

ITM Platform Tasks map directly to monday.com Items within the appropriate Group. Task name becomes Item name, task description maps to the Text column, start_date and due_date map to the Date column, assignee maps to the People column, priority maps to a Status or Dropdown column, and estimated_hours maps to a Numbers column. Parent-child task relationships migrate as Item Dependencies in monday.com (if the Pro plan or above is selected) or are stored as a text reference column on child items.

ITM Platform Subtasks are nested under Tasks. Where the destination monday.com plan supports Sub-items (Standard and above), Subtasks migrate as Sub-items maintaining the parent-child relationship. On Free or Starter plans without Sub-item support, Subtasks flatten into the parent Item as a Checklist column. The migration scope documents which plan tier is in use and applies the appropriate structure during migration.

ITM Platform's unlimited baseline tracking captures schedule, cost, and revenue snapshots per project. monday.com has no native baseline object. We extract all baseline records per project as a structured dataset (project_id, baseline_name, snapshot_date, planned_hours, actual_hours, planned_cost, actual_cost, planned_revenue, actual_revenue) and attach this as a JSON dataset to the project board or create a dedicated Baseline Tracking board with one item per baseline snapshot. Customers choosing the parallel board approach can then use monday's Chart and Dashboard features to visualize baseline variance over time.

ITM Platform Milestones are standalone date-driven markers that can belong to Projects or Tasks. We migrate Milestones as a dedicated Date column with a milestone flag (implemented as a Status column value or a checkbox column) on the relevant Item. Milestone name is preserved as a Text column alongside the date for context.

ITM Platform custom fields are entity-scoped (project, task, risk, purchase) and stored as key-value pairs. We extract each custom field definition and remap its type: text fields map to monday.com Text column, numeric fields to Numbers column, date fields to Date column, dropdown values to Dropdown or Status column, and boolean flags to Checkbox column. Each custom field is applied at the board or group level depending on entity scope in ITM.

ITM Platform Risks are a distinct entity type with probability, impact, owner, mitigation plan, and custom fields. monday.com has no native Risk object. We create a dedicated Risk Tracking Board with columns for Risk Name, Description, Probability (Dropdown), Impact (Dropdown), Owner (People), Mitigation Plan (Text), Status (Status), and linked Project (Board Relation). Risks that belong to a specific Project carry a Board Relation column pointing to the parent Program Board.

ITM Platform Purchases track procurement linked to Projects with name, amount, vendor, status, and custom fields. monday.com has no native Purchase entity. We create a dedicated Purchases Board with columns for Purchase Name, Amount (Currency or Numbers), Vendor (Text), Status (Status), and linked Project (Board Relation). Purchase amounts stored as numeric values in ITM migrate directly to monday.com Numbers or Currency columns.

ITM Platform Users are referenced across Tasks, Risks, and Assignments by UserID. We migrate the user list with name, email, and role, and remap UserIDs to monday.com Team Members by email match. Any ITM User without a matching monday.com account is flagged in a reconciliation queue for the customer's admin to provision before record import resumes. ITM role metadata (Project Manager, Resource, Stakeholder) maps to monday.com Team Member roles or is stored as a Text column in a Team Overview board.

ITM Platform Time Entries track hours logged against Tasks or Projects with date, hours, user, and description. monday.com's native Time Tracking column is available on Standard and above and records elapsed time against Items. For ITM entries that include a description and historical date (not just elapsed tracking), we create a Time Entries board with Items per entry or use the native Time Tracking column and log historical entries as past-dated time records. The choice depends on whether the customer needs to preserve the description field.