Migrate from Taskworld to Asana

Taskworld workspaces map directly to Asana organizations (the top-level container). We extract workspace-level member lists, guest collaborator limits, and organization metadata. Taskworld's Business plan allows 30 guests; Enterprise allows unlimited. Asana Starter also limits guests but Enterprise removes this cap. We flag any guest count that exceeds the destination plan ceiling and provide a reconciliation list for the admin to convert guests to full members or provision additional licenses.

Taskworld Projects map to Asana Projects with direct transfer of project name, description, start date, and status (active/archived). The destination project type (Team or Portfolio) is selected during scoping based on the organization's structure. Taskworld's project-level display setting for completed task visibility is preserved as a project metadata flag; Asana does not enforce this behavior natively so the setting is documented for the admin to apply in project settings post-migration.

Taskworld tasks map to Asana tasks with all core properties: title, description (rich text preserved), assignees (mapped by email to Asana User), followers, due dates, priority level, and start dates. Completed status migrates to Asana completion. Task IDs change during migration; we track the original Taskworld ID in a custom field tw_original_id__c for audit and reconciliation.

Taskworld subtasks map to Asana subtasks (first-class tasks nested under parent tasks). Taskworld supports one level of subtask nesting; Asana supports up to five levels. We preserve the Taskworld subtask hierarchy and pad any missing intermediate levels if the source had a flat subtask structure. Each subtask inherits the parent's assignee and due date unless individually overridden in the source.

Taskworld checklist items migrate to Asana Checklist items on the parent task. Completion status is preserved. Taskworld displays a percent-complete calculation based on checklist items; Asana does not auto-calculate this from checklists alone (it calculates from subtasks), so the percent-complete value is stored in a custom field tw_percent_complete__c on the task for reporting.

This is the most complex mapping in this migration. Taskworld custom fields are scoped per-project; the same field (e.g., Customer Name) may exist independently in multiple projects with the same name but different definitions. We extract every custom field definition across all projects, deduplicate by field name and type, consolidate into a single workspace-level custom field in Asana, and apply it to all projects that had a matching field. Field types (text, number, date, dropdown) map directly to Asana custom field types. Multi-select dropdowns in Taskworld map to Asana enumerator (multi-select) fields. Any fields that cannot be consolidated (e.g., two Taskworld fields with the same name but different picklist values in different projects) are flagged for manual resolution.

Taskworld blocks/blocked-by dependency links map to Asana dependency records. We translate the directional link into the appropriate Asana dependency type (Finish-to-Start by default). Note: Asana's dependency date-propagation behavior can produce red arrows if predecessor dates are not adjusted to account for duration, a known Asana quirk documented in the Asana community forum. We apply dependency records but cannot adjust date propagation automatically; this is a manual post-migration review item for the project manager.

Taskworld file attachments migrate to Asana as ContentDocument records attached via ContentDocumentLink to the parent task. The Asana API ignores attachments exceeding 100MB; we skip files above this threshold and provide a manifest of oversized files for manual re-upload to Asana's storage. Taskworld's Business plan caps storage at 1TB; if the workspace approaches this limit, we flag file counts and total storage size during scoping. Files are re-uploaded to Asana's storage during migration.

Taskworld project chat and task-level comments migrate as Asana Stories on the task. Author attribution is preserved where the author maps to an existing Asana User; comments from unmapped users are attributed to the migration service account. Thread structure is flattened to a chronological list; Asana Stories do not support threaded replies natively. Chat history (project-level chat, not task-level comments) migrates as tasks with a specific tag if the customer requests it; otherwise it is documented as out-of-scope.

Taskworld tags and labels migrate to Asana Tags (a workspace-level tagging object). Tag strings are preserved exactly. Asana tags are not tied to specific tasks automatically; they are applied as tags on tasks during migration. Tag hierarchy (if present in Taskworld) is flattened to a single-level tag set.

Taskworld time tracking entries (where available via API on Business and Enterprise plans) migrate to Asana Time Tracking entries if the destination organization is on Asana Advanced or Enterprise tier. If the destination is Starter, time entries are stored in a custom numeric field tw_time_hours__c on the task. Time entry notes and user attribution are preserved as story comments in Asana.

Taskworld workspace members (billed per-seat) map to Asana full members. Guest collaborators (up to 30 on Business) map to Asana guests if the destination plan supports guest licensing; otherwise they are flagged for conversion to full members. We resolve users by email match. Any Taskworld user without a matching Asana user goes to a reconciliation queue for the admin to provision.

Taskworld automations (Business and Enterprise plan only) trigger actions based on task events (status change, due date, assignment). We do not migrate automations as code because Taskworld and Asana automation models are structurally different. We deliver a written inventory of every Taskworld automation with its trigger, conditions, actions, and a recommended Asana Rule equivalent. The customer's admin rebuilds them in Asana Rules Engine (Advanced tier) or Workflow Builder (Enterprise tier) post-migration.