Migrate from Zoho Projects to Jira

Zoho Projects map to Jira Projects. We preserve the project name, description, status (active/completed archived), and start/end dates as Jira Project metadata. Jira Project Key (e.g., PROJ) must be defined; we recommend a 2-10 character alphanumeric key derived from the Zoho project name. Jira project type (Team-managed or Company-managed) is selected during scoping based on the team's governance requirements — Team-managed is simpler and recommended for migrations under 500 issues.

Zoho Task Lists map to Jira Components within the target Project. Jira Components provide a shared label for grouping Issues but unlike Zoho Task Lists do not support ordered task enumeration. If the Zoho Task List represents a strict sequence, we map it to a Jira Epic with child Stories instead, or we document the ordering in a Jira Confluence page linked to the Project. The customer chooses the grouping strategy during scoping.

Zoho Tasks map to Jira Issues. Task name becomes Issue Summary; description (rich text) migrates as Jira Description; start/end dates migrate as Due Date and the custom start_date__c field we provision. Status maps from Zoho status (Open, Not Started, Pending, Completed) to Jira status (To Do, In Progress, Done). Assignee maps by email match to Jira User.

Zoho subtasks (2-level nesting maximum) map to Jira Sub-task Issue type. Zoho's parent_task_id reference becomes Jira's Parent Link field. Jira Sub-task Issue type must be enabled in the project's Issue Type scheme before migration; we configure this during Jira project setup.

Zoho Milestones are project-level date-bound targets. Jira has no direct Milestone object — the equivalent is a Jira Version (a release with a target date) or a Label. We map Zoho Milestones to Jira Versions with the Milestone's target date preserved as the Version Release Date. If the Zoho Milestone contains a mixed set of task types, we apply a Label (e.g., milestone_Q3_launch) to all contributing Issues for cross-cutting visibility.

Zoho Issues (Bugs) map to Jira Issue with type Bug. Zoho Issue fields (severity, type, reporter) map to Jira custom fields or standard fields (Priority, Reporter, Labels). Zoho issue status workflow does not migrate — we map to Jira's Bug workflow statuses (Open, In Progress, Done, Closed) during the field mapping phase.

Zoho Timesheet entries (hours, date, user, billing rate, task link) map to Jira Worklog records. Jira Worklog stores timeSpent, started (timestamp), and author. Jira has no native billing rate field; we create a custom field billing_rate__c on the Issue to preserve Zoho's billing information. The Jira user performing the migration must have the Log Work permission on the target project.

Zoho Forums are project-level discussion threads with replies and timestamps. Jira has no Forum equivalent. We export Forum content as structured JSON and deliver it as a Jira Confluence page (preferred, if the customer has Confluence) or as Issue Comments on a designated Discussion Issue. Forum structure (thread vs flat) is preserved in the document format.

Zoho Comments on Tasks, Issues, and Milestones map to Jira Issue Comments. Comment body (rich text) migrates as Jira Comment body; author maps by email match to Jira User; timestamp becomes Jira Comment creation date. Threaded comment structures in Zoho flatten to Jira's flat comment model.

Zoho custom fields on Projects, Tasks, and Issues map to Jira custom fields. We extract custom field definitions from Zoho (field name, type) and create equivalent Jira custom fields before migration. Supported Zoho custom field types (text, number, date, picklist, multi-select) map to Jira Text Field, Number Field, Date Picker, Select (single), and Label or Multi-select. Zoho custom fields not supported by Jira's standard types are stored as Text Field with the raw value preserved.

Zoho Users and Team Members map to Jira Users by email address. We export the full Zoho user list (name, email, role, project-level permissions) and match to Jira users by email. Jira Site Admins must provision any Jira users not already in the destination Jira site before record import proceeds. Zoho project-level permissions do not map directly to Jira project roles — we deliver a permission mapping table for the admin to configure Jira project role memberships post-migration.

Zoho Tags applied to Tasks and Issues map to Jira Labels. Labels are plain-text string fields in Jira. We export the tag name and apply it to the matching Jira Issue. Jira Label naming conventions (no spaces) require us to replace spaces with hyphens or underscores during the tag mapping phase.