Migrate your Triskell data
Portfolio-centric PPM built for mid-market and enterprise organizations that need to align strategy, funding, and capacity across programs and projects at scale.
In its favor
Why people choose Triskell
The signal that keeps Triskell on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Organizations choose Triskell for its top-down portfolio hierarchy that makes it straightforward to see how programs and projects roll up to strategic objectives, especially when comparing funding requests against capacity.
Customers highlight Triskell's strong financial management module for projects, including budget planning, expense tracking, and forecasting without needing a separate finance tool.
Teams with established PPM processes value Triskell Adapt because it aligns to their existing workflows rather than forcing a pre-configured template, reducing reconfiguration work after go-live.
Mid-market and enterprise organizations cite Triskell's ability to scale across hundreds of projects and programs while maintaining a single source of truth for portfolio-level reporting.
Project managers consistently rate Triskell's customer service highly on review platforms, noting responsive support during implementation and ongoing configuration questions.
Users cite a steep initial learning curve as the primary frustration — the breadth of Triskell's feature set means new administrators require significant training time before feeling productive.
Some organizations report that the platform's depth becomes a constraint for small teams or departments that need lightweight task tracking rather than full portfolio governance overhead.
Customers with highly specialized workflow requirements sometimes find that Triskell's customization model, while powerful, demands more IT involvement than they anticipated, leading to delays in configuration changes.
Reasons to switch
Why people leave Triskell
The recurring reasons buyers give for replacing Triskell. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Triskell fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Triskell pricing overview
Triskell Ready starts at approximately €15 per user per month. Triskell Adapt and Triskell Platform are enterprise tiers priced by custom quotation, with implementation scope and user count driving the final cost. There is a free trial available for the Ready tier.
Triskell Ready
Tier 1 of 3
€15/user/month (starting, per Capterra)
What's included
Need help selecting your Project Management?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Triskell's schedule — see our quote-based pricing →
What gets migrated
Triskell object support
Object-by-object support for Triskell migrations. Per-pair details surface during scoping.
Portfolios
Mapping requiredPortfolios are the top-level container in Triskell's hierarchy. We migrate Portfolio records with their metadata and ownership, but the mapping to downstream Programs and Projects must be preserved via explicit foreign-key correspondence in our migration scripts.
Programs
Mapping requiredPrograms sit between Portfolios and Projects. They carry budget summaries, status rollups, and custom fields. We preserve the Program-to-Portfolio linkage by including parent IDs in the import payload and validate that destination Programs inherit the correct Portfolio context.
Projects
Mapping requiredProjects are the primary work container and support rich custom fields, multiple status workflows, and budget tracking. We map standard project fields directly and apply custom field value mappings sourced from the customer's field configuration export.
Tasks
Mapping requiredTasks live under Projects and support assignees, due dates, priorities, and custom fields. Task ordering and hierarchy are preserved by including parent-project IDs and sequence fields in the import.
Custom Fields
Mapping requiredTriskell allows users to define custom fields at Portfolio, Program, Project, and Task levels. We discover the custom field schema via the customer's configuration export and build field-level value maps before writing records.
Budgets and Financial Data
Mapping requiredTriskell includes real-time expense tracking, cost estimation, and financial reporting per project. We migrate budget amounts, actuals, and forecasts as numeric fields, and flag any currency or rounding differences between source and destination.
Users and Owners
Mapping requiredUser records and project/program ownership assignments are migrated as owner references. We map source user IDs to destination user IDs via an explicit mapping table and flag any unresolved owner references for manual assignment.
Status Workflows
Mapping requiredTriskell supports multiple status workflows per project type. We export the active workflow configuration and apply stage-to-stage mappings at migration time to ensure records land in the correct status on the destination.
Attachments
Mapping requiredAttachments are linked to Projects and Tasks. We migrate file references where the platform exposes a download URL; otherwise we flag the attachment for manual re-upload and document the file list in the migration worksheet.
Dashboards and Reports
Not in this platformTriskell's dashboards and 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.
| Object | Support | Notes |
|---|---|---|
| Portfolios | Mapping required | Portfolios are the top-level container in Triskell's hierarchy. We migrate Portfolio records with their metadata and ownership, but the mapping to downstream Programs and Projects must be preserved via explicit foreign-key correspondence in our migration scripts. |
| Programs | Mapping required | Programs sit between Portfolios and Projects. They carry budget summaries, status rollups, and custom fields. We preserve the Program-to-Portfolio linkage by including parent IDs in the import payload and validate that destination Programs inherit the correct Portfolio context. |
| Projects | Mapping required | Projects are the primary work container and support rich custom fields, multiple status workflows, and budget tracking. We map standard project fields directly and apply custom field value mappings sourced from the customer's field configuration export. |
| Tasks | Mapping required | Tasks live under Projects and support assignees, due dates, priorities, and custom fields. Task ordering and hierarchy are preserved by including parent-project IDs and sequence fields in the import. |
| Custom Fields | Mapping required | Triskell allows users to define custom fields at Portfolio, Program, Project, and Task levels. We discover the custom field schema via the customer's configuration export and build field-level value maps before writing records. |
| Budgets and Financial Data | Mapping required | Triskell includes real-time expense tracking, cost estimation, and financial reporting per project. We migrate budget amounts, actuals, and forecasts as numeric fields, and flag any currency or rounding differences between source and destination. |
| Users and Owners | Mapping required | User records and project/program ownership assignments are migrated as owner references. We map source user IDs to destination user IDs via an explicit mapping table and flag any unresolved owner references for manual assignment. |
| Status Workflows | Mapping required | Triskell supports multiple status workflows per project type. We export the active workflow configuration and apply stage-to-stage mappings at migration time to ensure records land in the correct status on the destination. |
| Attachments | Mapping required | Attachments are linked to Projects and Tasks. We migrate file references where the platform exposes a download URL; otherwise we flag the attachment for manual re-upload and document the file list in the migration worksheet. |
| Dashboards and Reports | Not in this platform | Triskell's dashboards and 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. |
Gotchas
What to watch for in Triskell migrations
Issues we've hit on past Triskell migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No publicly documented REST API for direct data extraction
Dashboard and report configurations are not migration-eligible
Status workflow differences between project types cause import validation failures
Custom field schema varies by object level and must be discovered per customer
| Severity | Issue |
|---|---|
| High | No publicly documented REST API for direct data extraction |
| High | Dashboard and report configurations are not migration-eligible |
| Medium | Status workflow differences between project types cause import validation failures |
| Medium | Custom field schema varies by object level and must be discovered per customer |
Leaving Triskell?
Where Triskell customers move next
5 destinations Triskell can migrate to.
How a Triskell migration works
Four steps, Triskell-specific
Connect
Not publicly documented into Triskell. Scopes limited to read-only on the data we move.
Map
We translate Triskell-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Triskell quirks before production.
Migrate
Full migration with Triskell rate-limit handling. Rollback available throughout.
FAQ
Triskell migration FAQ
Answers to the questions buyers ask most during Triskell migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Triskell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther project management tools we support
Ready when you are
Migrate Triskell.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Triskell setup and destination — written quote back within a business day.