How Channel Conflict Prevention Works

When a partner registers a lead, there’s a risk that the same company or contact already exists in your CRM — either as an existing deal or a previously registered lead. PartnerPortal is designed to prevent duplicates and give you control over how new leads connect to existing records.

When you approve a lead in PartnerPortal, the portal searches your connected CRM for existing records before creating anything new. You can link the incoming lead to an existing deal in your CRM, or choose to create a new one. This is the first line of defense against partners registering duplicate leads.

When a lead is approved and pushed to HubSpot, the portal automatically:

• Searches for an existing company using the submitted company’s domain name — if found, it uses that company; if not, it creates one.
• Searches for an existing contact using the submitted email address — if found, it uses that contact; if not, it creates one.
• Associates the contact with the company.
• Creates a new deal from the PartnerPortal lead data.
• Associates the contact and company with the new deal.

De-duplication behavior in Salesforce is determined by your Salesforce configuration. PartnerPortal doesn’t have visibility into your specific de-duplication rules. If Salesforce rejects a record creation due to a de-duplication rule, the portal surfaces that error to you.

• HubSpot users: company and contact de-duplication happens automatically — there’s nothing to configure.
• Salesforce users: your existing Salesforce de-duplication rules apply. Review your Salesforce configuration to make sure the rules reflect how you want duplicates handled.
• Regardless of CRM: you can always link an incoming lead to an existing CRM deal at the point of approval instead of creating a new record.