Migrate from Triskell to Jira

Triskell Portfolios are the top-level strategic container. Each Portfolio maps to a Jira Project as the parent entity. Jira does not have a native Portfolio-level object, so we set the Jira Project as the Portfolio proxy and document the Portfolio name, description, and strategic objective in the Jira Project description field. If multiple Triskell Portfolios exist, they map to multiple Jira Projects or to a Jira Projects-in-Domain structure.

Triskell Programs sit between Portfolios and Projects and carry budget summaries, status rollups, and custom fields. We map each Program to a Jira Epic within the corresponding Jira Project, preserving the Program's metadata as Epic description and custom fields. Program-level budget rollup values are flagged for manual entry into a Jira-compatible budgeting add-on since Jira has no native financial object.

Triskell Projects are the primary work container with rich custom fields, multiple status workflows, and budget tracking. We map Triskell Projects to Jira Project components, to Jira Epic children (Stories and Tasks), or to a Jira Project-level label scope depending on the customer's intended Jira Project structure. Status workflow differences are resolved via a stage-mapping table before import. Custom field values migrate to typed Jira custom fields that we pre-create during schema deployment.

Triskell Tasks map to Jira Stories, Tasks, or Sub-tasks based on their hierarchy position. Tasks with no child tasks become Jira Stories or Tasks; Tasks that are children of other Tasks become Jira Sub-tasks. Task assignees, due dates, priorities, and custom field values migrate directly. Parent-project IDs are preserved as Jira Epic links or as parent Issue links to maintain traceability across the Triskell-to-Jira hierarchy.

Triskell allows independent custom fields at Portfolio, Program, Project, and Task levels. We enumerate the complete custom field schema per object level during scoping and pre-create equivalent Jira custom fields (with correct Jira field types: text, number, date, select, multi-select, user picker) before any data import. Custom fields that do not have a Jira equivalent are flagged in the scope document. Any field discovered during migration that is missing from the Jira schema triggers a schema reconciliation step before records are written.

Triskell's real-time expense tracking, cost estimation, and financial reporting per project have no native Jira equivalent. We migrate budget amounts, actuals, and forecasts as Jira custom number fields on the Epic or Project level. Currency and rounding differences are flagged. The customer must select and install a Jira-compatible budgeting add-on (such as Structure or a dedicated financial add-on) post-migration; we document the full financial field inventory and recommended add-on mapping in the scope deliverable.

Triskell user records and project/program ownership assignments migrate as Jira User references. We map source user IDs to Jira user accounts via an explicit mapping table using email as the dedupe key. Any Triskell Owner without a matching Jira User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Archived or inactive Triskell users are mapped to Jira inactive users at the customer's direction.

Triskell supports distinct status workflows per project type. We export the active Triskell workflow configuration and build a stage-to-status mapping table for each Jira project before import. Records that reference a Triskell status value with no Jira equivalent are held in a review queue rather than written silently with a default status. Jira workflows are configured per Jira project during the pre-migration schema deployment.

Attachments linked to Triskell Projects and Tasks are migrated to the corresponding Jira Issues. We migrate file references where the platform exposes a download URL; otherwise we flag the attachment for manual re-upload and document the complete file list in the migration scope. Jira's file size limits (10MB per file on Standard, 250MB on Premium) are checked against the source attachment sizes before import.

Triskell dashboards and saved report configurations are UI-layer constructs built from saved queries and visualization settings. These are not accessible via standard data export and are not migrated by FlitStack AI. We document every dashboard's constituent metrics, filters, date ranges, and visualization type in the scoping worksheet so the customer's admin can rebuild them as Jira Dashboard gadgets or in Atlassian Analytics post-migration.