Migrate from ITM Platform to Trello

ITM Platform Portfolio is the top-level container with KPI alignment tags and strategic business goals. Trello has no Portfolio or KPI entity. We map the Portfolio name and description to the Workspace name and board description on the primary Trello Board, with the Portfolio's KPI alignment tags stored as Board Labels or as a structured text attachment. If the customer uses multiple Portfolios, each becomes a separate Trello Workspace with its own board set.

ITM Platform Programs group related Projects under a portfolio-level container with strategic alignment tags. Trello has no Program entity. We split each Program into either a dedicated Trello Board (preferred for organizations with fewer than 10 active boards) or into a labeled segment within a consolidated Board using Label names prefixed with the Program name. The choice is made during scoping based on board count and team count.

ITM Platform Projects map to Trello Boards by default. Each Project's name, description, dates, status, owner, and budget migrate to the Board name, description, due date, and custom fields. If the customer prefers a consolidated Board per Program, Projects become Lists within that Board instead, with project-level metadata stored as custom fields on the first card of each project group.

ITM Platform Tasks are the primary work-unit object and map directly to Trello Cards. Task name, description, due date, start date, priority, estimated hours, assignee, and parent-child relationship migrate to Card name, description, due date (from ITM start/due), Label (for priority), checklist item (for estimated hours), member assignment, and card grouping within the List. Parent-child task hierarchy from ITM flattens into card position or a structured checklist if the List ordering is insufficient to preserve the relationship.

ITM Platform Subtasks nested under Tasks become Trello Checklist items on the parent Card. Checklist item name preserves the subtask name. Status does not migrate; checklists do not support status in Trello's free structure. If the destination uses a Premium tier and the customer wants checklist completion tracking, we add a structured note to the card indicating the subtask's original ITM status.

ITM Platform Milestones are standalone date markers linked to Projects or Tasks. We migrate them as Card due dates on milestone-tracking cards (one card per milestone) in a dedicated 'Milestones' List on the destination Board, with the milestone name as card name and the original date as due date. Alternatively, milestones with Task-level scope become Labels on the linked Cards with a milestone date prefix in the label name.

ITM Platform Baselines store schedule, cost, and revenue snapshots per project. Trello has no baseline or scenario-planning entity. We extract all baseline records as a structured CSV attachment on the Board (stored as a Board description update or a pinned card attachment) so the customer retains the historical data for manual reference. This is a data preservation, not a functional migration.

ITM Platform entity-scoped custom fields map to Trello Custom Fields (Premium Power-Up). We extract each custom field definition (field name, type: text, number, date, dropdown) and its values per entity, then configure equivalent Custom Field definitions on the destination Trello Board before import. Text and number fields migrate directly; dropdown values migrate as Custom Field options. Board-level custom fields must be enabled and configured manually by the customer on each Board before migration runs because Trello's Custom Fields Power-Up requires per-board activation.

ITM Platform Risks are a distinct entity with probability, impact, owner, description, and mitigation plan. Trello has no native Risk entity. We migrate Risks as Cards in a dedicated 'Risks' List on the project Board, with Risk name as card name, description and mitigation plan as card description, and probability/impact as Custom Fields. If the customer's Trello is on the Free tier without Custom Fields, probability and impact become Labels and structured text in the card description.

ITM Platform Purchases track procurement linked to Projects with name, amount, vendor, and status. Trello has no native Purchase entity. We migrate Purchases as Cards in a dedicated 'Purchases' List on the project Board, with purchase name as card name, amount and vendor as card description or Custom Fields, and status reflected in List position (Requested, Approved, Ordered). Custom fields on the ITM Purchase entity migrate to Trello Custom Fields if the Premium tier is active.

ITM Platform Users referenced across Tasks, Risks, and Purchases map to Trello Members. We extract the user list (name, email, role) from ITM Platform and match by email against the destination Trello Workspace members. Any ITM user without a matching Trello Member is flagged in the reconciliation report for the customer's admin to provision before record import. Workspace-level member invitations are a separate step from data migration and must be completed before assignee mapping can proceed.

ITM Platform Time Entries track hours logged against Tasks with date, hours, user, and description. Trello has no native time-tracking entity. We migrate time entries as Checklist items on the linked Card (e.g., 'Week of 2025-01-06: 4.5h — John D.') or as structured text appended to the Card description if the Checklist approach is too granular. The customer chooses the format during scoping. Trello's time-tracking Power-Ups (like Planyo or TimeCamp integrations) are not configured as part of the migration scope.