Migrate from Triskell to monday Work Management

Triskell Portfolios are the top-level container holding Programs and defining organizational strategy. We map each Portfolio to a monday.com Workspace as the highest organizational tier. Portfolio metadata (name, description, owner, creation date) migrates as Workspace properties. Portfolio-level custom fields (budget targets, strategic objectives, OKR alignment) migrate as columns on a configuration Board within the Workspace, documented separately for the customer admin to reference post-migration.

Programs sit between Portfolios and Projects in Triskell's hierarchy and carry budget summaries, status rollups, and custom fields. We map each Program to a monday.com Board. The Program-to-Portfolio linkage is preserved as a Workspace association in monday.com. Program-level custom fields (business case, sponsor, investment request) migrate as Board-level columns. If the customer uses Triskell's financial summary at the Program level, those figures migrate as number columns on the Board.

In Triskell, Projects hold Tasks and carry rich custom fields, budget data, and a status workflow. We map each Project to a monday.com Board or, for simpler structures, to a Group within the parent Program Board. Project budget amounts, planned cost, actuals, and forecasts migrate as number columns. The Project's assigned status workflow from Triskell determines the column set we pre-build on the destination Board before Task import begins.

Triskell Tasks sit under Projects and support assignees, due dates, priorities, effort estimates, and custom fields. We map Tasks to monday.com Items within the parent Board, with Sub-items used when the Triskell Task has child tasks or detailed checklist breakdowns. Parent-project IDs are resolved to Board IDs at migration time. Task ordering and sequence fields from Triskell map to monday.com's Item position index within its group.

Triskell custom fields exist independently at each hierarchy level and must be enumerated per object type because there is no single schema export. We request a field inventory screenshot or export from each object level before migration, then build the corresponding monday.com column schema per Board. Text, number, date, and dropdown field types map directly to monday.com column types. Multi-select picklists from Triskell map to monday.com Dropdown or Tags columns. Any field discovered during migration that was not in the original inventory triggers a schema reconciliation step before affected records are written.

Triskell supports distinct named workflows per project type, each with its own set of status stages. We export the active workflow configuration for each project before migration, then pre-build the corresponding column set on the destination monday.com Board. Status probability percentages from Triskell do not map to monday.com natively; we document them as a reference table for the customer's admin to configure as column settings post-migration. Records with status values that do not map cleanly are held in a review queue rather than written with a default status.

Triskell's real-time expense tracking, cost estimation, budget planning, and financial forecasting per project migrate as monday.com number columns. We map planned_budget, actual_cost, forecast_cost, and variance as separate number columns. Currency alignment from Triskell migrates as a text or dropdown column since monday.com does not have a native currency field type. Any currency rounding or decimal precision differences are flagged before data is written.

Triskell user records and ownership assignments (Portfolio Owner, Program Manager, Project Sponsor, Task Assignee) map to monday.com Workspace Members and Item Assignee columns. We resolve owners by email match against the monday.com workspace member list. Triskell-specific ownership roles (Sponsor, SteerCo Member) that have no monday.com equivalent are documented as a Role column or as a tag on the relevant item for administrative reference post-migration.

Triskell Risk Registers and Issue Logs attached to Projects migrate as Items on a dedicated monday.com Board or as labeled Items within the Project Board. Risk severity and probability fields map to monday.com Dropdown or Label columns. We flag whether the destination has an existing Risk Management board and merge accordingly. Historical risk status transitions do not migrate as activity history; they are recorded as a text field on the Item.

Triskell attachments linked to Projects and Tasks migrate as a file reference inventory rather than as uploaded files. We extract the file name, linked object, and any accessible download URL. monday.com does not accept external file URLs during standard item creation; we document the full file list so the customer's team re-uploads attachments post-migration. If Triskell exposes a direct download endpoint via its integration layer, we attempt to migrate the file content as a monday.com File Upload column value.

Triskell dashboards and saved reports are UI-layer constructs built from saved queries that are invisible to the export function. These do not migrate. We document every visible dashboard from the Triskell instance, listing each widget's metric, filter, date range, and data source as a written specification that the customer's monday.com admin uses to rebuild equivalent Board views or chart widgets post-migration.

Triskell Adapt workflow rules and project-type automation triggers do not migrate to monday.com. The two platforms use different automation models with different trigger types, conditions, and action sets. We deliver a written inventory of every active Triskell workflow rule with its trigger, conditions, actions, and a recommended monday.com automation equivalent. The customer's monday.com admin rebuilds them as automation recipes post-migration.