Migrate from Celoxis to Trello

Celoxis Projects map directly to Trello Boards. Project name, description, start date, and target date migrate to Board name, Board description, and the first Card's due date for date anchoring. Celoxis Data Isolation workspaces map to separate Trello workspaces if the source account uses Celoxis Enterprise multi-workspace mode. Celoxis sub-projects map to child Boards via Trello Board Links Power-Up or a parent Board with a sub-Board list, depending on complexity at scoping.

Celoxis Tasks map to Trello Cards. Celoxis subtasks map to child Cards in the same Board or to checklist items within the parent Card — we determine the preferred strategy during scoping based on subtask depth. Celoxis task status (Not Started, In Progress, Completed) maps to Trello List position (To Do, Doing, Done) with a default three-list structure, customizable per Board. Celoxis split tasks and recurring tasks are noted separately as they have no Trello native equivalent and require manual rebuild if critical.

Celoxis finish-to-start, start-to-start, finish-to-finish, and start-to-finish task dependencies map to Trello Card Dependencies Power-Up (Atlassian-native) which supports blocking and blocking-with-date propagation. We reconstruct the dependency graph from Celoxis and configure the Power-Up relationships during migration. Lead-lag time is preserved in the dependency notes field since Trello does not natively support lead-lag. Celoxis critical path data is noted in a separate document for the customer admin to re-establish using Trello Timeline Power-Up if needed.

Celoxis Resources map to Trello Board Members. We resolve Celoxis users by email address and invite them to the corresponding Trello Board. Celoxis resource cost rates and billing rates have no Trello equivalent and are not mapped. Job Roles (role templates with associated cost rates) do not migrate; we deliver a role inventory for the customer admin to document outside Trello. Any Celoxis Resource not matched to a Trello user goes to the reconciliation queue.

Celoxis custom fields defined on Projects and Tasks map to Trello Custom Fields Power-Up on each Board. We match by name and map Celoxis field types (text, number, date, dropdown, checkbox, user reference) to Trello Custom Field types. Celoxis allows 25–1,000 custom fields depending on tier; Trello custom fields are per-card, not per-board, so the customer admin may need to choose which fields apply per-card during configuration. Custom fields defined on Celoxis Resources are not migrated as Trello has no resource-level custom field concept.

Celoxis project and task attachments migrate to Trello Card Attachments. We extract the file URL or binary from Celoxis and attach it to the corresponding Card. Celoxis document metadata (name, description, upload date, uploader) migrates as card attachment metadata. Celoxis v15 note: document body full-text search was removed; Trello card attachments are stored as-is without indexing. If the customer relies on document content search, we flag this gap and recommend a Trello-integrated search tool (Confluence, Google Drive) post-migration.

Celoxis Issues (separate from Risks) with status, assignee, and linked project map to Trello Cards with a dedicated Issue label. We preserve the Celoxis issue description, priority, and status as card description and Trello label color. Issue workflow states (Open, In Progress, Resolved, Closed) map to List position or label subsets depending on the source workflow complexity.

Celoxis Portfolios group multiple Projects under a strategic hierarchy. These map to Trello Workspaces (Enterprise tier) or a Board group with a naming convention (Portfolio-Project). Portfolio-level KPIs, aggregated financial views, and cross-project resource utilization do not migrate — Trello has no portfolio aggregation concept. We document the portfolio hierarchy as a reference map for the customer admin to recreate manually in Trello if required.

Celoxis Timesheet records (billable and non-billable time entries with activity codes and approval states) do not migrate. Trello has no timesheet module. Timesheet data is exported to CSV as a reference document for the customer admin to import into a separate time-tracking tool (Toggl, Harvest, or a native Trello Power-Up) if needed. The Celoxis Professional plan includes Timesheet as a standard feature; this object exists in most Celoxis Professional and Business accounts. We verify Timesheet add-on status at scoping.

Celoxis Expense records (with expense codes, reimbursable flags, and approval workflows) do not migrate. Trello has no expense tracking capability. We export expense records to CSV with codes, amounts, and reimbursable status as a reference for the customer admin. The approval workflow state is not exportable and must be re-established in the destination tool.

Celoxis multiple baselines per project (unique among PM tools) do not migrate. Trello has no baseline concept. We capture all baseline snapshots as a JSON reference file so the customer can compare planned vs. actual performance outside Trello. If baseline comparison is required post-migration, we recommend a Trello-integrated reporting tool (Power-Ups or a data warehouse export).

Celoxis Risks with severity, probability, and mitigation fields migrate to Trello Cards with a dedicated Risk label. Risk Management is a paid add-on at +$5 per user per month on Celoxis Professional; we verify add-on status at scoping and adjust migration object list accordingly. If active, we preserve risk severity and probability as Trello label colors and custom field dropdowns on the Risk card. Risks without the add-on do not exist in the source account.

Celoxis aggregated dashboards, cross-project KPIs, and financial reports do not migrate. Trello does not support native cross-board reporting dashboards (Power-Ups like Blue Cat Reports offer basic visualization, but native dashboards are not part of the core product). We export report data to CSV and deliver a report inventory with field definitions and row counts. Dashboard widget configuration (layout, chart types, date ranges) cannot be imported and must be rebuilt in Trello Power-Ups or an external reporting tool.

Celoxis Custom Apps (custom record types with their own fields, forms, and workflows, available on Business and Enterprise tiers) do not migrate. We export the data stored in custom app records as a flat CSV but cannot transfer the app definition itself. Customers must rebuild the app structure in the destination system. We provide a custom app field inventory (name, type, options) as a re-implementation guide.