Migrate from Triskell to Trello

Triskell Portfolios represent the top-level strategic container and typically hold multiple Programs. Trello has no Portfolio-level construct. We handle this by creating one Trello Workspace per Triskell Portfolio, using the Workspace description field for Portfolio metadata. Programs within the Portfolio become board-level labels or board groups within the same Workspace. If the customer has multiple Triskell Portfolios, we create a corresponding number of Trello Workspaces and note the linkage in the migration mapping document.

Triskell Programs sit between Portfolios and Projects and carry budget summaries, status rollups, and custom fields. Trello has no Program-level object. We flatten Programs by associating their Projects to shared Trello boards, and we capture Program-level custom field values and budget summaries in a designated card (a 'Program Summary card') on each relevant board with Program metadata stored in card descriptions and labels. The customer's admin decides whether Program rollup data belongs in labels, card descriptions, or a companion Confluence page.

Triskell Projects map directly to Trello Boards. Project name becomes the board name, Project description migrates to the board description, and project status determines which board list serves as the default or entry lane. Triskell Project-level custom fields (such as Project Manager, Department, Priority, or Start Date) become Trello card custom fields on every card in that board. If the destination Trello workspace is on the Free tier, boards are limited to 10 per Workspace; Standard and above remove this limit.

Triskell Tasks map to Trello Cards. Task name becomes the card title, Task description migrates to the card description, due date maps to the card due date field, and assignee maps to the card member. Task priority and custom fields migrate to card labels or custom fields (custom fields require Trello Premium). Task ordering within a Triskell project maps to card position within the target board list. Tasks with sub-tasks in Triskell become Trello checklist items with their own title, assignee, and due date where applicable.

Triskell allows tasks to have their own sub-tasks with independent assignees, due dates, and custom fields. Trello does not support sub-task custom fields; sub-task custom field values from Triskell are appended to the checklist item description or comment. Sub-task hierarchy beyond two levels is flattened into a single checklist level in Trello. We flag any Triskell sub-task with three or more nested levels as a candidate for conversion to a separate Trello card.

Triskell supports custom fields at Portfolio, Program, Project, and Task levels independently. Trello custom fields apply per card via the Custom Fields Power-Up, which is available on Standard and above (not Free). We migrate Triskell custom field values as Trello custom field values on cards. Custom field type mapping: text to text, number to number, date to date, dropdown to dropdown, checkbox to checkbox. Multi-select dropdown in Triskell maps to multi-select dropdown in Trello if the Premium custom fields Power-Up is enabled.

Triskell's financial module — including budget amounts, actuals, forecasts, and cost tracking per project — has no native Trello equivalent. We migrate budget amounts, planned cost, and actual cost as Trello card custom fields (numeric type) when the destination is Trello Premium with the Custom Fields Power-Up. When Premium is not available, financial summary data is stored in card descriptions in a structured format (e.g., 'Budget: €50,000 | Actual: €32,500 | Variance: €17,500'). Trello's native reporting does not support financial aggregation; teams requiring reporting on migrated budget data should plan for a third-party reporting Power-Up such as Screenful.

Triskell user records and project/program ownership assignments map to Trello Workspace members. We resolve owners by email match against the destination Trello Workspace member list. Any Triskell user without a matching Trello account is held in a reconciliation queue for the customer to provision before record import resumes. Member permissions in Trello (admin, normal, observer) do not map from Triskell's role model; we document the Triskell role for each user in the mapping inventory for the customer's admin to assign appropriate Trello permissions post-migration.

Triskell's configurable status workflows per project type define the stages a task passes through. Trello boards use lists as status lanes. We map each Triskell status workflow to a Trello board's list configuration — one list per status value in the workflow. We export the destination board's list structure before migration and build a status-to-list mapping table. Records referencing unmapped status values land in a default 'Backlog' list and are flagged in the reconciliation report for manual assignment.

Triskell attachments linked to Projects and Tasks migrate to Trello card attachments. We extract the Triskell attachment URL (where the platform exposes a download link) and attach the file to the corresponding Trello card. If Triskell does not expose a direct download URL, we provide a manifest of files by record ID for the customer's admin to manually re-upload. Trello Free and Standard limit attachment size to 10MB per file; files exceeding this threshold are noted in the manifest for the customer to assess whether to host externally and link rather than attach directly.

Triskell risk registers track risk ID, description, likelihood, impact, mitigation plan, and owner per project. Trello has no native risk object. We migrate risk register rows as Trello cards on a dedicated 'Risk Register' board or as labeled cards within the project board. Risk fields (likelihood, impact, status) migrate as card labels or card custom fields. Mitigation plans and risk descriptions migrate to the card description. Risk response history and comments do not have a Trello equivalent and are noted in the handoff inventory for the customer's admin to decide on handling.

Triskell dashboards and report configurations are UI-layer constructs built from saved queries and visualization settings. They are not accessible via standard data export and cannot be extracted. We do not migrate dashboards or reports. We document every Triskell dashboard's constituent metrics, filters, date ranges, and visualization type in the scoping worksheet during discovery, so the customer's admin has a written specification for rebuilding them in Trello via a reporting Power-Up or external BI tool. This documentation step is included in the standard migration scope at no additional charge.