Migrate your Celoxis data

Projects are the top-level container in Celoxis and carry rich metadata: status, billing type (Fixed Price vs Hourly), budgets, custom fields, and workspace isolation (Data Isolation). We map Projects 1:1 and flag the billing type since destination systems often handle project billing differently.

Tasks support split tasks, recurring tasks, baselines, and task-level budgets. Celoxis v15 added a /v2/tasks/move endpoint to move tasks across projects. We preserve parent-child hierarchy and all dependency links during migration.

Dependencies between tasks are stored as finish-to-start, start-to-start, finish-to-finish, and start-to-finish links with lead-lag time. We reconstruct the full dependency graph in the destination system.

Resources have both a cost rate (internal billing) and a billing rate (external/client billing), either of which can be overridden per project. We map these to the destination's resource cost fields and flag overrides since not all PM tools support per-project rate overrides.

Celoxis supports billable and non-billable time entries, activity codes, and one-click approvals. Timesheet data exports as tabular records but the approval workflow state does not carry over — we note this explicitly so the customer can re-run approvals post-migration.

Expenses include expense codes, reimbursable flags, and approval workflows. We map expense records with their codes and amounts. The approval status is not exportable and must be re-established in the destination.

Multiple baselines are supported per project (unlike some competitors). We capture all baseline snapshots so the customer can compare planned vs. actual performance in the destination.

Risks are a distinct object with severity, probability, and mitigation fields. Risk Management is a paid add-on on lower tiers, so we verify the source account has this feature active before migrating risk records.

Issues are tracked separately from Risks with their own workflow states. We migrate issue records with status, assignee, and linked project context.

Portfolios aggregate multiple projects under a strategic grouping. We map portfolio hierarchy but note that portfolio-level KPIs and aggregated financial views require recalculation in the destination since financial rollup logic differs by platform.

Celoxis allows 25–1000 custom fields depending on the tier. Custom fields can be defined on Projects, Tasks, Resources, and other objects. We export field definitions (name, type, options) and map values by field name to the destination, applying a mapping table where data types differ.

Job Roles define a role template (e.g., 'Developer', 'Designer') with an associated cost rate. We migrate role definitions and their rate assignments.

Documents are attached to projects and tasks. Celoxis v15 changed document search to index only metadata (name, description) rather than full document body content. We export file references and store attachments separately for re-association in the destination.

Dashboards with aggregated project data, charts, and KPIs can be exported to CSV or PDF. We export the report definitions and data. Native dashboard configuration (widgets, layout) cannot be imported into a different platform and must be rebuilt.

Celoxis allows creation of custom apps (custom record types with their own forms, fields, and workflows) on Business and Enterprise tiers. Custom Apps are Celoxis-specific and cannot be migrated directly — they require re-implementation in the destination system.