Migrate your Teamwork.com data

Projects are the top-level container in Teamwork.com, supporting multiple views (list, board, Gantt, table) and project-level custom fields. We migrate Projects 1:1 with their status, start/end dates, and associated Team assignments. Project templates are referenced but instantiated as new Projects at migration time.

Tasks are the core work unit and carry rich metadata: assignees, due dates, priority, estimated time, and subtasks. We preserve the full task hierarchy including parent-child relationships. Task-level custom field values are migrated alongside the task record. Completing a parent task does not auto-complete subtasks in Teamwork.com, a behavior we replicate at the destination.

Subtasks exist as a distinct nested record type under Tasks. We extract them as a flat list keyed by parent task ID and reconstruct the hierarchy in the destination. Subtasks carry their own assignee, due date, and completion status.

Milestones are date-driven project markers, optionally linked to specific tasks. We preserve milestone names, dates, and linked task associations. Milestones appear in both project-level and portfolio-level views.

Time entries are first-class records linked to tasks or projects, carrying billable/non-billable flags, hourly rates, and logged durations. We map them 1:1 including the billable flag and associated cost/revenue rates where available. Entries logged against tasks inherit the task's billable setting by default.

Custom Fields are available only on Premium subscription plans and above. They exist as project-level, site-wide task, or site-wide project types. We read all custom field definitions via the V3 API, map their types (text, number, dropdown), and migrate values field-by-field. Dropdown options must be reconciled with destination enumerations before import.

Teams are grouping constructs that hold multiple Users and can be assigned to Projects. Permissions are set at the project level per Team. We migrate Team memberships and project-level role assignments. Note that a User can belong to multiple Teams.

Users have profiles with name, email, role, hourly cost rate, and working hours. We extract User records and preserve cost rates for billing reconstruction. User permissions are a combination of site-wide role and project-level Team assignment. Client users have a reduced permission scope.

Comments attach to Tasks and can include @mentions, formatting, and timestamps. We extract full comment text and author attribution. Replies within a comment thread are preserved as nested entries. Attachments embedded in comments are treated as linked files.

Attachments can be linked to Tasks, Projects, or Posts. We extract file URLs and metadata (name, type, size, uploader). Large binary files may require separate blob migration handling depending on destination capabilities.

Tags are applied across Projects and Tasks for cross-cutting categorization. We preserve tag names and associations during migration. Tags in Teamwork.com are simple string labels with no hierarchy.

Invoices are generated from billable time entries and expense records and carry client associations, line items, and payment status. We map invoice headers and line items. Tax configurations and payment gateway references are flagged for manual review since they rarely transfer cleanly across platforms.

Clients are top-level entities that own multiple Projects. Client records carry contact info, billing rates, and a client portal user account. We migrate client records and their associated project ownership linkages.

Teamwork.com allows custom project statuses beyond the default set (Active, Completed, On Hold, etc.). Status names and color coding are customisable per workspace. We map custom statuses to destination equivalents and flag any with non-standard color associations.

Task Lists are section headers within a Project that group related Tasks. They carry ordering and optional start/due dates. We preserve list structure and task ordering within lists. List-level milestones can be migrated as discrete Milestone records.