Migrate from Genius Project to Jira

Genius Project records map to Jira Projects. Each Project becomes a Jira Project with the Genius Project name preserved. The Jira Project key is derived from the source project name abbreviation (up to 5 characters, uppercase). We create Projects before any Issues to satisfy the Project key dependency on Issue creation.

Genius Project tasks map to Jira Issues. We use Jira Issue Type to represent task hierarchy: top-level tasks become Stories, sub-tasks with no children become Tasks, and tasks with sub-tasks become either Stories with linked Sub-Tasks or Tasks with linked Sub-Tasks depending on the customer's naming convention. Parent-child relationships are preserved via Jira's Parent link field or Epic-Story link.

Genius Project subtasks map to Jira Sub-Tasks linked to their parent Issue. The subtask fields (assignee, dates, effort) transfer directly. Subtask hierarchy in Genius Project is flattened; multi-level subtask nesting in Genius Project creates a chain of linked Sub-Tasks in Jira.

Genius Project Resources (users, equipment, or roles) with user type map to Jira Users. We resolve by email match. Equipment and role-type resources are mapped to Jira Labels or Component Assignees rather than Users since Jira does not have a native equipment resource object. Owners without Jira accounts are held in a reconciliation queue for the customer to provision before record import.

Genius Project portfolios that contain multiple projects map to a Jira Project hierarchy or a Jira Portfolio (Advanced) group. We flatten the portfolio-project membership into the destination and document the portfolio name as a custom field (genius_portfolio__c) on each Jira Project for reporting. If the customer has Jira Portfolio (Advanced), we create hierarchical groups; otherwise we use Labels or a custom multi-select field.

Stage-Gate stage names and order from Genius Project map to a Jira custom picklist field (stage_name__c) on the Project or Epic level. The governance workflow logic, approval gates, and conditional routing in Genius Project have no Jira equivalent and are not migrated. We preserve stage name, stage order, and any stage-level notes as custom field values and deliver a written guide for recreating gate notifications in Jira automations or third-party apps.

Genius Project Cost Plan line items (planned cost, actual cost, variance) are aggregated per project and mapped to Jira custom number fields (budget_planned__c, budget_actual__c, budget_variance__c) on the Project. Jira does not have a native budget object; for complex financial tracking the customer needs a third-party app from the Atlassian Marketplace. We flag this gap during scoping and the customer decides whether Jira's custom fields are sufficient or a budget app is required.

CapEx investment records track capital expenditure approvals and tracking at the portfolio or project level in Genius Project. We map CapEx fields (investment amount, approval status, funding source) to Jira Project-level custom fields. These are not Jira-native financial objects; the customer should verify that Jira's custom field capacity and the chosen Jira plan support the number of custom fields required.

Resource capacity data (available hours, utilization percentages, allocation by time period) is exported as time-series records and mapped to Jira Resource Management if the customer has Jira Premium or Enterprise. If Jira Free or Standard is the destination, capacity data is preserved as a CSV export alongside the migration for reference. Resource Management requires explicit provisioning by the customer's Jira admin before capacity records can be created.

Genius Project custom fields (organization-specific properties on Projects, Tasks, and Resources) are discovered via export metadata during scoping and mapped to Jira custom fields of equivalent type. Text to text, number to number, date to date, picklist to picklist. Multi-select picklists in Genius Project map to Jira multi-select custom fields. Custom fields that reference non-migrated objects (e.g., a Cost Plan lookup) are flagged and resolved with the customer before import.

Documents attached to Projects or Tasks in Genius Project are exported as file references with filename, type, and linked entity. We preserve attachment metadata and either redirect file URLs to a temporary location during migration or provide a file remapping guide. Jira attachments require the files to be accessible by the Jira instance; we flag any attachments exceeding Jira's 10MB per-file limit before migration.