Migrate from Taskworld to Microsoft Project

Taskworld Workspace maps to a single MS Project plan file (.mpp) for desktop or a Project Online project entry for cloud. We extract workspace-level member lists and map them to the destination resource pool or project team. Workspace-level settings (e.g., guest limits) have no direct MS Project equivalent; we document these in the post-migration handoff as configuration reminders for the customer's admin.

Taskworld Projects map directly to MS Project projects. Project name, description, start date, and target end date migrate to the project-level fields. Taskworld's view type selection (Kanban, Timeline/Gantt, Calendar) does not control anything at the destination; we set the destination to Gantt view by default since that is MS Project's native scheduling mode.

Top-level Taskworld tasks map to summary tasks (WBS level 1) in MS Project. Task name, description (mapped to Notes field), due date (mapped to Finish), start date (mapped to Start), priority, and percent complete transfer directly. The Taskworld percent-complete value becomes the MS Project Percent Complete field at the summary level.

Taskworld nested subtasks map to MS Project sub-tasks within the same WBS hierarchy. We preserve the nesting depth up to MS Project's practical limit of 65,000 tasks per project. Checklist completion percentage from the parent task does not map to a standard MS Project field; we create a custom number field checklist_pct__c to carry this value if the customer's admin requires it for reporting.

Taskworld checklist items (with their completed/pending status) map to MS Project sub-tasks under the parent task. Each checklist item becomes a sub-task with the checklist item text as the task name, and the completion state maps to a flag field or percent complete value. For checklist-heavy workflows, we recommend the sub-task approach; for simple checklists, a text field listing completed items is a lighter alternative.

Taskworld dependency links (blocks/blocked by) map directly to MS Project predecessor fields. We extract the directionality of each Taskworld dependency and map it to the appropriate predecessor type: Finish-to-Start is the default since Taskworld's blocking model maps most naturally to this relationship. Finish-to-Finish and Start-to-Start predecessors migrate when the source dependency type supports it.

Taskworld per-project custom fields have no direct migration path. We extract every custom field definition (field name, data type, and all values per task) and deliver it as a custom field creation guide for MS Project Enterprise fields. The customer's admin creates the corresponding custom fields in MS Project's Organizer before migration; we then populate the values during import. Custom fields scoped to multiple projects consolidate to a single MS Project enterprise field definition.

Taskworld file attachments do not migrate. MS Project has no native attachment migration path. We extract the list of all file references (file name, URL, attached-to task) from Taskworld and produce a file manifest. The customer's admin uploads files to SharePoint or OneDrive and re-attaches them to the relevant MS Project tasks post-migration. We flag any files exceeding 250 MB or non-standard formats for manual handling.

Taskworld time entries per task migrate as notes on the relevant MS Project task if the destination is MS Project desktop, or as assignment hours if migrating to Project Online with resource management enabled. Planned hours do not map from Taskworld time tracking since Taskworld records actual time worked rather than estimated effort. We preserve the logged duration and author attribution as a task note for reference during post-migration billing or audit.

Taskworld workspace members and guest collaborators map to MS Project resources. We extract user name, email, and role (admin, member, guest). Resource type defaults to Material for Taskworld users without specific resource cost rates; the customer's admin sets resource rates in MS Project if cost tracking is required. MS Project desktop has no global user directory, so this mapping is project-scoped. For Project Online, we map users to the PWA Resource Center.

Taskworld tags (string labels on tasks and projects) migrate to an MS Project Text field tag__c. We preserve the tag string and map it as a comma-separated value in the text field. Tag hierarchy (if present in Taskworld) flattens to a single-level string. The customer's admin applies outline codes or enterprise text custom fields if hierarchical tag taxonomy matters at the portfolio level.