Migrate from Triskell to Asana

Triskell Portfolios are the top-level strategic container with ownership and metadata but no direct Asana equivalent. We map Portfolios to Asana Workspaces (for multi-division organizations) or to top-level Projects with a Portfolio flag custom field. If the customer has multiple Portfolios representing distinct business units, each becomes a separate Asana Workspace or a dedicated Team. Parent Portfolio metadata migrates as a text custom field and a Workspace-level description.

Triskell Programs sit between Portfolios and Projects and carry budget summaries, status rollups, and custom fields. We map Programs to Asana Projects at the team level, preserving the Program-to-Portfolio linkage via a custom field (parent_portfolio_ref__c) that references the destination Workspace or Project. Programs with no child Projects migrate as standalone Projects with a program_type__c custom field set to 'program' for identification.

Triskell Projects are the primary work container and map directly to Asana Projects. We map project name, description, status, start and due dates, and owner directly. Custom fields at the Project level migrate to Asana custom fields scoped to the project or to the team's portfolio of projects. Triskell's per-project-type status workflows require a stage-mapping table built during scoping; any status value not valid in the destination Asana project is flagged before import.

Triskell Tasks map to Asana Tasks under their parent Project. We preserve task name, description, assignee, due date, start date (requires Asana Premium), priority, and custom field values. Task ordering and hierarchy within the parent Project are preserved via Asana Sections and via the parent_task_gid field for subtasks. Triskell Tasks without a due date migrate as dateless Asana Tasks.

Triskell custom fields at the Portfolio level (e.g., strategic priority, portfolio owner, investment tier) migrate to Asana custom fields at the Workspace level or as Project-level custom fields on top-level Portfolio Projects. We enumerate all Portfolio-level custom fields from the customer's configuration export, map data types to Asana field types (text, number, date, enum, multi-enum), and create them before Portfolio-level records are written.

Triskell custom fields at the Program level (e.g., program sponsor, investment request status, capacity headroom) map to Asana custom fields scoped to the Projects that represent Programs. We apply the same type-mapped approach and create the destination fields in the target Asana project before Program records are imported. Fields that reference picklist values valid in Triskell but not in Asana are flagged for the customer to define before import.

Triskell custom fields at the Project and Task levels migrate to Asana custom fields at the corresponding project and task level. Number fields (e.g., budget allocated, actual spend) map to Asana number fields with currency formatting where applicable. Multi-select fields map to Asana enum or multi-enum fields. We validate picklist values against the Asana destination project before writing records with a held-reconciliation queue for any unmapped values.

Triskell's native budget tracking (budget amounts, actuals, forecasts, and expense data) has no Asana equivalent. We migrate these as custom number fields: budget_allocated__c, budget_spent__c, budget_forecast__c, and budget_variance__c. Currency data migrates as a number with the customer's base currency noted in a separate field. Financial reporting built on these fields must be reconstructed in Asana as custom reports or connected to an external BI tool.

Triskell user records and project/program ownership assignments migrate as owner references in Asana. We resolve Triskell owner records by email against the destination Asana organization's User table. Any Triskell Owner without a matching Asana User goes to a reconciliation queue; the customer's admin provisions the missing User before record import resumes. Inactive Triskell users are mapped to inactive Asana Users if historical assignment must be preserved.

Triskell supports distinct status workflows per project type. We export the active workflow configuration from Triskell and build a stage-mapping table for each project type. In Asana, we use the native Project Status field (on track, at risk, off track) as a summary indicator, and create a custom enum field (triskell_status__c) to preserve the original Triskell workflow stage value. Records that reference unmapped status values are held in a review queue rather than written silently with a default status.

Triskell file attachments linked to Projects and Tasks migrate to Asana attachments on the corresponding Tasks. We migrate file references where the platform exposes a download URL through the CSV export. Files exceeding Asana's 100MB attachment limit are flagged in the migration inventory with file name, size, and original location for manual re-upload. We document the full attachment list in the scoping worksheet so the rebuild effort is scoped rather than discovered post-migration.

Triskell dashboards and saved report configurations are UI-layer constructs built from saved queries and visualization settings. They are not accessible via standard data export and are not migrated by FlitStack AI. We document every Triskell dashboard's constituent metrics, filters, and data sources in the scoping worksheet so the customer's admin can reconstruct them in Asana using Asana Portfolios (Business tier) or custom BI connections.