Migrate from Zoho Projects to Asana

Zoho Projects map directly to Asana Projects. We preserve project name, description, status (active/archived mapping to Asana's active/archived), start date, and end date. Custom fields on the project level migrate to Asana custom fields which must be pre-created before migration. Project-level custom fields require a separate custom-field creation pass in Asana because Asana does not support custom fields at the project level in the same way; we typically store project-level custom field values as project description notes and flag them for manual field creation post-migration.

Zoho Task Lists map to Asana Sections within a Project. The hierarchical order of Task Lists is preserved as section order within each project. Section boundaries in Asana define the same grouping concept as Task Lists in Zoho, making this a direct 1:1 structural mapping. We extract task_list_id and task_list_order from Zoho to maintain sequence during import.

Zoho Tasks map to Asana Tasks within their parent Section. We preserve name, description (migrated as task notes in Asana), start date, due date, status (open/closed mapping to Asana's incomplete/complete), priority (low/normal/high/urgent mapping to Asana's numeric priority or custom priority field), and assignee. Subtasks are nested using Asana's subtasks API; Zoho's two-level subtask limit translates cleanly to Asana's subtask model.

Zoho subtasks (up to two levels) map to Asana subtasks. We preserve the parent_task_id relationship. Asana supports unlimited subtask depth in practice, but the migration flattens Zoho's two-level model cleanly without data loss. Subtask assignees, due dates, and descriptions migrate as-is.

Zoho Milestones map to Asana Milestones with target date and completion status preserved. We link contributing tasks to the milestone during import so that milestone progress reflects the underlying task completion in Asana. Zoho milestone custom fields migrate to Asana project-level custom fields that the admin pre-creates.

Zoho time entries (hours, date, user, billing rate, task link) migrate to Asana as task custom fields (hours_logged, billing_rate) or as task notes with structured text. Asana Basic and Premium do not include native time tracking; if the team uses Asana Business or Enterprise, we use a time-tracking-compatible field structure. We flag upfront if the destination tier lacks native time tracking and recommend a third-party integration plan (Toggl, Harvest, or another) post-migration.

Zoho Issues (bug tracker with separate status workflow) have no native Asana equivalent. We migrate Issues to a dedicated Asana project as Tasks, preserving severity, type, status, and description. Issue-specific custom fields map to task custom fields in the destination project. The customer receives a written recommendation to evaluate Asana's native bug reporting capabilities or a dedicated tool (Jira, Linear) if bug management depth is critical.

Zoho Forums are project-level discussion threads with replies and author timestamps. Asana has no native Forum object; project-level discussions exist as task Comments, and Workspace-level discussions exist as Conversations. We migrate Forum threads as structured task Comments attached to a representative project task, or as a document in the project's Conversations section, depending on thread context. Thread structure and author attribution are preserved where possible.

Zoho supports four dependency types (finish-to-start, start-to-finish, finish-to-finish, start-to-start); Asana supports finish-to-start primarily with start-to-finish available. We migrate all dependency types and flag any non-finish-to-start dependencies for testing in Asana because the Asana community forum documents known bugs with date recalculation when start-to-finish or finish-to-finish dependencies are used in complex timeline chains.

Zoho Tags applied to tasks map directly to Asana Tags. Tag name collision handling is performed during scoping; if a tag name conflicts with an existing Asana tag, we append a suffix or flag for admin resolution.

Zoho custom fields on Projects, Tasks, and Issues require pre-creation in Asana before migration. We extract custom field definitions (name, type, picklist options for dropdowns) and deliver a written field creation guide for the customer's Asana admin to execute before the migration window. Custom field values are then mapped during the import phase. Dropdown custom fields in Zoho map to Asana enum custom fields; text fields map to text; date fields map to date custom fields.

Zoho users (name, email, role, project-level permissions) map to Asana users by email. We resolve every assignee, milestone owner, and task owner from Zoho against the Asana destination workspace. Users without an Asana account go to a reconciliation queue for the admin to provision. Project-level permissions in Zoho map to Asana project membership (can_edit, can_view) with the caveat that Zoho's granular permission roles do not have a direct Asana equivalent.