Migrate from Planview ProjectPlace to Jira

Planview Workspaces map directly to Jira Projects. The Workspace name becomes the Jira Project name; Workspace description migrates as the Jira Project description. Workspace-level member lists map to Jira project role membership (Administrators, Developers, Users). We configure the Jira project type (Team-managed or Company-managed) during migration based on the customer's existing Jira maturity. If the customer has an existing Jira instance, we map Workspace to an existing Jira Project or create new Projects as needed.

Planview Tasks map to Jira Issue types based on a type-mapping rule defined during scoping. Typical mappings: Planview tasks with no children map to Jira Story or Task; tasks with sub-tasks map to Jira Epic with child Stories; bug-type tasks map to Jira Bug. The mapping rule is applied as a transform during migration. Jira's Epic Link custom field holds the parent Epic reference for Story-type Issues. Sub-tasks in Planview map to Jira Sub-task Issues under the parent Story.

Planview Kanban boards map to Jira Kanban boards scoped to the target Jira Project. Board column names from Planview map to Jira status categories (To Do, In Progress, Done) with column-specific status values. Card assignments and card-level metadata (priority, labels, assignee) migrate as Jira Issue fields. Note that Planview's cross-board card connections (cards linked across multiple boards for value stream visibility) cannot be replicated natively in Jira; we document these as Issue Link pairs for the customer to create manually post-migration.

Planview Milestones map to Jira Fix Version (Release) records attached to the target Project. The milestone name becomes the Version name; the milestone due date becomes the Version release date. Planview milestones linked to multiple tasks are resolved by associating the Fix Version with all child Issues. This approach freezes the milestone date against Planview's automatic date recalculation behavior, giving the customer a stable release target in Jira. If Planview milestone descriptions exist, they migrate as Version description.

Planview's Gantt dependency tree (Finish-to-Start, Start-to-Start, Finish-to-Finish, Start-to-Finish) maps to Jira Issue Link types (Blocks, is blocked by, Depends on, is depended on by). We preserve the dependency direction as the Jira link type so that the relationship semantics carry forward. Note that Jira does not natively support Start-to-Start or Finish-to-Finish dependencies; these map to Blocks links with a note in the issue description. Jira Premium's native Gantt view in Jira Software Data Center and Jira (Data Center 9.12+) renders these links visually.

Planview time entries (hours logged, date, user attribution, task reference) map to Jira Issue Work Logs. The Planview hours logged become Jira Worklog timeSpent; the Planview entry date becomes Jira Worklog started. User attribution maps via email-based user resolution to Jira User accounts. Time reporting aggregations (by project, by user, by date range) are not exported from Planview and must be rebuilt in Jira using native reports or a time-tracking add-on.

Planview user accounts map to Jira user accounts via email address resolution. User name, email, and avatar display as the Jira User profile. Workspace role membership maps to Jira project role membership. Role-based permissions (Admin, Member, Guest) in Planview require manual rebuild in Jira's permission scheme per project. Active and inactive user states are preserved; inactive users are provisioned in Jira as inactive accounts if historical attribution must be maintained.

Planview custom fields scoped to each Workspace map to Jira custom fields scoped to the corresponding Jira Project. We query the full Planview API surface (bypassing the OTB sync) to extract all custom field values. Field types map as follows: text fields to Jira Text Field (single-line), long text to Jira Text Field (multi-line), number fields to Jira Number Field, date fields to Jira Date Picker, dropdown fields to Jira Select List (single choice), checkbox fields to Jira Checkboxes (multi-select). Custom field context is set to the target Jira Project only.

Planview task comments and board discussions map to Jira Issue Comments. Comment text, author (resolved via email to Jira User), and timestamp (created date) migrate. Nested reply threads in Planview flatten to a single chronological comment list on the Jira Issue. @mention formatting is stripped during migration and noted in the reconciliation report for manual reconstruction if the customer chooses.

Planview document metadata (filename, uploader, upload date, URL) migrates as a Jira Issue Attachment reference or as a Confluence Page attachment. Binary file blobs require a separate parallel transfer step orchestrated alongside the data migration. We catalog all document references during the schema scan, validate file URL accessibility, and flag any orphaned documents (URLs that return 404) before the migration window. Full document version history does not migrate.

Planview Agile sprints map to Jira Sprints within the target Scrum board. Sprint name, start date, end date, and board assignment migrate. Burndown data, velocity metrics, and sprint commitment statistics are not exported from Planview; Jira recalculates these from Issue data post-migration. Backlog items in Planview migrate as Issues in the Jira backlog (ranked using Jira's ranking mechanism).