Skip to content

How to Sync Leads to Your CRM

PartnerPortal sends the partner leads you approve to your CRM as new deals, then keeps each lead connected to its deal as the deal moves forward. This page explains that whole process for every supported CRM: setting up the mapping, what happens when you approve a lead, syncing leads automatically, what comes back from your CRM, what to do when a sync fails, and how to disconnect. Each CRM’s own guide covers its connect steps and mapping screens.

Play

PartnerPortal has a native integration with each of these CRMs. The process on this page applies to all of them. Where a CRM behaves differently, this page says so.

Every lead follows the same path from your portal into your CRM:

  1. You connect your CRM and map it once. The mapping says which CRM records to create and how to fill them in from the lead.
  2. A partner registers a lead. It waits in Pending for your team, unless your portal approves leads automatically.
  3. The lead is approved, and a CRM record is created or linked. Your team chooses at approval time, or PartnerPortal does it for you if automatic sync is on.
  4. The lead and the CRM deal stay connected. Changes to the deal in your CRM, such as a new stage or close date, update the portal lead, so partners see progress without anyone retyping it.
  5. Optionally, portal edits go back to the CRM. On HubSpot and Pipedrive, two-way sync sends changes to a lead’s phase, close value and close date from the portal to the deal.

A lead in Pending is never sent to your CRM. Sync starts when the lead is approved.

A portal admin connects your CRM once from Integrations, signs in to the CRM to authorize the connection, and then sets up the mapping. Only one CRM can be connected at a time. For the exact steps, open your CRM’s guide above.

The mapping controls which records PartnerPortal creates in your CRM and how each field is filled in. You can fill a CRM field from:

  • a lead field, including the custom fields on your lead registration form
  • a field on the partner company, such as its name
  • a field on the partner user who registered the lead
  • a fixed value you type in, such as a lead source of “Partner”

Zoho is the exception. It can only be filled from lead fields, not partner fields.

Most CRMs create a deal plus the contact and company it belongs to. Salesforce lets you choose which objects to create, including custom objects. For the mapping screens, see your CRM’s guide.

Your lead phases are matched to your CRM’s deal stages, in both directions:

  • CRM stage to portal phase. When a deal changes stage in your CRM, the linked lead moves to the matching phase.
  • Portal phase to CRM stage. This sets the stage a new deal starts in. With two-way sync on, it also sets the deal’s stage when the lead’s phase changes in the portal.

For the starting stage of a new deal you can let PartnerPortal infer it from the mapping, map it manually, or always use one fixed stage.

Any stage or phase you don’t map is treated as N/A. A CRM stage mapped to N/A leaves the lead’s phase unchanged.

The deal-stage mapping screen where PartnerPortal phases are matched to CRM stages.

Map your won and lost stages to the portal’s Won and Lost phases. That mapping is what lets a deal you close in the CRM start payouts in the portal. See When a deal is won or lost.

When you approve a lead from its detail page and your portal has a CRM connected, PartnerPortal shows a dialog with three choices:

  • Create new — approve the lead and create a new deal in your CRM from the lead’s details. This is the standard path.
  • Link existing — approve the lead and connect it to a deal that already exists in your CRM, instead of creating a second one. See Link an existing CRM record.
  • Just approve — approve the lead without creating or linking anything. Use this for a lead that shouldn’t go to your CRM, or to connect it later.

The lead approval dialog with options to create a new deal, link an existing deal, or just approve the lead.

On Salesforce the buttons say Connection instead of Deal, because a lead can be linked to a Salesforce Lead or an Opportunity.

The lead is approved first, and then the CRM record is created. If creating the record fails, the lead stays approved. See If creating a CRM record fails.

CRMWhat Create new createsExisting contacts and companies
HubSpotEvery object in your mapping, usually a deal, contact and company, linked togetherReused only if HubSpot reports a duplicate and Duplicate Handling is set to Adopt
SalesforceThe objects you map, skipping any with Create on Lead Approval turned offMatched by your Salesforce duplicate rules when Duplicate Handling is set to Adopt
PipedriveAn organization, a person and a dealAlways created new
ZohoAn account, a contact and a dealAlways created new
AttioA deal, linked to a company and a personAlways reused: the company is matched by website domain and the person by email

On HubSpot and Salesforce, Error Handling decides what happens when one record in the set fails. Cleanup deletes the records already created in that attempt. Don’t Cleanup leaves them in place. For how existing records are matched, see How Duplicate Lead Detection Works.

Lead comments and files are not sent when the deal is created. HubSpot can copy comments added afterwards. See Comments and files.

The name of a new CRM deal comes from your field mapping. Most portals map the CRM’s deal name field to the name PartnerPortal generates:

  • HubSpot and Salesforce use the lead’s Company Name, then the contact’s name if there is no company. If both are empty, the name is Deal for Lead followed by the lead’s ID.
  • Pipedrive, Zoho and Attio combine the contact’s name and the company, such as Jane Doe - Acme Inc.

To mark every portal deal the same way, add a suffix in Leads → Configure → General Settings → CRM deal name suffix. For example, a suffix of - Partnerships turns Acme Inc into Acme Inc - Partnerships. The suffix applies to every CRM, and to deals created after you save it.

The Leads General Settings card with a CRM deal name suffix entered.

Use Link existing when the company or deal is already in your CRM, for example because your sales team logged it before the partner registered it.

  1. Choose Link existing, at approval or from the lead’s Connect button.

  2. Type in the search box and click Search. PartnerPortal searches your CRM live.

  3. Select the deal you want, then click Link Deal (on Salesforce, Link Connection).

  4. Click Proceed to confirm.

The link-existing dialog with a search box and a list of matching CRM deals to choose from.

What the search looks at depends on your CRM:

  • HubSpot matches words in the deal name, or an exact HubSpot deal ID. An empty search lists the first 100 deals.
  • Salesforce matches part of the record name, or an exact record ID. Records already linked to another lead are left out, and Salesforce won’t let one record be linked to two leads.
  • Pipedrive matches the deal title, or a deal ID. Type at least two characters.
  • Zoho uses Zoho’s own search across the deal’s searchable fields.
  • Attio matches part of the deal name.

If you approved a lead without syncing it, or it was approved before your CRM was connected, you can connect it at any time. An approved lead that isn’t linked yet shows a Connect button on its Pipeline details card.

  1. Open the lead’s detail page.

  2. Click Connect.

  3. Choose Create new to create a new CRM record, or Link existing to search for one.

An approved lead's pipeline details showing the Connect button next to the not-yet-linked CRM deal.

Once a lead is connected, the same card shows a link to the deal. Click it to open the deal in your CRM. Partners don’t see this link, or the Connect and Disconnect buttons.

A connected lead showing a deep link to the linked HubSpot deal and a Disconnect button.

When Create new fails after you approve a lead, PartnerPortal shows the error your CRM returned. The lead stays Approved but isn’t linked, so it shows the Connect button. Fix the cause, then click Connect to try again.

Common causes:

  • A required CRM field is empty. Your CRM requires a field that your mapping fills from a lead field the partner left blank. Make the lead field required on your lead registration form, or map a fixed value.
  • The record already exists. On HubSpot or Salesforce with Duplicate Handling set to Error, a duplicate stops the create. Use Link existing instead, or switch the setting to Adopt.
  • The lead has no partner user. HubSpot and Salesforce can’t create a record for a lead that isn’t attached to a partner and a partner user. Assign one on the lead’s Partner details card.
  • The connection has expired. Reauthorize the integration from Integrations.

PartnerPortal can approve new leads and create their CRM deals with no one on your team stepping in. This uses two switches on the Lead Settings screen, and works with HubSpot and Salesforce.

The General Settings card in edit mode, with switches for admin review, auto-approve, auto-sync to CRM and duplicate detection.

  1. Open Leads → Configure and click the edit button on the General Settings card.

  2. Turn on Auto-approve new leads. If New leads require admin review is on, turn it off first. The two can’t be on together.

  3. Turn on Auto-sync auto-approved leads to CRM.

  4. Click Save.

From then on, each new lead is sent to your CRM as if an admin had approved it and chosen Create new. The deal is created first, and the lead is approved once that works.

The settings act on leads created after you save. Leads already waiting in Pending are not approved or synced.

Automatic sync applies only to leads that are auto-approved. Leads your team approves by hand still show the approval dialog.

These leads are never auto-approved or auto-synced. They wait in Pending for your team:

Leads from the public lead form follow these settings like any other lead.

If your CRM rejects the new deal, the lead is not approved. It stays in Pending with the error saved on it, so it never shows as approved with nothing in your CRM.

When you open the lead, a yellow banner says Automatic CRM sync failed, with the error from your CRM. Fix the cause, then click Approve & connect in the banner to approve the lead and choose how to connect it.

PartnerPortal doesn’t retry a failed sync or email anyone about it. Check your Pending leads for the banner. If your portal’s account is suspended for billing, new leads aren’t synced, and they also stay in Pending.

Data can move between your portal and your CRM in two directions:

  • Portal to CRM, on approval. Creating the deal sends the lead’s data, for every CRM.
  • CRM to portal, afterwards. Changes to the deal in your CRM update the linked lead.
  • Portal to CRM, afterwards. Only with Two-Way Sync, on HubSpot and Pipedrive.
CRMUpdates from CRM to portalWhat comes backTwo-way sync (portal to CRM)
HubSpotAlways onEvery mapped field HubSpot can change, including contact and custom fieldsYes, with Two-Way Sync, off by default
SalesforceSync Deal Details Back to PartnerPortal. Older connections may have it offEvery mapped field Salesforce can changeNo
PipedriveSync Deal Details Back to PartnerPortal, on by defaultPhase, close value, close date, and won or lost status with the lost reasonYes, with Two-Way Sync, off by default
ZohoAlways onPhase, close value, close date, and lost statusNo
AttioSync Deal Details Back to PartnerPortal, on by defaultPhase, close value, close date, and won or lost statusNo

On HubSpot, the lead’s submission date and notes are never overwritten from the CRM.

On Salesforce, Track lead conversion keeps a lead connected when the Salesforce Lead it is linked to is converted into an Opportunity. See the Salesforce guide.

Two-way sync sends changes to a lead’s Phase, Close Value and Close Date from the portal to the linked deal. It is available on HubSpot and Pipedrive, and is off until you turn on Two-Way Sync in the integration’s settings. On Pipedrive, moving a lead to Won or Lost also marks the deal won or lost.

Your team can make those edits on the lead’s Pipeline details card. Partners can only make them if Allow partner to update pipeline status is on for their partner company. With two-way sync on, their edits are sent to the CRM like yours. See Enable two-way sync and reseller permissions and the Pipedrive guide.

Map both directions of your stage mapping before you turn it on. Otherwise phase changes in the portal have no stage to go to.

On HubSpot and Salesforce, every lead field you have mapped is locked on a linked lead. Those fields show as read-only on the lead, and they change only when the CRM sends an update. On HubSpot with two-way sync on, Phase, Close Value and Close Date unlock again so they can be edited and sent to HubSpot.

On Pipedrive, Zoho and Attio, fields stay editable on a linked lead. The next update from your CRM overwrites any field it sends, such as the phase or close value. Make pipeline changes in your CRM, so the two don’t disagree.

Moving a deal to a stage mapped to Won or Lost moves the lead to that phase, with these effects in the portal:

  • Won sets the lead to Active and records the date it was won. If Generate Commissions on Closed Won is on, it also creates a payout from the lead’s close value. See Payment Settings.
  • Lost expires the lead if Leads moved to Lost expire is on in Lead Settings. Otherwise its status stays the same.

How each CRM decides a deal is won or lost:

  • HubSpot and Salesforce follow your stage mapping. A won stage also sets the close date to today, unless Salesforce’s close date is mapped separately. Moving a deal to any other stage sets the lead back to Approved and clears its close date, so a deal you reopen in the CRM reopens in the portal.
  • Pipedrive uses the deal’s own won or lost status. A deal marked won or lost in Pipedrive moves the lead to Won or Lost, whatever the stage mapping says.
  • Zoho follows your stage mapping. A Closed Won or Closed Lost stage only changes the lead’s phase if it is mapped to Won or Lost.
  • Attio treats a stage as won or lost if it is mapped to Won or Lost, or if its name contains “won” or “lost”.

On HubSpot, turn on Comment / Activity Tracking to copy comments added to a linked lead onto the HubSpot deal’s timeline. Comments made in HubSpot don’t come back to the portal. See Comment / Activity Tracking.

The other CRMs don’t receive comments. No CRM receives the files shared on a lead.

Partners see their lead’s phase, close date and close value, which come from your CRM once the lead is linked. You can hide the close value from partners. See Sensitive fields.

Partners never see your CRM’s own stage names, only the portal phase each stage is mapped to. The link to the CRM deal, the Connect and Disconnect buttons, and the CRM icons on linked fields are shown only to your team.

The Disconnect button on a linked lead removes the link between the lead and its CRM deal. It doesn’t delete or change the deal in your CRM, and the lead keeps its status. You can connect the lead again later.

  • Deleting a portal lead removes its link to the deal. The deal stays in your CRM. Only Pending or Declined leads with no payouts and no matched revenue can be deleted.
  • Deleting a deal in your CRM leaves the portal lead in place, with the last values it received, and removes the link.

Disconnecting your CRM from Integrations removes the stored connection. On HubSpot, Pipedrive, Zoho and Attio, it also deletes every link between your leads and their deals. Reconnecting doesn’t restore those links, so you would have to link each lead again by hand. If the CRM asks you to sign in again, use Reauthorize instead.

Sync usually starts in the portal. HubSpot can also work the other way: it can watch your HubSpot deals and create portal leads from them, credited to the partner each deal belongs to. See Import HubSpot Deals as Leads. The other CRMs don’t create portal leads.

SettingWhereWhat it doesCRMs
Auto-approve new leadsLeads → Configure → General SettingsApproves new leads on arrivalAll
Auto-sync auto-approved leads to CRMLeads → Configure → General SettingsCreates a CRM deal for each auto-approved leadHubSpot, Salesforce
Detect duplicate leadsLeads → Configure → General SettingsHolds leads for companies already registered, and keeps them from auto-syncingAll
CRM deal name suffixLeads → Configure → General SettingsAdds text to the end of every new deal nameAll
Leads moved to Lost expireLeads → Configure → Lead PhasesExpires a lead when it moves to Lost, including from your CRMAll
Duplicate HandlingIntegration settingsFails or reuses the record when the CRM reports a duplicateHubSpot, Salesforce
Error HandlingIntegration settingsDeletes or keeps partly created records after a failureHubSpot, Salesforce
Sync Deal Details Back to PartnerPortalIntegration settingsTurns updates from the CRM to the portal on or offSalesforce, Pipedrive, Attio
Two-Way SyncIntegration settingsSends phase, close value and close date changes to the CRMHubSpot, Pipedrive
Comment / Activity TrackingIntegration settingsCopies lead comments to the HubSpot dealHubSpot
Generate Commissions on Closed WonPortal Setup → Payment SettingsCreates a payout when a lead moves to WonAll

Can leads sync to my CRM automatically, without anyone approving them?

Section titled “Can leads sync to my CRM automatically, without anyone approving them?”

Yes, on HubSpot and Salesforce. Turn on Auto-approve new leads and Auto-sync auto-approved leads to CRM in Leads → Configure. See Sync leads automatically.

Can I sync leads automatically when my team approves them by hand?

Section titled “Can I sync leads automatically when my team approves them by hand?”

Not automatically. When you approve a lead by hand, the approval dialog asks whether to create a new deal, link an existing one, or just approve. Choosing Create new sends it straight away.

Check the lead’s detail page:

  • If it shows an Automatic CRM sync failed banner, your CRM rejected the deal. The banner shows why. See If an automatic sync fails.
  • If it is Pending, it hasn’t been approved yet. It may have been flagged as a duplicate, or come from an affiliate link.
  • If it is Approved with a Connect button, it was approved with Just approve, or creating the deal failed. Click Connect to send it.

Yes, by choosing at approval. Pick Just approve for any lead that shouldn’t go to your CRM. There are no rules that filter leads by partner, type or field value.

Will PartnerPortal create duplicate contacts and companies in my CRM?

Section titled “Will PartnerPortal create duplicate contacts and companies in my CRM?”

It depends on your CRM. Attio always reuses matching companies and people. HubSpot and Salesforce can reuse an existing record when Duplicate Handling is set to Adopt. Pipedrive and Zoho always create new ones. To attach a lead to a deal you already have, use Link existing. See What gets created in your CRM.

If I change a lead in the portal, does my CRM update?

Section titled “If I change a lead in the portal, does my CRM update?”

Only with two-way sync, on HubSpot and Pipedrive, and only for phase, close value and close date. Otherwise, make changes in your CRM and let them sync back. See Two-way sync.

Will I see an error if an update from my CRM doesn’t arrive?

Section titled “Will I see an error if an update from my CRM doesn’t arrive?”

No. Failed updates from your CRM to the portal aren’t shown in the app. If a linked lead stops updating, check that the connection is authorized and that the CRM stage is mapped to a phase, then contact support.