Migrate your ITM Platform data

Projects are the primary container object in ITM Platform, supporting both Agile and Waterfall methodologies. We migrate projects with their full property set including dates, status, owner, budget, and methodology flag via the /projects endpoint.

Programs group related Projects under a portfolio-level container. We preserve the program-to-project parent-child relationship and migrate the program's strategic alignment tags as extended properties.

Portfolios sit above Programs and Projects in ITM Platform's hierarchy. We map the portfolio structure as a top-level container, extracting all child Programs and Projects in the correct containment order.

Tasks are the core work-unit object attached to a Project. We migrate task name, description, dates, status, assignee, estimated hours, and priority via the /tasks endpoint, preserving parent-child task relationships.

Subtasks are nested under Tasks in ITM Platform. Where the destination platform does not support a two-level task hierarchy, we flatten Subtasks into the parent Task as a structured checklist or custom multi-value property.

Baselines capture schedule, cost, and revenue snapshots for a Project. ITM Platform stores baselines as an array per project. We extract all baseline records and store them as a structured dataset attached to the project, since destinations typically do not have a native baseline object.

Milestones are standalone date-driven markers that can belong to Projects or Tasks. We migrate them as date properties with a milestone flag, merging them into the destination's task or project record where no native milestone object exists.

Custom fields are entity-scoped (project, task, purchase, risk, etc.) and stored as key-value pairs per entity. We extract each custom field definition and its values, then remap them to equivalent custom fields in the destination or encode them as structured JSON properties.

Risks are a distinct entity type in ITM Platform with custom fields. We map the risk name, description, probability, impact, owner, and mitigation plan. Where the destination does not have a native risk object, we convert risks to a custom object or attach them as properties to the parent project.

Purchases are an entity type used for procurement tracking linked to Projects. We extract purchase name, amount, vendor, status, and custom field values and map them to the destination's equivalent purchase or budget line-item object.

Users are referenced by UserID across Tasks, Risks, and Assignments. We migrate the user list with name, email, and role. We remap UserIDs to the destination's user identifiers during the assignment step of migration.

Time entries track hours logged against Tasks or Projects. We migrate time entry records with date, hours, user, and description. Where the destination lacks a native time-entry object, we store entries as a structured dataset attached to the parent project.

ITM Platform's API does not expose a documented file-attachment endpoint for downloading uploaded documents. We skip binary attachments in the standard migration scope and flag them for manual handoff. Customers can export attachments manually via the UI before the migration window.

Comments on Tasks and Projects are migrated as plain-text thread entries attached to the destination's equivalent task or project record. Formatting and user-mention metadata are stripped during translation.