Migrate from Twproject to Jira

Twproject Projects map to Jira Projects. We use the project name as the Jira Project key prefix base during scoping. Each Twproject project gets a corresponding Jira project with its own default Issue Type Scheme, Workflow Scheme, and Permission Scheme. On-premise Twproject deployments require the customer-provided server URL before project extraction begins; cloud deployments use Twproject's standard API base.

Top-level Twproject tasks that serve as project milestones or phase containers map to Jira Epic issues. The Epic's Summary, Description, Assignee, and Dates (start, due) transfer directly. Epic Link (the relationship that connects Stories and Tasks to an Epic) is established during the child mapping phase.

Twproject child tasks map to Jira issuetypes based on the task's Twproject status and any type indicator. Tasks marked as defects in Twproject become Jira Bugs. Tasks with story-point estimates become Jira Stories. Standalone work items become Jira Tasks. Tasks with a Twproject parent task become Jira Subtasks. Parent-child hierarchy is preserved through Jira's parent-link field.

Twproject's Gantt WBS hierarchy (phases, sub-phases, tasks) maps to Jira Epic at the top level with Stories and Subtasks for deeper nesting. The WBS numbering sequence from Twproject is stored as a custom text field wbs_path__c on each Jira issue so that the original Work Breakdown Structure ordering is preserved and queryable in Jira.

Twproject Resources map to Jira Users. We resolve by email match against the Jira instance's user directory (Atlassian Identity for Cloud, or Jira internal directory for Data Center). Twproject cost rates and department metadata transfer to custom fields on the Jira User record (rate_per_hour__c, department__c) for use in reporting or Tempo Timesheets configuration. Any Twproject Resource without a Jira match enters a reconciliation queue for the customer's admin to provision.

Twproject Worklogs are not included in the JSON project export. We pull them directly from the Twproject API using task ID associations, then write them to Jira as Tempo Timesheets worklogs linked to the corresponding Jira Issue. Date-range scoping is confirmed during discovery. Without Tempo, Jira has no native worklog object to receive this data; we flag Tempo as a required add-on for worklog migration scope.

Twproject cost and budget data (Costs & Revenues section, budget-vs-actual forecasts) are not in the JSON export. We pull them via API and map to Jira custom number fields on the Project or Epic (budget_amount__c, actual_cost__c, forecast_cost__c). Jira has no native cost tracking; the customer decides whether to use these custom fields for reporting or to install Tempo with financial tracking.

Twproject wizard-defined custom fields on tasks and projects are enumerated during discovery via API and mapped to Jira custom fields of equivalent type (text, number, date, select, multi-select). Jira custom field context (project scope) is configured before import. Custom field options (select, radio) migrate as Jira custom field options with the same label-value mapping.

Twproject tags on tasks and projects map to Jira Labels. Labels are a flat string field in Jira — we normalize Twproject's tag list by splitting multi-value tags and inserting each as a separate Jira label. Jira Labels are project-scoped by default but are searchable org-wide.

Twproject's resource workload view (allocation percentages per resource per time period) transfers as a lookup table in a Jira custom object or as Jira custom fields on the User record (allocation_monday__c through allocation_friday__c). For Premium or Enterprise Jira, we can map to Advanced Roadmaps if the customer licenses it; otherwise we document the allocation data in a written inventory for manual entry or third-party app configuration.

Twproject's Kanban is a daily planning view, not a project-level board. Task assignments and statuses migrate to Jira but the Twproject board configuration (columns, swimlanes, card display fields) does not have a direct Jira analog. We document the Twproject column-to-status mapping as a Jira Board configuration guide and the customer's Jira admin sets up the Kanban board post-migration.