Migrate from Project Drive to Jira

Project Drive Projects map directly to Jira Projects as the top-level container. We preserve project name, description, status (Active/Archived maps to Jira's Active/Archived), and creation timestamp. Jira project key must be decided before migration — keys are permanent and cannot be changed or reused after creation. We coordinate with the customer's Jira admin to define the key scheme during scoping.

Project Drive Tasks map to Jira Issues. The standard Jira Issue Type (mapped as Story or Task during configuration) carries the task name as Summary, description as Description, assignee as Assignee, start date as Due Date or a custom start field, and status as Status within the configured Workflow. Task priority maps to Jira Priority values (Highest, High, Medium, Low, Lowest). Project Drive's task status values are mapped to Jira workflow statuses during schema configuration.

Project Drive Subtasks nest under Tasks. We map them to Jira Subtask Issue Types with the Jira parent issue as the Parent Link. Jira requires the parent Issue to exist before the Subtask can be created, so we sequence the import: parent issues first, then subtasks. If the destination Jira project uses a simplified Issue Type scheme without Subtask enabled, we convert subtasks to linked Issues with a 'Subtask of' link instead.

Project Drive Milestones are date-flagged markers in the Gantt view. We map them to Jira Fix Versions (Releases) when the milestone represents a deliverable checkpoint, or to Issues with a 'Milestone' label when it represents a tracked goal. The milestone name becomes the Fix Version name, and the milestone date becomes the Fix Version release date. We preserve the milestone relationship to parent tasks via the Fix Version field on the linked Issues.

Project Drive Gantt view displays task dependencies visually, but exported data may flatten these to ordering indices. We reconstruct dependency relationships from the Gantt visual layout and apply them as Jira Issue Links using the appropriate link type (Blocks, Is blocked by, Depends on, Follows, Precedes). Finish-to-Start is the most common; we infer the link direction from the Gantt arrow orientation in the export. We flag any ambiguous dependency directions for customer confirmation during scoping.

Project Drive Users and task assignees map to Jira User accounts by email match. We extract every distinct assignee from the task export and match against the Jira destination site's user list. Assignees without a matching Jira user go to a reconciliation queue for the customer's Jira admin to provision before record import. Jira's permission scheme assigns access per project, so we document the target project permissions per user during scoping.

Project Drive stores budget and cost data as native project fields. Jira has no native financial fields, so we map these to custom Number fields (e.g., Budget_Amount__c, Actual_Cost__c, Estimated_Cost__c) that the customer configures in Jira before migration. We flag null values and discuss whether budget data should live in Jira custom fields, as a linked Confluence financial document, or in a connected finance tool (NetSuite, Everhour, etc.) during scoping.

Project Drive file attachments on tasks and projects are exported as binary file blobs. We upload them to Jira as Issue Attachments using the Jira REST API. Original filename and content type are preserved. Jira imposes a 10MB per-file limit for attachments via the API (larger files require Jira's own upload endpoint). We flag any attachments exceeding this limit for manual handling or alternative storage.

Project Drive integrates with external calendars but does not expose calendar event objects in its export. Jira similarly does not expose calendar event data via its standard export. Calendar sync re-establishes post-migration through Jira's built-in calendar integration or a Marketplace app (e.g., Tempo Calendar or Structure). We do not migrate calendar entries; we flag this gap in the migration scope so the customer can plan re-sync with their calendar provider.

Project Drive project status values (Active, On Hold, Completed, Archived) map directly to Jira Project status. We preserve the status at migration time and note that Jira projects do not have a formal 'On Hold' status — projects are either Active or Archived. Projects on hold in Project Drive can be archived in Jira with a note, or the customer can use a Jira project category to group paused projects.