Migrate from Worksection to Jira

Worksection Projects map directly to Jira Projects. Each Worksection project name becomes a Jira project name, and Worksection project-level custom fields (created via Administration) map to Jira custom fields scoped per project. Jira project type selection (Jira Software vs Jira Work Management) is made during scoping based on whether the team uses sprints, epics, and story points — Software — or general task management — Work Management.

Worksection Tasks map to Jira Issues. Task title maps to Summary, description maps to Description (migrated as Jira's rich-text format), assignee maps to Assignee via email resolution, due date maps to Due Date, and priority maps to Priority (Critical/High/Medium/Low). Status mapping depends on the target Jira project's workflow — we configure the transition states during Jira project setup before migration begins.

Worksection Subtasks inherit their parent Task and migrate as Jira Subtasks under the parent Issue. We preserve the parent-child relationship by setting the Parent Issue key on each Jira Subtask during import. Jira Subtasks have a fixed single-parent structure matching Worksection's single-level subtask nesting — deeper nested subtasks in Worksection require flattening into Jira's structure.

Worksection time entries with hours and descriptions map to Jira's Time Tracking fields (Time Spent and Original Estimate). Worksection's hourly rate does not map to a Jira field — Jira has no native billing or rate feature. We store the Worksection cost value as a custom field worksection_cost__c on the Jira Issue and document the rate configuration in the migration handoff for the customer to reconcile in an external billing tool if required.

Worksection task-level comments migrate as Jira Issue Comments with author attribution (display name from Worksection member record) and timestamp preserved. Threaded discussions are flattened into Jira's chronological comment structure since Jira does not natively support nested reply threads. Author attribution relies on email matching between Worksection member records and Jira user accounts.

File attachments on Worksection Tasks and Projects migrate as Jira Issue Attachments. We resolve FTP-linked files and Google Drive references to physical files during extraction and attach them to the corresponding Jira Issue during import. Jira's attachment size limits (10MB per file on most plans) apply — files exceeding this are flagged for the customer to host externally and link.

Worksection task labels migrate to Jira Labels as a straightforward 1:1 mapping. Stage tags migrate to Jira Labels or Components depending on the customer's preference — Labels are simpler for categorization, Components are better if the team wants to group issues by deliverable or service area. The customer chooses during scoping.

Worksection member accounts (name, email, role) map to Jira User accounts via email resolution. We run owner resolution before record import so that every Worksection assignee and commenter has a corresponding Jira user account. Members without a Jira account go to a reconciliation queue for the customer's admin to provision before migration resumes.

Worksection team structures migrate to Jira Groups or Project Roles depending on the destination Jira Cloud plan. Groups are simpler and available on all plans; Project Roles offer finer-grained permission scoping on Business and Enterprise plans. If Worksection teams map to Jira projects 1:1, we recommend using Jira project membership rather than groups.

Worksection custom fields created per-project via Administration map to Jira custom fields. Since Worksection allows per-project custom field schemas, we audit each Worksection project's field definitions and create matching Jira custom fields per project. Field types are mapped: text to Jira Text Field, number to Number Field, date to Date Picker, dropdown to Jira Select List. Custom field configuration is completed in the Jira project setup phase before record import.

Worksection task dependencies visible in the Gantt chart migrate as Jira Issue Links (Blocks / Blocked By / Depends On link types). We parse the Worksection dependency export and recreate the relationships in Jira. Note: Worksection stage-to-stage 'next stage' linking does not migrate and is dropped by Worksection's own import logic — we document the gap and recommend recreating stage flow as Jira workflow transitions post-migration.