Migrate from Teamwork.com to Microsoft Project

Teamwork.com Projects map 1:1 to Microsoft Project MPP files. We preserve the project Name, Description, Start Date, and End Date as the project calendar start and finish. Project status (Active, Completed, On Hold) maps to the project-level state. If the customer uses multiple concurrent MPP files, we generate one MPP per Teamwork.com Project. MPP files with blank rows between tasks cause upload failure per Teamwork.com's own import documentation; we strip any null rows during export.

Teamwork.com Task Lists are section headers within a Project that group related Tasks. Microsoft Project does not have a distinct Task List object type. We create a top-level Summary Task row per Task List with the Task List name, and indent all child Tasks beneath it. Task List-level start/due dates become the summary task's constraint dates. If the customer uses list-level milestones, these map to milestone rows under the relevant summary task.

Teamwork.com Tasks map directly to Microsoft Project Task rows. Task Name, Description (mapped to Task Notes), Start Date (maps to Task Start and Baseline Start), Due Date (maps to Task Finish and Baseline Finish), Priority (mapped to a custom Priority field or Text1 column), and estimated time (Work field) transfer 1:1. Task Status (Active, Complete) maps to Percent Complete or Physical Percent Complete depending on the customer's progress-tracking preference.

Teamwork.com Subtasks nested under a parent Task become indented child Task rows in Microsoft Project. The parent Task becomes a Summary Task with an outline level above its child rows. Subtask assignees, due dates, and estimated time carry forward to the child row. Microsoft Project does not auto-complete child tasks when a parent Summary Task is marked complete — this replicates Teamwork.com's native behavior where completing a parent does not cascade to subtasks.

Milestones in Teamwork.com map directly to Milestone rows in Microsoft Project (Task with Milestone = Yes). Milestone names and dates preserve. Milestones linked to specific tasks in Teamwork.com retain their date anchor rather than being re-derived from the linked task timeline.

Project-level Custom Fields in Teamwork.com (available on Premium plan and above) map to custom Text columns in the destination MPP file. We read the Custom Field definitions via the V2 API during extraction, then write values to named custom columns. If the source account is on a Starter or Deliver plan, Custom Fields are API-inaccessible; we flag this during scoping and document the field names and types for manual column addition post-migration.

Site-wide task Custom Fields (administrator-created, globally applied to tasks) require the same Premium-tier access. We retrieve both project-level and site-wide task Custom Fields via the V3 custom fields endpoint filtered by projectId, merge them, and map dropdown-type Custom Fields with their options array to ensure enumerated values are valid in the destination column.

Teamwork.com Tags are comma-separated string labels applied across Projects and Tasks. Microsoft Project does not have a native tag object. We map tags to a Text column in the MPP file with a 'Tags' column header. Multi-value tags are concatenated as a single comma-separated string, matching the behavior of Teamwork.com's native tag storage.

Teamwork.com Users with assigned tasks map to Microsoft Project Resources. The Resource Name maps from the user's Display Name, and the user's email address becomes the Resource Initials or Notes field for identification. Hourly cost rates from Teamwork.com transfer to the Resource Standard Rate field if the customer uses resource cost tracking. Teamwork.com Teams are grouping constructs that do not map to a Microsoft Project entity; we flatten team memberships to individual Resource assignments per task.

Teamwork.com task assignments (a user linked to a Task with optional allocation percentage) map to Microsoft Project Resource Assignments on the task row. The Assigned Resources column in Teamwork.com maps to the Names field on the Assignment row in Microsoft Project. Allocation percentage maps to Units on the assignment.

Teamwork.com Time Entries linked to Tasks carry billable/non-billable flags, hourly rates, and logged durations. Microsoft Project has no native billing or time tracking object; we map the logged hours to the Work field on the corresponding Task, with the billable flag preserved in a custom Notes entry or a Text column. If the customer requires billable vs non-billable differentiation, we document it for reconstruction in a separate time-tracking tool or Project Online resource plan.

Teamwork.com Comments on Tasks include author attribution, timestamp, and formatted text. Microsoft Project Task Notes is a single rich-text field per task. We append all comments to the task Notes field in chronological order with author and timestamp headers. Nested comment threads are flattened to maintain the conversation order. Large comment volumes per task may require truncation or a companion document for review.