Migrate from Celoxis to Asana

Celoxis Projects map to Asana Projects. We preserve project name, description, status (Active/On Hold/Completed maps to Asana's Project color-state or a custom status field), start date, target end date, and custom fields. Celoxis billing type (Fixed Price vs Hourly) and budget amounts are extracted as custom fields in Asana since Asana has no native budget tracking. Portfolio groupings from Celoxis map to Asana Portfolios or to a custom Portfolio section within a Workspace.

Celoxis Tasks map to Asana Tasks, and Celoxis Subtasks map to Asana Subtasks (nested tasks). We preserve parent-child hierarchy, task name, description (rich text), start date, due date, priority, and custom fields. Celoxis split tasks and recurring tasks are mapped to Asana's recurring task feature where the pattern is compatible; non-compatible split task structures are noted and mapped as separate tasks with a shared custom field identifier to preserve the relationship.

Celoxis finish-to-start, start-to-start, finish-to-finish, and start-to-finish dependencies with lead-lag time map to Asana's dependency feature in Timeline view. We reconstruct the dependency graph using Asana's dependencies field (depends_on and blocking). Lead-lag time is stored as a custom numeric field since Asana does not natively support lead-lag offset values on dependencies.

Celoxis multi-baseline snapshots (schedule baseline, cost baseline) have no direct Asana equivalent. We store each baseline snapshot as a set of task-level custom fields (e.g., Baseline Start Date, Baseline End Date, Baseline Duration, Baseline Cost) populated from the Celoxis baseline export. The customer can compare current task dates against baseline fields in Asana but cannot visualize a Gantt overlay of multiple baselines as in Celoxis.

Celoxis Resources (Users) map to Asana Workspace Members. We preserve name, email address, and role. Celoxis cost rate (internal billing) and billing rate (external/client billing) are stored as custom fields on the user's profile record in a connected tool (e.g., a resource management spreadsheet) since Asana does not have native resource cost or billing rate fields. If the customer uses Celoxis Job Roles, we map role names and their default cost rates to a custom Role field on the Asana member.

Celoxis timesheet entries (billable and non-billable) map to Asana time entries logged against tasks. We map hours, date, activity code, and the billable flag. Celoxis timesheet approval workflow status is not exportable and cannot migrate; we note which time entries were in approved, pending, or rejected state at migration time in a custom field for the customer's admin to re-establish. Time-code-level billing rates from Celoxis are preserved as custom fields on the Asana task for post-migration billing calculations.

Celoxis Expense records have no native Asana equivalent. We export expense code, amount, currency, reimbursable flag, and linked project/task. In Asana, we attach this data as a custom object export (CSV or JSON) linked to the relevant Asana project via a project identifier field. The customer can import this into an expense management tool (Expensify, Airbase) or maintain it as a reference spreadsheet. The approval workflow state does not migrate.

Celoxis Risks are a distinct object with severity, probability, mitigation, and owner fields. Asana has no native risk register. We create Asana Tasks under a dedicated Risks section within each project, populating severity as a custom dropdown field (Critical/High/Medium/Low), probability as a custom percentage field, and mitigation as the task description or a linked subtask. Risk status (Open/Mitigated/Closed) maps to Asana task completion state.

Celoxis Issues tracked separately from Risks map to Asana Tasks under a dedicated Issues section within each project. We preserve issue title, description, status, assignee, and linked project context. Issue workflow states (Open/In Progress/Resolved/Closed) map to Asana task completion or a custom status field depending on the customer's preference.

Celoxis custom fields (25-1000 depending on tier) defined on Projects and Tasks map to Asana custom fields. Field name, type (text, number, date, dropdown, checkbox), and options migrate directly. Multi-select dropdown options in Celoxis map to Asana multi-select fields. Custom fields defined on Celoxis Resources map to Asana member custom fields. Celoxis Custom Apps (custom record types) are not an Asana object type; we export the app record data as a separate dataset with a project or task identifier for the customer's admin to re-implement in Asana Forms or a connected database.

Celoxis Portfolios aggregate multiple projects under a strategic grouping. Asana has a Portfolio feature (Premium) that groups projects across teams. We map portfolio membership (which projects belong to which portfolio) to Asana Portfolio membership. Portfolio-level KPIs and aggregated financial views require recalculation in Asana since Asana Portfolios do not store financial data.

Celoxis Job Roles define a role template (e.g., Developer, Designer) with an associated cost rate. We map role name to a custom Role field on Asana Workspace Members. The cost rate associated with each role is preserved in a custom Cost Rate field on the member record or in a linked resource management export. Asana does not natively support role-based cost rates.

Celoxis documents and file attachments linked to projects and tasks migrate as Asana Attachments. We export file references and store the file content in Asana's attachment storage. Celoxis v15 changed document search to index only metadata (name, description) rather than full document body content; we note this change for the customer so they can adjust any search-dependent workflows. Full-text document content is preserved as-is but will not be searchable within Asana.