Project or work management platform
Not a CRM - fails on core objects, status, resolution, value, actual close date, linked buyer, record preservation, structured lost reasons, email sync, schedulable activity types, opportunity reporting
Core objects
Not at all
Trello's documented object model is Board, Card, Member, Action, Attachment and Sticker. Card is the only working record; there is no separate Person, Company or Activity object. The API's "Organization" is the Workspace (a team/billing container linked from Board.idOrganization), not a customer company record.
Source: https://developer.atlassian.com/cloud/trello/guides/rest-api/object-definitions/, https://developer.atlassian.com/cloud/trello/swagger.v3.json
Verification: Verified
Pipeline stages
In full
The List schema carries a numeric `pos` field for ordering and an `idBoard` reference. The Card schema carries `idList`, so each card holds the list (stage) it is in and lists are ordered on the data.
Source: https://developer.atlassian.com/cloud/trello/swagger.v3.json
Verification: Verified
Status
Not at all
Card's only state field is `closed` (archived/not archived), which controls board visibility, not an open-vs-closed deal outcome. No field separates deal status from which list a card occupies.
Source: https://developer.atlassian.com/cloud/trello/swagger.v3.json, https://support.atlassian.com/trello/docs/archiving-and-deleting-cards/
Verification: Verified
Resolution
Not at all
No won/lost field ships on the Card object, and no stage-metadata mechanism (like a "stage marked won" flag) is documented.
Source: https://developer.atlassian.com/cloud/trello/swagger.v3.json
Verification: Verified
Value
Not at all
No money field ships on the Card object. Custom Fields (Standard plan and up) support checkbox, date, dropdown, number and text types only - the vendor states there is no currency/money type, and the field itself must be buyer-created.
Source: https://support.atlassian.com/trello/docs/using-custom-fields/
Verification: Verified
Scope of work
In part
Card carries a native `desc` (description) field of up to 16,384 characters. There is no line-item or product structure.
Source: https://developer.atlassian.com/cloud/trello/swagger.v3.json
Verification: Verified
Expected close date
In full
Card ships a native `due` date field, settable on any card without a Power-Up or custom field.
Source: https://developer.atlassian.com/cloud/trello/swagger.v3.json
Verification: Verified
Actual close date
Not at all
Card's only completion field is `dueComplete`, a boolean. No native field records the date/time a card was marked done or closed; vendor docs describe no such field.
Source: https://developer.atlassian.com/cloud/trello/guides/rest-api/object-definitions/
Verification: Verified
Opportunity owner
In full
Card ships an `idMembers` field for assigning one or more members, set and changed independently of who created the card (creator information is not even a Card field - it is derived from the card's action/creation log).
Source: https://developer.atlassian.com/cloud/trello/swagger.v3.json
Verification: Verified
Linked buyer
Not at all
Trello has no customer/contact record type at all - Members are Trello platform users (collaborators), not a shippable "Person" business record - so there is no person record for a card to link to as a buyer.
Source: https://developer.atlassian.com/cloud/trello/guides/rest-api/object-definitions/
Verification: Verified
Record preservation
In part
Archiving a card preserves it indefinitely, searchable and recoverable, distinct from permanent deletion. Vendor docs do not state whether archived cards feed Dashboard view's reporting.
Source: https://support.atlassian.com/trello/docs/archiving-and-deleting-cards/, https://support.atlassian.com/trello/docs/dashboard-view/
Verification: Verified
Structured lost reasons
Not at all
No native lost-reason field ships. A buyer-built dropdown Custom Field could hold reasons, but Dashboard view (the native reporting surface) explicitly does not support custom field calculations, and Table view documentation does not describe grouping or counting by custom field.
Source: https://support.atlassian.com/trello/docs/dashboard-view/, https://support.atlassian.com/trello/docs/single-board-table-view/
Verification: Verified
Email sync
Not at all
"Create cards by email" is one-directional: sending or forwarding mail to a Trello-controlled address creates a card. It is not a mailbox connection - vendor docs describe no way to send email from Trello or read a real inbox.
Source: https://support.atlassian.com/trello/docs/creating-cards-by-email/
Verification: Verified
Calendar sync
In part
Calendar view (Premium/Enterprise) exports only a card's due date via a one-way iCalendar feed to Outlook or Google Calendar; vendor docs state changes made in Trello won't instantly update third-party apps, and there is no reverse sync creating or editing cards from the external calendar.
Source: https://support.atlassian.com/trello/docs/using-trello-with-microsoft-outlook/, https://support.atlassian.com/trello/docs/calendar-view/
Verification: Verified
Schedulable activity types
Not at all
Trello has no activity-type concept (call, meeting, task) - a card carries one due date and optional checklist items, with no fixed or buyer-defined set of schedulable activity types.
Source: https://developer.atlassian.com/cloud/trello/swagger.v3.json
Verification: Verified
Opportunity reporting
Not at all
Dashboard view (Premium and up), the only native reporting surface, shows cards per list, per due date, per member and per label as counts/bar or pie charts. Vendor docs list this early version as not supporting conversion rates or forecasts.
Source: https://support.atlassian.com/trello/docs/dashboard-view/
Verification: Verified