Migrate from Work as Team to Asana

Work as Team Projects map directly to Asana Projects. Project name, description, start date, and deadline migrate as-is. We map the Project privacy setting (internal vs client-facing) to Asana's project-level visibility and Guest-addition flag. If the Work as Team project has a company-linked client, we document the client contact for manual Guest addition post-migration.

Work as Team Lists present a structural gap: they are a first-class container layer above Tasks with no Asana equivalent. We evaluate each List during scoping. Lists that function as logical groupings within a project map to Asana Sections. Lists that represent distinct workstreams or deliverables with their own timelines map to separate Asana Projects under a Team-level folder. We flag the strategy per project during discovery and present it in the scope document before migration begins.

Work as Team Tasks map to Asana Tasks with title, description (rich text), due date, start date, and priority preserved. Subtasks in Work as Team map to Asana Subtasks (one level only; grand-subtasks are flattened into a single subtask chain or promoted to sibling Tasks with a parent-link custom field). Task status in Work as Team (Not Started, In Progress, Waiting, Complete) maps to Asana task completion state (open vs completed).

Work as Team Milestones have no direct Asana object. We create an Asana Task with the milestone name, the milestone due date, and a custom field Milestone (checkbox or text) set to True. The milestone task is added to the correct project. If Work as Team milestones have a description, we migrate it to the task description.

Work as Team supports per-task checklists (individual items within a Task). These migrate to Asana Subtasks within the parent Task. Each checklist item becomes a subtask with the same title. Completion state maps directly. Checklist ordering is preserved by subtask sequence.

Asana has no native time-tracking object. We migrate Work as Team time entries as custom fields on the related Task: Time Logged (number field in hours), Billable (checkbox), and Time Entry Notes (text). This preserves the historical record but requires a third-party time-tracking integration (Harvest, Toggl, Clockify) for ongoing logging. We document the custom field schema and recommend an integration during handoff.

Work as Team task dependencies (Finish-to-Start, Start-to-Start, Finish-to-Finish, Start-to-Finish) map to Asana dependencies using the Asana Dependences app (formerly a third-party integration, now available natively on Advanced and Enterprise; we document the equivalent approach for Starter using the Relationships feature). Lag time in Work as Team maps to a custom Lag Days field on the dependency relationship.

Work as Team file attachments migrate to Asana Attachments. We apply Asana's 100MB per-file limit during export: any Teamwork attachment exceeding 100MB is flagged for the customer to host externally (SharePoint, Google Drive, Dropbox) with the link stored in a custom URL field on the task. File metadata (filename, upload date, uploader) is preserved in the Asana Attachment record.

Work as Team workspace members map to Asana workspace members. We resolve by email match. Any Teamwork member without a matching Asana user is placed in a reconciliation queue for the customer's admin to provision before production migration. Member role (Admin, Project Manager, Member, Guest) maps to Asana team-level permissions during project sharing.

Work as Team's client companies and their portal access have no direct Asana equivalent. We migrate client contacts as Asana Guests (Starter and above) with explicit project-level sharing rather than a portal. Client contact email, name, and company are preserved. We document each client's projects for manual Guest invitation post-migration.

Work as Team tags migrate to Asana tags. Both platforms use a tag-as-label model. Tag names and colors migrate where color is supported in the export. Tags used across multiple projects in Teamwork become project-level tags in Asana if they were project-scoped, or global tags if they were workspace-scoped.

Work as Team custom fields (text, number, date, dropdown, checkbox, currency, user) map to Asana custom fields of the equivalent type. Dropdown options in Work as Team migrate to Asana enum options. We flag any custom field that references a Lookups to another entity (e.g., linking a Task to a Client) as a custom lookup field in Asana or as a text field with the reference value stored, depending on the target Asana plan.

Work as Team task comments migrate to Asana task comments. Comment body, author (resolved by email to Asana User), and timestamp migrate as-is. Mentions in Work as Team comments do not resolve in Asana and are migrated as plain text with the @username preserved in brackets for manual remediation.

Work as Team automations (Rules) do not migrate as code. We audit every active Rule during discovery, document its trigger, conditions, and actions, and deliver a written inventory with a recommended Asana Rule equivalent. Asana's Rules engine uses a different trigger model (record-created, record-updated, date-arrived, form-submitted) from Teamwork's (action-based within project). The customer's admin rebuilds Rules in Asana Rules post-migration.