There are several options that allow integrating Bevy with your Salesforce instance to synchronize the next items:

• Sync Users as Leads
• Sync Attendees as Leads & associate them with the event campaign as campaign members
• Sync Events as Campaigns
• Sync Chapters as Campaigns
• Sync Chapter Members as Leads

The following sections describe these integration options and explain how to set them up.

How does it work?

A summary of how Bevy's Salesforce integration works.

• If we find a contact in Salesforce, we'll use it and update the contact with data we have mapped.
• Then, we'll associate that contact with the event campaign.
• If there is no contact, we'll search for a lead. If there is one, we'll use it, and update it with the data we have mapped.
• If there isn't an existing lead, we'll create a new one and update the data we have mapped.
• Then we'll associate the lead with the event campaign.
• If an existing campaign member already exists, we'll update that record with the new changes.

You have the flexibility to dictate create/edit behavior. We support defining on a per-field basis whether it should update an existing record or not.
Ex: If when finding an existing lead you don’t want to change the first name, we can set that up, so the first name would only be sent when creating a new lead.
If you are not wanting to replace data on existing records, Bevy has the functionality to allow defining what data should be sent to create and/or update when syncing with Salesforce.