Migrate from Celoxis to monday Work Management

Celoxis Portfolios aggregate multiple projects under strategic groupings with portfolio-level KPIs and aggregated financial views. monday.com Workspaces sit above Boards as organizational containers and can host related boards for a portfolio. We map the portfolio name to the workspace name and assign relevant boards during migration. Portfolio-level KPIs (aggregated cost, budget variance) require recalculation in monday.com because the platform does not have a native portfolio aggregation engine.

Celoxis Projects map to monday.com Boards. Celoxis project metadata — status, billing type (Fixed Price vs Hourly), start and end dates, budget amounts — maps to custom columns on the board. The Celoxis billing type (Fixed Price or Hourly) becomes a Status Label or a text column on the board. Project custom fields migrate as monday.com custom columns by name with type matching: text to text, number to numbers, date to date, dropdown to labels or dropdown columns.

Celoxis Tasks and Subtasks map to monday.com Items and Sub-items. We preserve parent-child hierarchy by creating sub-items under the parent item. Celoxis task fields (start date, end date, % complete, estimated hours, actual hours) migrate to monday.com date columns, numbers columns, and the built-in progress tracking column. Task-level budgets map to a custom number column.

Celoxis stores FS, FF, SF, and SS dependencies with lead-lag time. monday.com's Dependency column supports only finish-to-start (FS) dependencies natively. We migrate FS dependencies as dependency column links. FF, SF, and SS dependencies are documented in a dependency map delivered alongside the migration and noted as manual rework in monday.com because those dependency types have no native equivalent.

Celoxis supports multiple baselines per project. monday.com has no native baseline concept. We create a custom date column for the baseline start date and a number column for baseline budget or hours, with a text column for baseline name. Each Celoxis baseline snapshot becomes a separate column set (Baseline 1, Baseline 2, etc.) on the board. The customer should note that monday.com cannot automatically compute variance between baselines — this requires a manual report or formula column setup post-migration.

Celoxis Resources have cost rates and billing rates (with project-level and time-code overrides). monday.com uses Person columns that link to workspace members. We map Celoxis Resources to monday.com workspace members by email match. Cost rate and billing rate values migrate as custom number columns on the board (not as a runtime-calculated field, since monday.com does not have a resource cost engine). We flag any Celoxis Resource without an email match for manual user provisioning before migration.

Celoxis Timesheet entries (billable and non-billable time logged against a task with activity codes) map to monday.com's built-in Time Tracking column on Pro and Enterprise plans. Each time entry's hours, date, and billable flag migrate. Note that monday.com's time tracking does not support activity codes or time-code billing rate overrides — these require a custom column or a separate board. Timesheet approval workflows do not migrate; monday.com has no native approval state for time entries.

Celoxis Expenses include expense codes, reimbursable flags, amounts, and approval workflows. monday.com has no native expense module. We create a separate Expenses board with columns for expense code, amount, reimbursable flag, date, and status. Approval workflows require rebuilding in monday.com's Automation Center using status-change triggers. Celoxis expense approval state is not exportable and must be re-established manually.

Celoxis Risks are a distinct object with severity, probability, and mitigation fields. monday.com has no native risk register. We create a Risks board with columns for severity (label or number), probability, mitigation owner (person column), and linked project (board linking column or item name referencing the parent project board). Risk Management is a paid add-on on Celoxis lower tiers; we verify add-on status at scoping before including risk records in the migration scope.

Celoxis Issues are a separate object from Risks with their own workflow states, assignees, and linked project context. We map Issues to a separate Issues board in monday.com mirroring the Risks board structure, with columns for issue title, status, assignee, and linked project board. Issue workflow states require mapping to monday.com status values during scoping.

Celoxis Job Roles define role templates (e.g., Developer, Designer) with an associated cost rate. monday.com does not have a native Job Role concept. We map role definitions to a Roles board or to a text/label column on the resource board. The cost rate associated with each role migrates as a number column. This is a static mapping that requires manual updates if role rates change.

Celoxis allows 25-1000 custom fields per tier on Projects, Tasks, Resources, and other objects. We export field definitions (name, type, options) and map field values to monday.com custom columns by type: text fields to text columns, numbers to number columns, dates to date columns, dropdowns to label or dropdown columns, and multi-select to label columns. Field type matching is performed during scoping; any Celoxis field type without a direct monday.com equivalent is documented for the customer to resolve.

Celoxis Custom Apps (custom record types with their own fields, forms, and workflows, available on Business and Enterprise tiers) cannot be migrated to monday.com. monday.com's Custom Objects feature requires building a custom app via the Developer Center and is not a direct record-type migration target. We export the data stored in custom app records as a CSV during scoping and deliver a field inventory so the customer's developer can rebuild the app structure in monday.com. Custom app workflows are documented separately for rebuild in monday.com's Automation Center.

Celoxis documents are attached to projects and tasks. We migrate file references and metadata (document name, description, upload date) as text columns with a URL placeholder if the files are stored in an external system. monday.com's file attachment column can host uploaded files, but Celoxis file storage cannot be directly accessed. The customer should export documents from Celoxis before migration and re-upload to monday.com or connect via Google Drive, SharePoint, or another integration post-migration.

Celoxis dashboards with aggregated project data, charts, and KPIs export as data snapshots in CSV or PDF. We export the report definitions and underlying data so the customer can rebuild visualizations in monday.com Dashboards. Native widget configuration (chart types, layout, filters) cannot be imported. monday.com dashboards are separate from boards and support chart widgets, number widgets, and timer widgets, but the customer must rebuild the dashboard layout from the exported data.