Migrate your Zoho Projects data

Projects are the top-level container in Zoho Projects. We export all project metadata including status, dates, and custom fields. There is no limit on the number of projects in paid tiers.

Task Lists sit one level below Projects and contain ordered tasks. We preserve the list order and associate each list with its parent project via project_id.

Tasks are the core work unit. We export all standard fields: name, description, start/end dates, status, priority, assignees, and dependency links. Subtasks are nested as a separate field array within the parent task.

Zoho Projects supports two levels of subtasks. We flatten subtask relationships into a parent_task_id reference so the destination can reconstruct the hierarchy if needed.

Milestones are date-bound markers that can group multiple tasks. We export milestones with their target dates and link them to the tasks that contribute to their completion.

Time logs are linked to tasks and include hours, date, user, and billing info fields. We export timesheet records as first-class time entries and associate them with their parent task ID.

Issues are tracked separately from tasks and have their own status workflow. Custom field mapping is required because issue severity and type picklists may differ between source and destination Zoho instances.

Forums are project-level discussion threads. We export the full thread including replies, author, and timestamp. Author mapping requires user ID translation if the destination has a different user directory.

Documents are stored in Zoho's file store and referenced by URL or file ID. We preserve attachment metadata (filename, size, upload date) but file binary transfer depends on the destination's storage connector.

Custom fields can be added to Projects, Tasks, and Issues. We extract the custom field definitions and their values, then map them to equivalent custom fields in the destination or store them as property bags if no matching field exists.

Users have roles and project-level permissions. We export the user list including email, name, and role, then map to the destination user by email or create placeholder users if the destination is a different platform.

Workflow rules in Zoho Projects are configuration-level records that define triggers and actions. We do not export workflow definitions because they are tightly coupled to Zoho's rule engine and do not map cleanly to other platforms.

Tags are applied to tasks and issues. We export the tag name and the task ID it is attached to. Mapping to the destination requires checking for tag name collisions.

Comments on tasks, issues, and milestones are exported as standalone records with a parent_object_id and parent_object_type reference. We preserve the author, timestamp, and body text.

Finish-to-start and other dependency types are stored per task. We export the dependency type and the dependent task ID. The destination must support the same dependency model or we convert them to predecessor links.