Migrate from Triskell to Microsoft Project

Triskell Portfolios have no direct Microsoft Project equivalent. We map each Portfolio to a Project Online Enterprise Project (PWA site) or, for Project for the Web destinations, to a Microsoft Dataverse entry that serves as the top-level grouping. Portfolio metadata (description, owner, start date, status) migrates as Project-level custom fields on the top-level entry. Programs under the Portfolio are mapped to sub-projects or summary-task groups within the same destination entry, depending on the customer's chosen structure.

Triskell Programs map to either a standalone Project within the Project Online site (preferred for independent programs) or a top-level summary task under the Portfolio-level entry (preferred when programs share a budget or timeline). Program budget summaries, status rollups, and custom fields migrate as project-level fields or as custom fields on the summary task. The mapping decision is made during scoping based on whether the customer needs independent scheduling for each program.

Triskell Projects map to Microsoft Project project files (MPP) or Project Online project entries. The Project Name, description, start date, finish date, priority, status, and custom fields migrate to the project-level fields. Tasks under the Triskell Project become tasks within the Microsoft Project file, with Outline Level preserved via the WBS field. Parent-child task relationships are preserved by setting the Outline Number and Summary task structure. Summary-level Start, Finish, and Work fields are recalculated by Microsoft Project after import and cannot be locked.

Triskell Tasks map to Microsoft Project tasks. Standard fields — Name, Start, Finish, Duration, Work, Actual Start, Actual Finish, % Complete, Priority, Notes — migrate directly. Assignees migrate as Resources linked via the Assignment table. Dependencies between tasks (Triskell predecessor-successor) map to the PredecessorLink field with dependency type: Finish-to-Start (Type 1), Finish-to-Finish (Type 2), Start-to-Start (Type 3), Start-to-Finish (Type 4). Cross-project dependencies are flagged for the admin to resolve manually post-import because Project Online requires projects to be checked in to resolve external predecessors.

Triskell allows independent custom field definitions at the Portfolio, Program, Project, and Task levels with no unified schema export. We enumerate custom fields per object level from the customer's in-app configuration export and build a per-level mapping table. Portfolio-level custom fields migrate to custom fields on the top-level Project Online Enterprise Project entry or to SharePoint columns if the destination is Project for the Web. Custom fields that use Triskell-specific picklist values not present in the destination require the admin to define the picklist values before import.

Program-level custom fields in Triskell (status indicators, governance metadata, business-unit flags) map to project-level custom fields in the destination. We validate the destination field type (Text, Number, Date, Picklist, Flag) against the Triskell field type and flag any mismatch. Triskell multi-select or checkbox fields map to Project Online multi-value Enterprise Custom Fields or to a Text field with delimited values if the destination does not support multi-value fields.

Project-level custom fields from Triskell map to Microsoft Project Enterprise Custom Fields defined in Project Online PWA settings. We create the Enterprise Custom Field in the destination PWA (via Project Online Settings > Enterprise Custom Fields) before any project data is imported. Custom fields referencing Triskell picklists with non-standard values are held in a review queue until the destination picklist is populated.

Task-level custom fields from Triskell (milestone flags, cost categories, approval status) map to Microsoft Project task-level custom fields. Project Online supports Enterprise Custom Fields of type Text, Number, Cost, Date, Flag, and Resource; we match each Triskell field type to the nearest Project Online equivalent. Outline Codes are used for hierarchical task classification codes in Project Online.

Triskell budget amounts (planned cost, actual cost, forecast, variance) migrate to Microsoft Project cost fields on the project or summary task. Planned Cost maps to Fixed Cost or Cost field; Actual Cost maps to Actual Cost (calculated from resource rates and actual work). Budget data precision and currency symbols are validated against the destination's regional settings, and any rounding discrepancies are flagged in the reconciliation report. Triskell's financial forecasting data migrates as a custom field if no direct cost field exists.

Triskell users (owners assigned to Portfolios, Programs, Projects, and Tasks) map to Microsoft Project Resources. We resolve by email match against the Project Online Resource Pool. Triskell role-based assignments map to generic Resources if the destination does not have named user provisioning in Project Online. Any Triskell user without a matching Resource in the destination org is held in a reconciliation queue for the customer's admin to provision before task import resumes. Material resources (equipment, software licenses) in Triskell map to Material Resources in Microsoft Project with per-unit cost rates.

Attachments linked to Triskell Projects and Tasks are migrated as Hyperlink fields pointing to the original file URL if the platform exposes a download URL. For files stored within Triskell that cannot be exported via URL, we produce a manifest of file names, sizes, and associated project/task, and the customer re-uploads them manually to the destination SharePoint document library or Project Online project site post-migration. The attachment manifest is included in the scoping worksheet.

Triskell's project-type-specific status workflows (with stage gates and conditional transitions) have no native equivalent in Microsoft Project, which uses only task-level status (Not Started, In Progress, Completed) and % Complete. We map Triskell status workflow stages to a custom Text field on the project or task and document the mapping table in the scoping worksheet. Status-driven workflow automation in Triskell is not migrated (see automation disclaimer).