Migrate from TeamWork Live to Jira

TeamWork Live Projects map directly to Jira Projects. The project name, description, status (active/archived), start date, and due date migrate as Project metadata. Project-level client linkage from TeamWork Live does not have a direct Jira equivalent; we map client-linked projects to Jira Projects with a label identifying the client, or recommend Jira Service Management for client-facing project management use cases. Project key (the Jira project prefix) is auto-generated or customer-specified during provisioning.

TeamWork Live Tasks map to Jira Issues with the issue type determined during scoping. Tasks marked as bugs or defects in TeamWork Live map to Jira Bug issue type. Standard work tasks map to Jira Task. Tasks representing deliverable work items from an agile backlog map to Jira Story. The task title, description, status, priority, assignee, and due date migrate directly. Jira's Assignee field resolves to the User mapped from TeamWork Live by email match.

TeamWork Live Task Lists within a Project map to Jira Components. Component names preserve the Task List name. Components provide a grouping mechanism in Jira that mirrors Task List organization. If Task Lists are used for categorization rather than grouping (for example, tagging tasks by work type), we may instead map Task List names to Jira Labels. The customer chooses the grouping strategy during scoping based on how Task Lists are used in the source account.

TeamWork Live Milestones map to Jira Fix Versions with the milestone name as the version name and the target date as the release date. TeamWork Live milestones that have an associated completion date are flagged separately; we create a corresponding Fix Version with a released status in Jira. Milestones without a due date are created as unreleased versions. The project association maps directly.

TeamWork Live Users map to Jira Users by email address as the deduplication key. Active and inactive status is preserved. Guest or client-level users from TeamWork Live are held in a reconciliation queue because Jira Software does not have a native guest user concept at the project level; these users may require manual provisioning or a separate Jira Service Management customer account if client access is required in the destination.

TeamWork Live Time Entries map to Jira Issue Worklogs with the hours logged, date, and optional notes preserved. The primary schema gap is the billable/non-billable flag: TeamWork Live marks time entries as billable for client invoicing, but Jira worklogs have no native billing flag. We preserve the billable flag value in a custom field twl_billable__c on the Jira Issue and flag it for the customer's admin to map to their invoicing workflow post-migration. Hourly rate overrides from TeamWork Live are held as a separate mapping note for the customer's finance team.

TeamWork Live Comments attached to tasks migrate as Jira Issue Comments with the comment text, author (resolved by email to Jira User), and timestamp preserved. Rich-text formatting in TeamWork Live comments may not round-trip cleanly; HTML-heavy comments are flagged for manual review post-migration or cleaned to plain text during import.

TeamWork Live project-level custom fields (text, number, dropdown) map to Jira Project-level custom fields. We pre-create the destination custom fields in Jira with the correct field type (text, number, select, multi-select) before migration. Dropdown option lists from TeamWork Live must be manually recreated in Jira's field configuration as Jira does not support programmatic option creation via the REST API. This is documented in the migration scope as a pre-migration admin task.

TeamWork Live task-level custom fields map to Jira Issue-level custom fields with the same type mapping. Text fields become Jira Text Field (single-line) or Text Area (multi-line) depending on the expected content length. Number fields map to Jira Number Field. Dropdown fields map to Jira Select Field with options recreated in Jira field configuration. Custom field data is only available if the source TeamWork Live account is on a Premium plan or above; custom fields do not exist in lower-tier accounts.

TeamWork Live Tags applied to tasks or projects migrate as Jira Labels. Labels are stored as string arrays and map directly to Jira's label field. Jira Labels have a 255-character limit per label; tags exceeding this limit are truncated or flagged for renaming. Jira Labels do not support hierarchical tagging, so any tag categorization logic from TeamWork Live must be redesigned in Jira using components or custom fields.

TeamWork Live Companies linked to projects for client access and billing tracking do not have a direct Jira equivalent in Jira Software. We map company names to Jira Project Labels with a client: prefix, or recommend Jira Service Management if the client-facing project management use case is central to the migration. Project-level client permissions from TeamWork Live cannot migrate to Jira Software's permission scheme without redesign; we document the current permission structure as a written inventory for the customer's admin to rebuild.