Bevy can sync community data one-way to Salesforce as Leads and Campaigns. The native Salesforce integration in General Settings remains supported for communities still on that connection, including Salesforce Professional Edition and customers on other Salesforce editions who have not been moved. Communities with the Salesforce card enabled can connect from Settings → Integrations by signing in to Salesforce.
Bevy’s Salesforce integration keeps your CRM current with community activity by syncing selected Bevy objects one-way into Salesforce. There are two supported connection paths:
| Path | Who uses it | Where you connect |
|---|---|---|
| Native Salesforce integration | Customers already connected this way. That includes Salesforce Professional Edition and customers on other Salesforce editions who have not been moved. | Admin dashboard → General Settings → Salesforce section. You enter the instance URL, username, password, and security token. |
| Integration Suite | Communities whose Salesforce card is available under Integrations | Admin dashboard → Settings → Integrations → Salesforce. You sign in to Salesforce and choose Allow. |
Note: The native Salesforce integration is not deprecated. Customers on that path should continue to use native setup and the object sync articles until Bevy communicates a change for their community. That includes Salesforce Professional Edition and customers on other Salesforce editions who have not been moved.
Salesforce is retiring the username, password, and security token sign-in that the native connection uses. On the Integration Suite path you sign in to Salesforce and choose Allow. If you do not see a Salesforce card under Settings → Integrations, contact your Customer Success Manager. Bevy turns that card on for your community.
Important: If your community already uses the native connection, leave it in place. Do not turn it off yourself. Bevy turns the native sync off only after the Integration Suite connection is verified for your community, so both do not keep writing to the same Salesforce organization.
Supported sync objects
On the native Salesforce integration, sync is one-way from Bevy to Salesforce. Each Bevy instance must connect to its own Salesforce organization.
| Bevy object | Salesforce object |
|---|---|
| Users | Leads |
| Attendees | Leads |
| Events | Campaigns |
| Chapters (groups) | Campaigns |
| Chapter members | Leads |
Important: Connecting multiple Bevy instances to the same Salesforce org is not supported. See the FAQs for details.
Sync is one-way from Bevy to Salesforce. Changes made in Salesforce do not sync back to Bevy.
How does it work?
On the native Salesforce integration, Bevy matches people and campaign membership like this:
- If Bevy finds a Contact in Salesforce for the email, it uses that Contact and updates it with mapped data, then associates it with the event campaign.
- If there is no Contact, Bevy searches for a Lead. If one exists, it updates the Lead with mapped data and associates it with the event campaign.
- If no Lead exists, Bevy creates a Lead, applies mapped data, and associates it with the event campaign.
- If a Campaign Member already exists, Bevy updates that record with the new changes.
You can define create versus update behavior on a per-field basis. For example, you can send first name only when creating a new Lead, and skip overwriting first name on existing records. Work with Bevy Support to configure those rules for your mappings.
Integration Suite connection
When your community uses Settings → Integrations → Salesforce, Bevy sends a record within a few minutes of it being created or changed in Bevy. Only records created or changed after you connect are sent. Contact Bevy Support if you need existing records sent. Connection steps are in Salesforce integration - Connect Bevy to Salesforce.
| In Bevy | In Salesforce | How it is matched |
|---|---|---|
| Member | Lead, or the existing Contact | By email. An existing Lead or Contact is updated. Otherwise a new Lead is created. |
| Event | Campaign | Created on the first sync, then the same Campaign is updated. |
| Chapter | Campaign | Created on the first sync, then the same Campaign is updated. |
| Event registration | Campaign Member on the event’s Campaign | Status Registered, unless you choose another status in the setup wizard. |
| Chapter membership | Campaign Member on the chapter’s Campaign | Status Joined, then Departed when they leave, unless you choose other statuses. |
You choose the field mapping and the Campaign Member statuses in the setup wizard. On the Salesforce side you can type a field name, including a custom field. On the Bevy side you pick from the list. If a Bevy field you need is not on the list, contact Bevy Support.
If you are moving from the native connection:
- Enter the field mapping again in the wizard. The native mapping does not carry over.
- If you do not map a Company field, new Leads use Bevy User as the company. The native connection used N/A.
- When you map whether a member is subscribed to the Global Newsletter, Bevy updates that Salesforce field when the subscription changes. The update continues after Bevy turns the native sync off. If that field is not on the Bevy list in the setup wizard, contact Bevy Support.