Migrate from Teamwork.com to Jira

Teamwork.com Projects map directly to Jira Projects. We preserve project name, description, start and end dates, and status (Active, On Hold, Completed). Project-level custom fields from Teamwork.com migrate to Jira custom fields scoped to the target project. Jira project type (team-managed or company-managed) is determined during scoping; company-managed is recommended for organizations with existing Jira administration governance.

Teamwork.com Tasks map to Jira Issues with the type determined by a scoped rule: tasks with a bug-like label or priority flag map to Jira Bug; tasks linked to a release milestone map to Jira Story; all others map to Jira Task. Assignee, due date, priority (low/normal/high/critical mapping to Jira priority levels), estimated time, and description (as rich text) migrate directly. Task List membership from Teamwork.com becomes a Jira Component or label depending on the customer's naming convention preference.

Teamwork.com Subtasks map to Jira Sub-Task issues linked to their parent Issue via the issuelinks relationship. Each subtask carries its own assignee, due date, status, and estimated time. We extract subtasks as a flat list keyed by parent task ID and reconstruct the hierarchy in Jira using the 'jira_subtask' link type. Note: completing a parent task in Jira does not cascade to subtasks, matching Teamwork.com's non-propagating parent-complete behavior.

Teamwork.com Milestones map to Jira Fix Versions (releases) on the target project. We preserve milestone name, due date, and description. If a Teamwork.com milestone is linked to specific tasks, we record the linked task IDs in a custom Jira field tw_milestone_links__c so that the relationship is queryable post-migration. Milestone color coding has no Jira equivalent and is documented for manual re-creation in project settings.

Teamwork.com Time Entries migrate to Jira Work Logs against their source Issue. Each work log preserves the logged duration (in seconds), the billable flag (mapped to a custom Jira field tw_billable__c), and the time entry date. Hourly rates do not migrate to Jira (no rate field on Work Log); we export the rate data to a CSV delivered alongside the migration for the customer's admin to use in billing reconstruction in an external tool. Project-level time entries without a task anchor are logged against a placeholder 'Project Setup' issue created during migration.

Teamwork.com Users map to Jira Users by email address match. User profile fields (name, email, role) migrate; hourly cost rate from Teamwork.com is written to a custom Jira field tw_hourly_rate__c for reference. Any Teamwork.com user without a matching Jira account goes to a reconciliation queue for the admin to provision before record migration resumes.

Teamwork.com Teams map to Jira Groups. Project-level team permissions are translated to Jira project role assignments during migration. We preserve team membership and document the role each team holds per project so that the customer's Jira admin can assign project roles accordingly. Note: Jira Groups are site-wide, matching Teamwork.com's global Teams concept, but Jira project roles add a second permission scoping layer not present in Teamwork.com.

Teamwork.com Task Comments migrate to Jira Issue Comments with full text, author attribution, and creation timestamp preserved. @mentions in Teamwork.com comments are written as plain text references in Jira (Jira does not support cross-user @mention notifications on imported comments). Comment threading is preserved as sequential comments ordered by timestamp.

Teamwork.com Tags migrate to Jira Labels on the corresponding Issues. Tags are simple string labels with no hierarchy in either platform, making this a direct 1:1 map. We deduplicate tag names during import to avoid Jira's label limit (max 32768 labels per global label list). Customer chooses whether to scope labels globally or per-project during scoping.

Teamwork.com Custom Fields (project-level and site-wide) migrate to Jira Custom Fields scoped to the target project. Dropdown (select) and multi-select custom fields carry their option arrays; we pre-create the Jira custom field options during schema setup so that the enumerated values are valid on import. Text, number, date, and URL custom field types map directly. This mapping requires a Teamwork.com Premium-equivalent plan on the source account; we detect the subscription tier during scoping and flag any custom field definitions that cannot be read via API before migration begins.

Teamwork.com Clients (organizations with associated projects, contacts, and billing rates) have no direct Jira Software equivalent. If the destination includes Jira Service Management, Clients map to Organizations. If the destination is Jira Software only, Clients are documented in a delivered CSV with their associated projects, contact names, and billing rates for manual re-creation or external CRM integration. The customer decides during scoping whether Jira Service Management Organizations are in scope.

Teamwork.com Invoices (generated from billable time entries and expense records) are not migrated to Jira. Jira Software has no invoicing or billing capability. We export invoice headers, line items, payment status, and tax configurations to a structured CSV delivered alongside the migration. The customer imports this into their accounting system (QuickBooks, Xero, NetSuite) or recreates records manually. This is documented explicitly in the migration scope before migration begins.