Migrate from Teamwork.com to Asana

Teamwork.com Projects map 1:1 to Asana Projects. Project status (Active, On Hold, Completed) maps to Asana's project archived state (false = active, true = archived) with color-coding preserved where supported. Start date and end date transfer to Asana's Project Start Date and Project Due Date fields. Project-level custom fields map to Asana project custom fields on a field-by-field basis; see Custom Fields row for scope merging notes.

Teamwork.com Task Lists are section headers within a Project that carry ordering and optional start/due dates. They have no direct Asana equivalent — Asana uses Sections as the grouping construct within Projects. We map each Teamwork.com Task List to an Asana Section within its parent Project, preserving list-level ordering and start/due date as a Section description note. List-level Milestones (milestones attached to a Task List rather than a standalone date) are flagged during scoping and converted to individual milestone tasks within the Section.

Teamwork.com Tasks map to Asana Tasks with full metadata: assignees, due dates, priority, estimated time, and description. The task hierarchy (parent task ID, child subtask IDs) is preserved as Asana's parent task reference and subtasks field. Priority values (low, normal, high, urgent) in Teamwork.com map to Asana's Custom Fields priority enum if available or to a custom numeric sort field. Task List association is resolved to the target Section during migration.

Teamwork.com Subtasks are distinct API objects carrying their own assignees, due dates, and completion state. In Asana, subtasks are a field on a parent Task rather than a separate object. We flatten the Subtask hierarchy by creating each Subtask as a Task in its own right, then linking it to the parent Task via Asana's subtasks field. Individual Subtask assignees and dates are preserved. Note that Asana's parent task completion does not cascade to subtasks, matching Teamwork.com behavior; we do not implement auto-complete propagation.

Teamwork.com Milestones are date-driven project markers, optionally linked to specific tasks. Asana Milestones are available on Starter and above plans as a distinct feature. We map milestones to Asana Milestones within the parent Project where the Asana plan supports it, preserving milestone name and target date. Milestones with no date or with list-level attachment are converted to tasks with a Milestone tag. Linked task associations are preserved as task dependency notes. Teams on Asana Enterprise can use Goals as milestone grouping structures, which we note as a post-migration option.

Teamwork.com Time Entries carry billable/non-billable flags, hourly rates, and logged durations linked to tasks or projects. Asana has no native time tracking. We map Time Entries to a custom fields group on the related Asana task (total logged hours, billable flag, hourly rate) or deliver them as a separate Time Entries table in a written inventory with task ID lookup keys. Customers who need ongoing time tracking are advised to integrate Timely or Harvest post-migration, both of which have native Asana integrations. Time Entry data is fully extracted from Teamwork.com regardless of destination strategy.

Teamwork.com Custom Fields exist at project-level and site-wide (task and project) scopes. Asana Custom Fields are project-level only with no site-wide equivalent. We retrieve both scopes via Teamwork.com V2 API, merge them by name, and map to Asana project-level custom fields. Dropdown-type custom fields carry an options array that we preserve as Asana enum options. If the same field name exists as both a project-level and site-wide field in Teamwork.com, we flag the conflict and map to separate Asana fields with a naming convention. Teamwork.com Custom Field data only exists if the source account is on a Premium-tier plan or above.

Tags in Teamwork.com are simple string labels applied across Projects and Tasks. Asana Tags are workspace-level labels that can be applied to any task. We map tags 1:1 by name, preserving the full tag set across the workspace. Tags used for cross-cutting categorization migrate as-is; tags used for billing classification (Teamwork.com) are flagged and mapped to the Time Entry strategy.

Teamwork.com Comments attach to Tasks with author attribution, formatted text, and timestamps. Asana Stories serve the same purpose on Tasks. We extract full comment text and author name, creating an Asana Story entry for each comment in chronological order. @mentions in Teamwork.com are preserved as text and noted for manual recreation in Asana Conversations or as @mentions if the mentioned user is an Asana workspace member. Replies within comment threads preserve nesting via the parent Story reference.

Teamwork.com Teams are grouping constructs holding multiple Users, with project-level permission assignments. Asana Teams are workspace-level groupings of people used to organise projects and control access. We map each Teamwork.com Team to an Asana Team, preserving the team name and populating it with matched Asana workspace members. Project-level role assignments (Team = Admin, Member, Guest on a specific project) require post-migration recreation in Asana because Asana permissions are Team-scoped, not project-plus-team scoped.

Teamwork.com Users carry name, email, role, hourly cost rate, and working hours. We map Users to Asana workspace members by email as the dedupe key. The Teamwork.com hourly cost rate transfers to a custom field on the Asana user profile or, if not supported, to a Staff Cost Rates lookup document. Any Teamwork.com User without a matching Asana workspace member goes to a reconciliation queue for the customer's admin to provision.

Teamwork.com Clients are top-level entities owning multiple Projects, carrying contact info, billing rates, and a client portal user account. Asana has no native client object. We map Client records to a custom field on the related Project (Client Name, Client Contact, Client Billing Rate) and deliver a written Client-to-Project lookup table for reference. Customer Portal access from Teamwork.com (Enterprise feature) requires rebuild via Asana's Enterprise Customer Portal offering, which we document in the automation inventory.

Teamwork.com Attachments link files to Tasks, Projects, or Posts with name, type, size, and uploader metadata. Asana Attachments are linked resources (Google Drive links, Dropbox links, uploaded files) attached to Tasks. We extract attachment URLs and metadata, writing them as URL attachments in Asana where the attachment type is a direct link, or noting upload-file attachments as a separate blob migration step depending on the customer's Asana storage allowance.

Teamwork.com Invoices carry client associations, line items, tax configurations, and payment status. Asana has no native invoice object. We extract invoice header and line item data into a written Invoice Inventory document keyed by client and project, preserving invoice number, date, amount, and payment status. The customer recreates invoices in their accounting tool of record (QuickBooks, Xero, FreshBooks) post-migration.