Migrate from Celoxis to Microsoft Project

Celoxis Projects map directly to Microsoft Project project files or Project Online projects. We extract the project name, status, start date, finish date, calendar, billing type (Fixed Price vs Hourly), and budget amounts. Celoxis workspace isolation (Data Isolation feature on Enterprise) does not map to a Microsoft Project concept — we flag multi-workspace customers and advise organizing projects into Microsoft Project site collections or Project Online project spaces post-migration.

Celoxis Tasks and Subtasks map to Microsoft Project Task rows. We preserve parent-child hierarchy (outline level), WBS codes, task notes, and Celoxis custom fields defined on tasks. Celoxis split tasks map to Microsoft Project split tasks; recurring tasks map as individual tasks with a note field indicating the recurrence pattern since Microsoft Project does not store recurrence as a native recurring schedule.

Celoxis task dependencies (finish-to-start, start-to-start, finish-to-finish, start-to-finish with lead/lag time) map directly to Microsoft Project predecessor links on the successor task. We reconstruct the full dependency graph and assign the correct predecessor type and lag days per Microsoft Project's predecessor field format (e.g., 'FS+2d' for finish-to-start with two-day lag).

Celoxis multiple baselines per project map to Microsoft Project's 11 available baseline slots (Baseline through Baseline 10). We assign Celoxis baseline snapshots to Microsoft Project baseline slots in chronological order. Baseline start dates, finish dates, durations, and costs migrate to the corresponding baseline fields.

Celoxis milestones with milestone type designation map to Microsoft Project milestone tasks (zero-duration tasks). We preserve the milestone name, date, and any associated milestone-level custom fields.

Celoxis Resources (users and role-based resources) map to Microsoft Project Resources. We extract the resource name, type (Material vs Work), Max Units, Cost Rate Table entries (per-hour cost), and billing rate from Celoxis. Note that Microsoft Project does not have a separate billing rate field — cost rate is the internal rate only. Any Celoxis billing rate used for client invoicing must be recorded as a custom field in Microsoft Project.

Celoxis resource-task assignments map to Microsoft Project Assignments with the assigned resource, units (percentage or hours), and work. We preserve assignment-level notes, overtime settings, and the Celoxis booking type (Committed vs Proposed) as a custom field on the assignment.

Celoxis custom fields (25–1000 depending on tier) defined on Projects, Tasks, and Resources map to Microsoft Project custom fields of the closest matching type: Text, Number, Date, Flag, or Outline Code. We export the field definition (name, type, picklist options) and map values during the data phase. Microsoft Project custom fields have a 64-character name limit and no concept of workspace-scoped custom fields — all custom fields are project-level in desktop MS Project and org-level in Project Online.

Celoxis Risk records (available on Professional and above or as a paid add-on) have severity, probability, mitigation, owner, and status fields. Microsoft Project has no native Risk register object. We export the Risk records as a CSV with all fields and deliver them as a structured handoff document. The customer can recreate risks in a SharePoint list, Power Apps canvas app, or a third-party risk management tool. Risk Management is a paid Celoxis add-on at $5/user/month — we verify the source account has this module active at scoping.

Celoxis Issues have their own workflow states, assignee, priority, and linked project context. Microsoft Project has no native Issue tracker. We export Issue records as a CSV. The customer recreates issue tracking in SharePoint, Microsoft Lists, or a dedicated service desk tool. The Issue approval workflow state is not exportable and must be re-established in the replacement tool.

Celoxis Timesheet entries (billable and non-billable time entries with activity codes and approval status) have no Microsoft Project equivalent. Microsoft Project tracks work assignments but does not include a timesheet submission and approval module. We export timesheet records as CSV. The customer can move timesheet data to Microsoft Dynamics 365 Project Operations, Smartsheet, or another PSA tool if timesheet tracking continues post-migration. Timesheet module is a paid add-on on Celoxis Essential; we verify its active status at scoping.

Celoxis Expense records with expense codes, reimbursable flags, amounts, and approval status do not migrate to Microsoft Project. We export expense data as CSV. Microsoft Project does not include expense tracking. Customers requiring expense management post-migration should plan to use Microsoft Dynamics 365, Expensify, or a SharePoint-based expense request form built in Power Apps.

Celoxis Portfolios aggregate multiple projects under strategic groupings with portfolio-level KPIs and financial rollups. Microsoft Project lacks a native portfolio object. Project Online's Project Spaces and Project for the web's Roadmap feature provide partial portfolio visibility but do not include portfolio-level financial aggregation. We map portfolio membership (which projects belong to which portfolio) and flag that portfolio KPIs and rollup views require manual rebuild in Power BI or the Microsoft Power Platform.

Celoxis Custom Apps (Business and Enterprise tiers) create fully custom record types with their own forms, fields, and workflows. Microsoft Project has no equivalent concept. We export the data stored in Custom App records as CSV with the field definitions documented. The customer must rebuild the app structure in Power Apps or a custom SharePoint solution. Custom Apps are Celoxis-specific constructs and the app definition itself cannot be transferred.