Where a software deal came from across 4 tools

• HubSpot's Record Source Detail 1 stores the name of the import, a form, or a workflow, as stated in the "View and use record source properties" documentation HubSpot.
• If an admin edits or deletes a source channel in Pipedrive, the change applies to all existing records, including open, won, lost, and archived deals and leads, according to the "Lead source in deals" article Pipedrive.
• In Close, a Lead's Source stays associated with the Lead as it moves through Opportunity Pipelines, allowing measurement of conversion rates and revenue by the original lead source, according to the "Opportunity Pipelines & Statuses" guide Close.
• Zoho's API documentation uses "Employee Referral" as a sample value for Lead_Source in an example, not as the only allowed source, as shown in the "Insert Records" documentation Zoho.

In Pipedrive, the source is either manually entered or automatically populated when a lead or deal is added, according to Pipedrive.

Admin edits to source channels affect historical data. If an admin edits or deletes a source channel from the list of values, the change will apply to all existing records (open, won, lost and archived deals and leads), according to Pipedrive. See Open, won, and lost stage rules in 4 sales tools. This impact extends across every record state, not just new entries.

The mechanism behind this behavior is a fixed backend identifier. Pipedrive uses a fixed backend ID (source_channel_id) regardless of the name you set, according to Pipedrive. Because the ID remains constant, changing the display name alters how the source appears in existing records.

A critical constraint for revenue leaders is that in most cases, the detail properties cannot be manually set or edited, according to HubSpot.

The following table lists the source fields and their storage behaviors for Close and Zoho. Each row quotes the page for that publisher.

When reviewing a deal in HubSpot, the system captures the origin through specific properties that you should read before attempting any manual changes. The "View and use record source properties" documentation outlines exactly what these fields contain and when they were introduced. Understanding these stored values prevents you from overwriting historical data with inaccurate labels during a deal review.

The Record Source property was created in February 2024 and backfilled with data for the past four years, according to HubSpot. This backfill is a data migration event, not a performance metric or a sales result. The Record Source Detail properties were created in March 2024, according to HubSpot. These dates indicate when the fields became available in the system, not when specific deals were won or lost.

The Record Source Detail 1 field stores specific identifiers depending on how the record was created. If the record came from an import, Record Source Detail 1 stores the name of the import, according to HubSpot. If the record originated from a form, Record Source Detail 1 stores the name of the form, according to HubSpot. If the record was generated by a workflow, Record Source Detail 1 stores the name of the workflow, according to HubSpot.

This restriction means you cannot freely change the detail value to match a new channel name or a revised attribution model. You must read the value already stored in the field and record it in your review notes as-is. Do not attempt to overwrite the system-stored value with a manual entry, as the interface generally prevents this action. See Bulk-edit sales records: 4 checks before saving changes.

When you open a deal record, look for the Record Source and Record Source Detail 1 fields. Copy the exact text displayed in Record Source Detail 1 into your deal review document. If the text says "Q3 Import" or "Webinar Registration Form," write it down exactly as it appears. Do not replace it with a broader category like "Inbound" or "Outbound" unless the system itself displays that broader category. The goal is to preserve the specific origin identifier that the system captured when the record was created. This approach ensures your deal review reflects the actual data stored in the CRM rather than an interpretation of that data. See Weekly deal review filters across 4 sales systems.

In the "Lead source in deals - Knowledge Base | Pipedrive" documentation, the deal source field can be filled in two ways. This automatic population happens at the moment the record is created, tying the source value to the initial state of the deal.

When managing these source values, an admin must understand how changes propagate through the system. This broad application means that a single edit in the admin settings does not just affect new entries; it rewrites the source label on historical data across every record status.

The system tracks the source by this internal ID rather than by the visible text label. Consequently, when the visible name of the channel changes, the system updates the display text for every record linked to that specific ID.

For a revenue leader reviewing deals, this behavior implies that renaming a source channel is a global action. It alters the historical record of where deals came from, not just the label for future deals. If you change the name of a channel that was used for deals closed last quarter, those closed deals will reflect the new name in the source field.

In Opportunity Pipelines & Statuses | Close Help Center, the documentation states that a Lead's Source stays associated with the Lead as it moves through Opportunity Pipelines. This persistence allows you to continue to measure conversion rates and revenue by the original lead source, according to Close. Because the source remains attached to the lead record throughout its lifecycle, the original attribution is not overwritten when the deal progresses to later stages. This behavior supports the deal review process by ensuring the source value recorded at the start of the opportunity remains available for analysis.

In Insert Records | Zoho CRM API | V8, the documentation provides a specific example involving the Lead_Source field. It notes that if a layout rule triggers when the Lead_Source is Employee Referral, and the Company field is mandated, the system throws the MANDATORY_NOT_FOUND error if you fail to give the Company key in the input, according to Zoho. This example uses Employee Referral as a sample value to illustrate how mandatory field validation works when a specific source is selected. Employee Referral is a sample value in that example, not the only allowed source. The example serves to demonstrate the interaction between layout rules and mandatory fields in the API context.

The same Insert Records | Zoho CRM API | V8 page instructs that for any module, you must specify all the mandatory fields while creating a record, according to Zoho. Additionally, it notes that a specific key is mandatory when a pipeline is enabled for the Deals module, according to Zoho. These rules apply to the creation of records through the API and highlight the need to include required data points based on the module configuration. The distinction between a sample value in an example and a mandatory field requirement is critical for accurate record creation.

When reviewing a deal, distinguish between a source value that is a system-stored attribute and a value that is merely an example in documentation. The Close documentation confirms the source stays with the lead, while the Zoho documentation uses Employee Referral only to illustrate error handling. Do not interpret the Zoho example as a restriction on other source values. Check the specific configuration of your Zoho module to determine which fields are mandatory for your setup.

Copy the source value exactly as the system stored it. Do not rename the channel or overwrite the original entry. The goal is to record the current state before any review changes are made.

HubSpot notes that the number of detail properties containing values varies depending on the source and the specificity available, for example, Record Source Detail 1 has a value, but Record Source Detail 2 and Record Source Detail 3 don't, according to HubSpot. Copy the detail that has a value. This ensures the review reflects the actual stored data rather than an inferred label.

You open 10 deals and copy the source text already stored on each one into a review note. 4 of the 10 are closed and 6 are open. You set 0 new source names on this pass. The note keeps the wording you saw.

Open one live deal and copy the source value already stored, without renaming it.

What does HubSpot put in record source detail 1 for an import?

For an import, the system stores the name of the import in this field. According to HubSpot, the documentation specifies that Record Source Detail 1 contains "the name of the import."

When did HubSpot say the record source property was created?

The property was created in February 2024. The detail properties were created in March 2024. According to HubSpot, the Record Source property was created in February 2024 and backfilled with data for the past four years.

What happens to old Pipedrive deals if an admin edits a source channel?

The change applies to all existing records, including open, won, lost, and archived deals and leads. According to Pipedrive, if an admin edits or deletes a source channel from the list of values, the change will apply to all existing records.

Does Close keep the lead source when the lead moves through pipelines?

Yes, the source stays associated with the lead as it moves through Opportunity Pipelines. According to Close, a Lead's Source stays associated with the Lead as it moves through Opportunity Pipelines, so you can continue to measure conversion rates and revenue by the original lead source.

Is Employee Referral a required Zoho source?

No, it is a sample value used in an API example, not the only allowed source. According to Zoho, the documentation provides an example where a layout rule triggers when the Lead_Source is Employee Referral. Mandatory fields depend on your specific layout rules, not on a fixed list of sources.