Migrate from Workzone to Jira

Workzone Workspaces map to Jira Projects as top-level containers. Starter plans are limited to 3 workspaces; Team and Enterprise are unlimited. We assess workspace count during scoping and flag any Starter-plan migrations that approach or exceed the 3-workspace cap, as archived workspaces may contain projects that cannot migrate. Each Jira Project requires a Project Key (prefix) that we generate from the workspace name during import.

Workzone Projects live inside Workspaces and contain tasks, attachments, and metadata. We export project status, date range, and custom field values (if the add-on is active). Jira Projects are the destination; we create them in Jira first so that child task imports have a parent reference. Project-level permissions in Workzone map to Jira Project Role memberships in the destination.

Workzone Tasks map to Jira Issues. The mapping type (Story versus Task) depends on the customer's Jira project configuration: we use Story for deliverables with acceptance criteria and Task for work items. Standard fields migrate directly: summary, description, assignee, reporter, due date, priority, and status. Workzone task dependencies migrate to Jira Issue Links (Blocks/Is Blocked by) or to the parent-child relationship if the dependency is a subtask.

Workzone Subtasks nest inside Tasks and inherit parent context. Jira Sub-Tasks are a distinct issue type linked to a parent Story or Task. We preserve the full parent-child hierarchy and ensure that subtask assignees and due dates are retained on the Jira Sub-Task record. Subtask descriptions migrate as the subtask's description field.

Custom fields are a paid add-on in Workzone, so we first verify the plan tier during scoping. If custom fields exist, we map Workzone field types (text, number, date, choice list) to Jira custom field types. Jira requires custom fields to be assigned to specific issue type contexts before they accept values during import; we pre-create the Jira custom fields with correct contexts before data migration begins.

Files attached to Workzone tasks and projects are downloaded and re-uploaded to Jira. Workzone's Team tier includes 500 GB storage; Starter includes 250 GB. Jira Cloud attachments upload via the REST API using multipart form data. Large files (>10 MB per file, Jira's limit) require chunking or alternative upload methods. We preserve original filenames, upload timestamps, and author information.

Time tracking is included in Workzone Team and Enterprise plans but is limited on Starter. Jira includes time tracking (Log Work) on all Jira Software and Jira tiers. We map logged hours to Jira Worklog records, preserving the associated issue, user, time spent, and date. Workzone's billable/non-billable flag maps to a Jira custom worklog field if the customer requires billable tracking in Jira.

Document approvals are a Workzone Team-tier feature. We export approval records including approver identity, approval status, timestamps, and comments. Jira has no native approval workflow as a migratable object, so we map approval data to Jira Comments with the approver name and status prefixed in the comment body, and we recommend the customer implement Jira automation or a third-party approval app post-migration.

Workzone task-level comments and threaded replies export with author, timestamp, and content. Mentions and @-references are preserved as plain text. We map comments to Jira Issue Comments with the original timestamp and author preserved. Threaded discussions in Workzone map to Jira comments in chronological order; Jira does not natively support threaded comments without a marketplace app.

Workzone tags are lightweight labels applied to tasks and projects. Jira uses Labels (comma-separated) as the equivalent field. Multi-value tag arrays in Workzone map to Jira Labels with the original tag names preserved. We flag any tag-to-category mapping discrepancies during scoping if the customer's tagging taxonomy is complex.

Workzone distinguishes between full seat users (creators, project managers) and unlimited collaborators (reviewers, guests). We export both roles separately. Jira charges per user, so we compare the total distinct Workzone user population (full seats plus collaborators) against the destination Jira site's seat count. Any excess requires the customer to purchase additional Jira seats or convert collaborators to free-tier external users before migration.

Workzone supports reusable project templates at the workspace level on Team and Enterprise tiers. We export template structure including task scaffolding and default assignees. Jira's Next-gen projects use simplified templates; classic Jira projects use shared configurations. We document the Workzone template structure in a written handoff document so the customer's admin can seed Jira projects from the documented template scaffold. Templates do not migrate as deployable configuration.