Migrate from Zoho Projects to monday Work Management

Zoho Projects map 1:1 to monday.com Boards. Project metadata (name, description, status, start/end dates) migrates as Board name, Board description, Board status (via a Status column), and Date columns. We create one monday Board per Zoho Project, preserving the original project name and any custom fields defined at the project level as Board columns where monday supports them.

Zoho Task Lists map to monday.com Groups within the target Board. We preserve Task List ordering as Group ordering and copy the Task List name as the Group label. Task Lists are the Zoho container for sequential or grouped tasks, which aligns with monday's Group concept even though the semantic depth differs.

Zoho Tasks map directly to monday.com Items within the target Group. Standard fields (name, description, start date, end date, priority, assignee) map to Item name, Description column, Date range columns, Status labels, and Person columns respectively. Subtasks are handled as Subitems (see mapping below). Parent task status and milestone linkage are preserved via Status column values migrated from Zoho task status.

Zoho subtasks map to monday.com Subitems on the parent Item. Zoho supports two levels of subtask nesting (task within task within task). monday.com Subitems are a single-level construct available on Pro and Enterprise plans. We flatten Zoho's two-level subtask chain into a flat Subitem list on the top-level parent Item and flag any nested subtasks of subtasks in the migration report for manual reassignment. If the destination monday workspace is on a lower tier without Subitems, we promote second-level subtasks to first-level Items in the same Group.

Zoho Milestones are date-bound markers that group tasks. monday.com has no standalone milestone object, so we create a Date column capturing the milestone target date and a Status label (e.g., 'Milestone: On Track', 'Milestone: At Risk') on each item that belongs to a Zoho milestone. The milestone name becomes a text label or a dedicated column depending on the destination schema. This is a known structural difference documented upfront so the customer decides the preferred display before migration.

Zoho finish-to-start and other dependency types are stored per task. monday.com Dependency columns (which surface predecessor links in Gantt and Timeline views) are available on Pro and Enterprise plans. We migrate dependency records to monday Dependency columns where the destination plan supports them; on Standard plans we write a predecessor link description into the Item's Description column as plain text for manual rebuild in the Gantt or Timeline view.

Zoho time logs linked to tasks include hours, date, user, billing rate, and billable/non-billable flags. monday.com's Time Tracking column (Pro plan) logs hours per Item with a user attribution. We migrate time entries as Time Tracking records on Pro workspaces. On Standard workspaces, we create a Number column (Hours) and a Date column per entry, noting that multi-entry days consolidate into multiple rows. Billing rate and billable flags have no native monday equivalent and are preserved in a Text column for reference.

Zoho Forums are project-level discussion threads with replies, authors, and timestamps. monday.com Board Updates is the closest equivalent — a threaded update stream per Board. We migrate forum threads as Board Updates, using the forum post author as the monday user and preserving the reply chain and timestamps. If the destination has no matching monday user for the forum author, we create a placeholder user and flag it in the reconciliation report.

Zoho task and issue comments migrate to monday Item Updates. We preserve the comment body, author, and timestamp as a monday Update attached to the parent Item. Author mapping follows the same email-lookup process as the User mapping step; unresolved authors are flagged for admin review.

Zoho Issues are tracked separately from tasks with their own status workflow (Open, In Progress, Resolved, Closed). We migrate issues as Items within a dedicated 'Bugs' or 'Issues' Group in the target Board. The Zoho issue status maps to a monday Status column; issue severity and type picklists map to Status or Labels columns. Custom field mapping is required for any severity/type fields because the picklist values may differ between source and destination.

Zoho documents are stored in Zoho's file store and referenced by file ID or URL. We preserve attachment metadata (filename, size, upload date, uploader) in a migration report. File binary transfer depends on the destination monday workspace's storage limits. We re-upload files where the destination plan permits; for large file counts we coordinate with the customer to provision additional storage or use an external file link column pointing to the original Zoho URL if the source remains accessible.

Zoho custom fields on Projects, Tasks, and Issues require type-mapped migration to monday column types. Text fields map to Text columns; date fields to Date columns; numeric fields to Number columns; dropdowns to Status or Labels columns; user-picker fields to Person columns; checkbox fields to Checkbox columns. We extract the custom field definition schema from Zoho and the target monday workspace column schema before migration, then generate a field-type mapping table for the customer to approve before import.

Zoho Users (with roles and project-level permissions) map to monday Users by email address. We export the Zoho user list including name, email, role, and project-level permission flags. The monday workspace must have matching user accounts provisioned; we match by email and flag any Zoho users without a monday counterpart for the customer's admin to create before the main migration begins. Zoho project-level permissions do not map to monday's Board-level permission model and are documented for manual rebuild.

Zoho tags applied to tasks and issues migrate to monday Labels columns on Items. We export the tag name and the task or issue ID it is attached to. Labels in monday must be pre-created in the workspace or board to receive records; we generate the label creation list from the Zoho tag inventory before migration.