Copper

Copper carries separate Person, Company, Opportunity and Task record types, alongside Leads and Projects. The Opportunity entity exposes `company_id` and `primary_contact_id` association fields, and a task can be related to a lead, person, company or opportunity record. Records can also be linked through a Related section on each profile. Only `name` is required by the API when creating an opportunity, so company association is possible rather than compulsory, although the guidance for creating an opportunity in the interface describes a primary contact as a required field.

Source: https://developer.copper.com/opportunities/create-a-new-opportunity.html, https://developer.copper.com/opportunities/fetch-an-opportunity-by-id.html, https://support.copper.com/en/articles/8823248-relating-records, https://support.copper.com/en/articles/8823266-working-with-tasks, https://support.copper.com/en/articles/8823260-working-with-opportunities

Verification: Verified

An opportunity sits in a pipeline and moves through that pipeline's ordered stages, carrying `pipeline_id` and `pipeline_stage_id`. Stages are defined by the account, can be renamed, reordered and deleted, and each stage carries its own win probability.

Source: https://developer.copper.com/opportunities/list-pipeline-stages.html, https://support.copper.com/en/articles/9533612-working-with-new-pipelines, https://developer.copper.com/opportunities/fetch-an-opportunity-by-id.html

Verification: Verified

The Opportunity object carries its own status attribute whose documented values are Open, Won, Lost and Abandoned, held separately from pipeline_stage_id. Open versus settled is therefore readable from the opportunity itself with no stage lookup.

That field's own values are not open/closed alone - they also carry won and lost (see resolution notes), so it is a single non-overlapping tri-state mechanism rather than a dedicated status-only attribute. Amended 4 Sep 2026: this scores in part, not in full.

Source: https://developer.copper.com/opportunities/overview.html

Verification: Verified

The same status attribute carries Won and Lost as distinct values, so the outcome is an attribute of the opportunity rather than something inferred from the stage it ended in. Copper's help center describes Won, Lost and Abandoned as the closing statuses a user applies.

Source: https://developer.copper.com/opportunities/overview.html

Verification: Verified

monetary_value ships on the Opportunity, surfaced as projected revenue.

Source: https://developer.copper.com/opportunities/overview.html, https://support.copper.com/en/articles/8823260-working-with-opportunities

Verification: Verified

Only details, documented as a description, with no products or line-items facility.

Source: https://developer.copper.com/opportunities/overview.html, https://support.copper.com/en/articles/8823260-working-with-opportunities

Verification: Verified

close_date ships, documented as the expected close date.

Source: https://developer.copper.com/opportunities/overview.html, https://support.copper.com/en/articles/8823260-working-with-opportunities

Verification: Verified

Copper ships one close_date field, documented in the API reference as the expected close date, and there is no second field for the date an opportunity actually settled. The vendor's help center instructs the user to set that same field when closing: to add a closing date showing when the deal was completed on a win, and to change the close date to today on a loss. No vendor documentation states that Copper stamps the date itself when status changes.

Source: https://support.copper.com/en/articles/8823260-working-with-opportunities

Verification: Verified

assignee_id ships, the user who owns the Opportunity.

Source: https://developer.copper.com/opportunities/overview.html, https://support.copper.com/en/articles/8823260-working-with-opportunities

Verification: Verified

primary_contact_id is a required link to a Person, alongside the separate company_id.

Source: https://developer.copper.com/opportunities/overview.html, https://support.copper.com/en/articles/8823260-working-with-opportunities

Verification: Verified

Closed opportunities stay in the account and stay measurable. Copper's custom report metric list includes separate record counts and value sums for won, lost and open opportunities, win rate metrics, and a running sum of won value ordered by the opportunity close date, all of which require the closed records to persist and remain queryable.

Source: https://support.copper.com/en/articles/8823394-custom-reports-reference-documents-metrics

Verification: Verified

Marking an opportunity Lost prompts for a Loss Reason chosen from a defined list, stored on the record as `loss_reason_id`. Administrators can add, rename, reorder and delete the options, and the values feed a Loss Reasons report, so the field is structured and reportable rather than free text.

Source: https://support.copper.com/en/articles/8823335-understand-and-customize-loss-reasons-field, https://developer.copper.com/opportunities/fetch-an-opportunity-by-id.html

Verification: Verified

With a connected Google account, mail sent and received in Gmail syncs automatically onto the matching Copper records, and the Send and Reply from Copper setting lets users compose and reply from inside Copper with delivery through their Gmail address, so the flow runs both ways. The capability is constrained to Google mailboxes: vendor documentation names no Microsoft 365 or Outlook mailbox connection, and directs users of other clients to a BCC address instead. Mail between users on the account's own domain is excluded from sync.

Source: https://support.copper.com/en/articles/8823339-email-settings, https://support.copper.com/en/articles/8823283-working-with-the-gmail-integration, https://support.copper.com/en/articles/8823340-send-and-reply-from-copper-setting, https://support.copper.com/en/articles/8823268-how-emails-and-logged-activities-sync-between-records

Verification: Verified

Calendar events are a two-way sync with Google Calendar: an event created on a Copper record is issued as a Google Calendar invitation, existing Google Calendar events are pulled into Copper against recognized record email addresses and logged in the activity log, and an update on either side is mirrored on the other. Two constraints apply. Tasks sync to Google Calendar in one direction only, into a Copper Reminders calendar carrying name, due date and due time, and vendor documentation describes no equivalent Outlook or Microsoft 365 calendar sync.

Source: https://support.copper.com/en/articles/8823250-creating-and-syncing-events-to-google-calendar, https://support.copper.com/en/articles/8823267-syncing-tasks-to-google-calendar, https://support.copper.com/en/articles/8823337-google-sync-settings

Verification: Verified

Tasks are created inside Copper with a due date, reminder, assignee, priority, status, a related record and an Activity Type, and can be single or recurring with subtasks. Activity types ship with Phone Call, Meeting and To-do, and administrators can create custom types, up to thirty enabled at a time, optionally counting as interactions for reporting. Calendar events for meetings can also be created directly from a record.

Source: https://support.copper.com/en/articles/8823266-working-with-tasks, https://support.copper.com/en/articles/8823328-create-and-edit-activity-types, https://support.copper.com/en/articles/8823250-creating-and-syncing-events-to-google-calendar

Verification: Verified

Amended 14 Sep 2026: this record previously credited Copper with a passing win-rate leg. That credit is withdrawn - the metric is a marketing-style ratio, not a win rate, and this now fails the leg.

One of the three required reports is native. Forecasting is native through the Pipeline Projection Total and Pipeline Projection Weighted reports, which group open opportunities by expected close date and weight value by the win probability attached to the stage. The other two fail. Stage-to-stage conversion rate is not documented: the pipeline summary reports show value, count and average days per stage rather than the proportion advancing, the days-in-stage custom report covers duration only, and requests for a funnel conversion report appear as open questions in the vendor community. Win rate also fails: Copper's own custom-report reference defines "Opp Record Count Win Rate %" as "the percentage of opportunities that are Won Status" and "Opp Value Win Rate %" as "the percentage of total Opp Value that is Won Status" - a proportion against opportunities generally, not against closed (won+lost) opportunities specifically - and a separate Copper support article gives the same metric a stated formula elsewhere: "Total win rate is calculated by dividing (won opportunities / total opportunities) * 100". Won divided by all opportunities, open ones included and undifferentiated from lost ones in the denominator, is a marketing-style lead-conversion ratio, not a sales win rate (won ÷ (won+lost)) - the same conflation found on GoHighLevel's "Conversion Rate" widget. A Looker Studio connector exists for reporting outside the product, which does not count toward this dimension.

Source: https://support.copper.com/en/articles/8823394-custom-reports-reference-documents-metrics, https://support.copper.com/hc/en-us/articles/204356615-Legacy-Reports-Sales-By-Owner-Source-and-Loss-Reasons, https://support.copper.com/en/articles/8823412-pipeline-reports-forecast, https://support.copper.com/en/articles/8823409-pipeline-reports-pipeline-summary, https://support.copper.com/en/articles/8823379-custom-reports-sales-cycle-length-and-days-in-stage, https://community.copper.com/ask-a-question-or-share-an-idea-33/opportunity-conversion-rate-between-stages-1359

Verification: Verified