Migrate from Celoxis to Jira

Celoxis Projects map to Jira Projects. Each Celoxis project carries status, billing type (Fixed Price vs Hourly), budgets, and custom fields. Jira Projects contain Issues organized by type. We create Jira Projects using the Jira REST API, map Celoxis project status to Jira project key, and preserve the project description and custom field values as Jira issue fields or project properties. Celoxis workspace isolation (Data Isolation on Enterprise) maps to separate Jira Cloud sites or Data Center instances if the customer requires hard data separation.

Celoxis Tasks map to Jira Issues by type. Celoxis parent-child task hierarchy maps to Jira Issue hierarchy using the parent link field. Celoxis split tasks and recurring tasks do not have native Jira equivalents; we flatten split tasks into individual Jira Issues and document the recurrence pattern for manual sprint planning. Celoxis v15 added /v2/tasks/move for cross-project moves; we use Jira bulk move operations with the same cross-project resolution. Task-level budgets from Celoxis are flagged as no native Jira equivalent.

Celoxis finish-to-start, start-to-start, finish-to-finish, and start-to-finish dependencies with lead-lag time map to Jira Issue Links. We reconstruct the full dependency graph in the destination Jira project using the Jira Issue Links API. Lead-lag time is stored as a custom field on the link because Jira's native blocking links do not support lead-lag natively; the customer should review whether the lag field is needed for sprint planning or whether standard blocking links suffice.

Celoxis Resources with cost rates and billing rates map to Jira Users. The Celoxis resource cost rate (internal) maps to a custom User field (eg, cost_rate__c) and the billing rate (external/client) maps to a separate custom field (billing_rate__c) because Jira has no native billing rate concept. Resource allocation percentages from Celoxis workload views map to Jira Project Role assignments and, if Jira Software Premium is used, to the capacity planning feature. Celoxis Job Roles (role templates with cost rates) map to Jira Project Roles for reuse across projects.

Celoxis timesheet entries (billable and non-billable time with activity codes) map to Jira Issue worklogs. Each Celoxis timesheet entry linked to a task maps to a Jira Issue worklog record with the time spent, author (mapped to Jira User), and date preserved. Celoxis timesheet approval workflow state does not carry over. Activity codes from Celoxis map to Jira Worklog properties or a custom field; the customer should decide whether activity code reporting requires a companion app (eg, Tempo Timesheets) post-migration.

Celoxis Expense records (expense codes, reimbursable flags, amounts) map to Jira Issue worklogs with a custom expense_amount__c field, expense_code__c field, and a reimbursable__c checkbox. Approval workflows do not migrate. If Jira Service Management is also in scope, expenses may map to Request Subtasks or a custom Request Type instead. The customer chooses the expense representation during scoping based on their Jira product mix.

Celoxis multiple named baselines per project have no native Jira equivalent. Jira does not support multi-baseline scheduling. We export all Celoxis baseline snapshots as a written report (project name, baseline date, task schedule snapshot, task cost snapshot) and the customer recreates scope snapshots manually in Jira using Labels (tagging issues in scope) or Fix Versions (milestones). Baselines are a high-priority manual rebuild item for projects with contractual schedule obligations.

Celoxis Risk records (severity, probability, mitigation fields) map to Jira Issues using a custom Issue Type (Risk) if the customer configures one, or using a standard Issue Type with a risk_priority__c, probability__c, and mitigation__c set of custom fields. Risk Management is a paid add-on in Celoxis; we verify it is active during scoping before including Risk records in the migration scope. Jira has no native Risk object type; the custom Issue Type approach is the closest equivalent.

Celoxis Issues (separate from Risks) with their own workflow states map to Jira Issues using a standard Issue Type (Bug or Task) with the Celoxis issue status mapped to Jira status via a status mapping table. Assignee, description, and linked project context transfer directly.

Celoxis Portfolios aggregate multiple projects under strategic groupings with aggregated KPIs and financial views. Jira Software Premium offers Advanced Roadmaps for cross-project planning. Standard Jira (without Premium) does not have native portfolio management. We map portfolio hierarchy as a Jira project hierarchy (using Project Links or a naming convention) and document the portfolio-level KPIs that require recalculation in Jira or a reporting tool. If the customer uses Jira Product Discovery, that tool can replace Celoxis Portfolio views.

Celoxis custom fields (25-1000 depending on tier) on Projects, Tasks, Resources, and other objects map to Jira custom fields. We map text, number, picklist, multi-select picklist, date, currency, formula, and file attachment field types to their Jira equivalents. Celoxis rollup fields (sum, average, min, max of numeric fields rolled up to summary tasks) do not have a native Jira equivalent; Jira's issue hierarchy and aggregations are more limited. We flag rollup fields for manual configuration in Jira or a companion app.

Celoxis Custom Apps (custom record types with their own fields, forms, and workflows) on Business and Enterprise tiers cannot be migrated. We export the data stored in custom app records as a structured CSV/JSON with field definitions, and we deliver a written field inventory listing each custom app's record structure, field types, and options. The customer's admin rebuilds the app definition in Jira (as custom Issue Types and custom fields) or a complementary tool. Custom App workflows do not migrate.