Project or work management platform
Not a CRM - fails on core objects, status, resolution, value, linked buyer, opportunity reporting
Core objects
Not at all
ClickUp's only record type is the Task, held under Space > Folder > List. 'Custom Task Types' let a workspace name and icon a variant (e.g. Deal, Contact) but it shares the Task schema and endpoints - the API doc calls it a classification set via `custom_item_id`, not a distinct object. The 'Tasks' custom field type links tasks to other tasks generically; there is no dedicated Person or Organization schema.
Source: https://developer.clickup.com/docs/custom-task-types, https://developer.clickup.com/docs/tasks, https://developer.clickup.com/docs/customfields
Verification: Verified
Pipeline stages
In full
Each List's `statuses` array carries an ordered `orderindex` per status, and every task carries a single current `status`. This is confirmed in the official Get List response example, which lists statuses with `orderindex` and `type`.
Source: https://developer.clickup.com/reference/getlist
Verification: Verified
Status
Not at all
The Get List schema shows each status object itself carrying a `type` of `open` or `closed` (e.g. 'to do' type open, 'complete' type closed). Open/closed is a property of which status a task occupies, not a separate field on the task.
Source: https://developer.clickup.com/reference/getlist
Verification: Verified
Resolution
Not at all
Status `type` only takes open/closed values in the documented schema - there is no won/lost value and no separate resolution field shipped on a task.
Source: https://developer.clickup.com/reference/getlist
Verification: Verified
Value
Not at all
Money/Currency is listed among the optional Custom Field types a workspace can choose to add; it is not a field present on a task by default the way status or due_date are.
Source: https://developer.clickup.com/docs/customfields
Verification: Verified
Scope of work
In part
Every task carries a native `description`/`text_content` field in the documented Task schema. There is no shipped line-item or product list.
Source: https://developer.clickup.com/reference/gettask
Verification: Verified
Expected close date
In full
`due_date` is a native, settable field on every task per the documented Task and Update Task schemas, not a buyer-added custom field.
Source: https://developer.clickup.com/reference/gettask, https://developer.clickup.com/reference/updatetask
Verification: Verified
Actual close date
In full
`date_closed` is documented as a native task field: 'Timestamp when task was closed', null until the task's status changes to a closed-type status - a system-set value, not a buyer-built field.
Source: https://developer.clickup.com/reference/gettask
Verification: Verified
Opportunity owner
In full
The documented Task schema carries `assignees` (users assigned) as a field distinct from `creator` (user who created the task).
Source: https://developer.clickup.com/reference/gettask
Verification: Verified
Linked buyer
Not at all
No Person object exists to link to. The only native linking mechanism, the 'Tasks' custom field type, connects a task to other generic tasks, not to a dedicated buyer/contact record.
Source: https://developer.clickup.com/docs/customfields
Verification: Verified
Record preservation
In full
Archiving is documented as a distinct, optional action from closing a task: 'When you archive a task, you're removing it from view, not deleting it.' Marking a task's status closed does not archive or delete it, so closed tasks remain in place and queryable.
Source: https://help.clickup.com/hc/en-us/articles/6329610622487-Archive-a-task
Verification: Verified
Structured lost reasons
In part
No shipped lost-reason field exists, but a buyer-built Dropdown/Label custom field is countable: Pie Chart dashboard cards document 'Group by' options including 'Custom Fields', so a lost-reason dropdown can be tallied natively.
Source: https://help.clickup.com/hc/en-us/articles/25952858845719-Pie-Chart-cards
Verification: Verified
Email sync
In full
Users connect their own Gmail, Outlook/Microsoft 365 or IMAP mailbox to a task. Vendor help states: 'Send and receive emails directly from tasks' and replies 'will be displayed in the task's activity feed in addition to your email inbox' - two-way, not BCC-only.
Source: https://help.clickup.com/hc/en-us/articles/6303747270807-Use-Email-in-ClickUp
Verification: Verified
Calendar sync
In part
Google/Outlook Calendar integrations sync calendar events both ways in ClickUp's Planner, but vendor docs qualify this: 'Changes you make to an event in Google Calendar will not update the related task in ClickUp' and 'Tasks that are added to your Planner will not be reflected in your Outlook Calendar' - task-level sync runs one direction only. The separate iCal feed is explicitly one-way.
Source: https://help.clickup.com/hc/en-us/articles/6336507264663-Google-Calendar-integration, https://help.clickup.com/hc/en-us/articles/30618267005975-Outlook-Calendar-integration
Verification: Verified
Schedulable activity types
In full
Custom Task Types are workspace-defined names (Call, Meeting, etc.) on the same schedulable Task object (due/start date, reminders) - a native feature for buyer-defined types, not a fixed vendor list.
Source: https://developer.clickup.com/docs/custom-task-types
Verification: Verified
Opportunity reporting
Not at all
Calculation cards only offer generic 'Sum, Count, Average, Median, Min, Max, Range' presets, and Pie/Bar cards produce distributions grouped by status or field - not rates. No native win-rate, conversion-rate or forecast metric is documented.
Source: https://help.clickup.com/hc/en-us/articles/21928345433879-Calculation-cards, https://help.clickup.com/hc/en-us/articles/25952858845719-Pie-Chart-cards
Verification: Verified