Migrate from ClickUp to Microsoft Project

Each ClickUp List becomes a separate Microsoft Project file (.mpp) or Project Online project. The List name becomes the Project name. We map the List's default status configuration to Project task status (Not Started, In Progress, Completed). List-level Custom Fields scoped to the source List are exported with their scope metadata and recreated as Project Custom Fields on the destination project. Spaces and Folders above the List are mapped to Summary Tasks inside the project or held as a separate naming convention for the customer's Project Online workspace structure.

ClickUp Folders (the middle hierarchy layer) map to Summary Tasks in Microsoft Project. Summary Tasks in Project can be collapsed to hide child tasks, which approximates the Folder collapse behavior in ClickUp. We preserve the Folder's custom status settings and any Folder-level Custom Fields by attaching them as Project-level custom columns that inherit to all child Summary Tasks and regular Tasks. If the customer uses Project Online, we can map Folders to Project phases using the Phase custom field.

ClickUp Tasks map directly to Microsoft Project Tasks. The mapping includes Task Name, Start Date, Due Date (converted to Finish Date in Project), Priority (mapped to Project Priority field), Assignees (mapped to Resources with unit allocation), Description, and any attachments (migrated as linked file references to SharePoint or external URLs). Task status in ClickUp (Custom Status values) is mapped to Project Task Status (Not Started, In Progress, Completed) with a custom field preserving the original ClickUp status label for audit.

ClickUp Subtasks map to indented Tasks in Microsoft Project at outline level two or deeper, preserving the parent-child relationship as outline hierarchy. We note that Subtasks in ClickUp do not inherit all parent task properties, so we explicitly copy Start, Finish, and Duration from the parent to the child during migration to ensure the subtask retains scheduling context. The subtask name inherits the full ClickUp path in a custom field for traceability.

ClickUp task dependencies (Finish-to-Start, Start-to-Start, Finish-to-Finish, Start-to-Finish) map to Microsoft Project predecessor-successor links with equivalent dependency types. We export the dependency relationship as Task Name plus dependency type, then resolve the predecessor task GUID to its new Project Task ID during import. Lag time and lead time values migrate as Project lag or lead days. We flag any dependency loops detected during export for the customer to resolve before migration runs.

ClickUp time entries (duration, user, billable flag) map to Project Assignment Actual Work on the corresponding Task-Resource assignment. We extract time tracked per task per user, aggregate by task, and set Actual Work in hours on the task. Billable flag from ClickUp is stored as a custom Project flag field (Is Billable). Planned hours from ClickUp (if set) migrate as the Project Task estimated work value. Note that Microsoft Project requires Resources to be defined before assignments can be made, so Resource provisioning happens before time entry migration.

ClickUp Custom Fields scoped to List or task level are mapped to Microsoft Project Custom Fields. We perform type conversion: ClickUp dropdown fields become Project Lookup Tables; ClickUp date fields become Project Date columns; ClickUp number and currency fields become Project Number and Cost columns; ClickUp person fields are resolved to Project Resources. ClickUp equation fields are not natively supported in Project; we document the formula logic for the customer to recreate in a Project custom field or external tool. Custom Fields scoped at Space or Workspace level that should cascade to all Lists require pre-migration restructuring or a documented field re-creation plan.

ClickUp view configurations (List, Board, Gantt, Calendar, Timeline) are recreated as Microsoft Project views. The Gantt view is the default view in Project and maps most directly from ClickUp's Gantt. ClickUp List view maps to the Task Sheet view in Project. Board view has no direct equivalent; we recommend using Grouping in Project's Task Sheet with the Status or Resource field as the grouping key. Calendar view maps to Project's Calendar view. We deliver a view-mapping document listing the destination view and any non-standard column or grouping configuration.

ClickUp Tags (workspace-level labels applied to tasks across lists) are mapped to a Project Text column named Tag. Multi-value tags (tasks with multiple tags) are concatenated with commas in the single text column. If the customer uses Project Online, we can map tags to a SharePoint managed metadata column if the SharePoint task list integration is used. We do not create a separate tag management interface because Microsoft Project has no native tag registry.

ClickUp Goals with linked tasks, key results, and progress metrics have no Microsoft Project equivalent. Project Online Plan 5 includes portfolio-level status reporting but not the Goal data model. We export the Goal definitions (name, description, linked tasks, current progress) to a structured CSV inventory that the customer's PMO uses to re-establish goal tracking post-migration, either in Project Online's portfolio views, a separate Excel model, or a dedicated OKR tool. This is a manual handoff, not an automated migration.

ClickUp Automations (triggers and actions based on task events) have no Microsoft Project equivalent inside the core product. We export every automation rule with its trigger, conditions, and actions to a written inventory document that the customer's team reviews for rebuild in Power Automate (cloud flows) or as manual project management procedures. Automations are not migrated as code. The inventory includes the ClickUp automation name, the List it applies to, trigger event, condition logic, and recommended Power Automate trigger/action pair.