Migrate from Antura to Jira

Antura Projects map to Jira Projects as the top-level container. Project name, description, status, start date, and target end date migrate directly. Antura project status (Active, On Hold, Completed, Cancelled) maps to Jira Project's archived state or a custom status field depending on the destination Jira edition. We create Jira Projects via the Jira API before issue import begins, using the Jira project key as the identifier for all child record references.

Antura Sub-projects nest under parent Projects and inherit portfolio-level metadata. Jira does not have a native Sub-project concept; we map Antura Sub-projects to Jira Epics within the target Project. The Epic Name and Description map from the Sub-project name and description. We preserve the parent-child relationship by setting the Epic Link on any migrated Stories or Tasks that should belong to the Sub-project, and we flag which Sub-projects lack child tasks so the customer can decide whether to create standalone Epics or restructure before import.

Antura Tasks map to Jira Issues with the Jira issue type determined by the customer during scoping. Standard Antura work items become Jira Stories or Tasks; Antura Tasks marked with a bug indicator become Jira Bugs. Antura task assignee, due date, status, and description migrate directly. Antura's flat task structure means we set no parent Issue on migrated records unless the customer specifies a grouping rule (for example, grouping by project phase or Antura Sub-project). The customer chooses the grouping strategy during scoping because Jira's hierarchy requires an explicit parent-child decision.

Antura Milestones are date-driven markers within Projects. Jira uses Fix Version (associated with an issue's release) and Component (grouping within a project) to represent milestones. We map Antura Milestone dates and names to Jira Fix Version records created under the target Project, and we link migrated Issues to the relevant Fix Version based on the Milestone assignment in Antura. The customer chooses between Fix Version and Component during scoping based on their Jira release management process.

Antura Resources represent employees with capacity data, skills, and cost rates. Jira does not have a native Resource object; Jira manages assignments through User provisioning and, at Premium and Enterprise tiers, through Jira Software's capacity planning. We extract Antura Resource names and email addresses, resolve them against the destination Jira site's User table by email match, and flag any Antura Resources without a corresponding Jira User for the customer's admin to provision. Capacity and utilization percentages from Antura migrate as custom fields on the User record or as a separate reporting spreadsheet for the customer's resource manager to reconcile post-migration.

Antura tracks Risks (probability, impact, mitigation) and Issues (severity, owner, status) as separate objects. Jira does not have a native Risk issue type in core Software; customers either use a custom Risk Issue type, Jira's native Issue type with a Risk category, or Jira Align for formal risk management. We map Risk probability and impact fields to Jira custom fields, map Risk mitigation to the Issue Description or a custom mitigation field, and map Issue severity to a Jira Priority value. The customer chooses the risk representation strategy during scoping.

Antura Cost Records include estimates, budgets, actuals, and forecasts per Project. Jira Software core does not have native financial fields. We map cost data to Jira custom number fields (Budget Estimate, Actual Cost, Forecast) on the Jira Project or Epic level. For Jira Premium and Enterprise customers, we map to Jira's built-in capacity and estimation fields. The customer decides whether cost data lives on Project metadata, Epic metadata, or Story-level estimation fields during scoping. Multi-currency handling requires the customer to configure Jira's currency field or document exchange rates at migration time.

Antura Time Entries record hours spent by Resources on Tasks or Projects with date and description. Jira Worklog tracks time spent on Issues with author, date, duration, and comment. We map Antura Time Entry hours to Jira Worklog entries linked to the corresponding Jira Issue. The Jira Worklog author resolves by matching the Antura Resource email to the Jira User. If the customer requires billing rate preservation, we map the Antura cost rate to a custom Worklog field since Jira does not support per-entry billing rates without a third-party app.

Antura Documents attach to Projects and Sub-projects as binary files. We extract document metadata (filename, type, date, owner) from the Antura export and map it to Jira Issue Attachment metadata at the target Project level. The actual file binaries require a separate file-transfer process using Antura's document export feature to a shared location, followed by manual reattachment in Jira. We flag this upfront and recommend running the parallel file transfer during the scoping phase so that binaries are staged before cutover. Jira's 10MB per-attachment limit and 256GB storage cap require the customer to verify their Jira Cloud storage allocation or Jira Data Center storage volume before file transfer begins.

Antura supports organization-specific custom fields across Projects, Tasks, and Resources with no public metadata API for schema discovery. We conduct a manual schema discovery phase where we export a full field inventory from the customer's Antura instance through the admin interface, identify all active custom fields per object, and map each to a corresponding Jira Custom Field with the appropriate Jira field type (text, number, date, picker, checkbox, radio, cascading select). Jira custom fields require context configuration (which issue types and projects the field applies to); we configure this during the Jira destination setup phase. The customer validates the custom field mapping during UAT before production import.

Antura Portfolio groups Projects for strategic oversight with priority, status, and strategic alignment fields. Jira Advanced Roadmaps (a paid add-on for Jira Software Premium and Enterprise) provides cross-project planning with team capacity and dependencies. Jira Align offers portfolio-level planning as a separate product. We map Antura Portfolio membership and priority to Jira Advanced Roadmaps plans or, for customers without Advanced Roadmaps, to a Jira project designated as a Program with links to child Projects. We flag that strategic alignment fields require customer-defined custom fields in Jira since no native equivalent exists.