Answers about Bevy’s Salesforce sync direction, objects, permissions, and how the native Salesforce integration and the Integration Suite path relate during migration.

Is the Salesforce sync bidirectional?

No. Phase 1 supports a one-way sync from Bevy to Salesforce only. Bidirectional sync is not included in this release. This applies to both the native Salesforce integration and the Integration Suite path.

Which objects does Bevy sync to Salesforce?

Bevy syncs the following objects to Salesforce (both paths):

• Users — synced as Leads
• Attendees — synced as Leads
• Events — synced as Campaigns
• Chapters — synced as Campaigns
• Chapter members — synced as Leads

I already use the native Salesforce integration. Do I need to change anything?

No. Keep using General Settings → Salesforce unless your Customer Success Manager schedules an Integration Suite migration for your community. Object sync articles that reference General Settings still apply to the native path.

I am on Salesforce Professional Edition. Do I need to migrate?

No. Customers on Salesforce Professional Edition remain on the native Salesforce integration. Bevy will communicate any change to this exception separately. Do not migrate Professional Edition customers to the Integration Suite path unless otherwise directed.

Can the native Salesforce integration and the Integration Suite path run at the same time?

Yes. During a migration period, both may coexist. Do not remove or disable the native Salesforce integration unless Bevy’s migration guidance for your community explicitly instructs you to do so.

How do I know which path my community uses?

• If you configure Salesforce under General Settings (instance URL, username, password, security token, and sync checkboxes), you are on the native path.
• If you connect Salesforce under Settings → Integrations with an OAuth Connect flow and field-mapping UI, you are on the Integration Suite path.

If you are unsure, contact your Customer Success Manager before changing either connection.

How often does data sync from Bevy to Salesforce?

Bevy syncs data approximately every five minutes via the Salesforce REST API. That frequency is not configurable. Records sync individually (not in bulk). If a sync fails — for example, if Salesforce returns an API limit error — Bevy retries over the next two days.

What permissions does my Salesforce account need?

Your Salesforce account needs standard read/write permissions for Contacts, Leads, Campaigns, and Campaign Members, and must be marked as a Marketing User. Sandbox users also need sandbox access.

• Native path: Bevy uses a username, password, and security token stored in General Settings.
• Integration Suite path: You authenticate with OAuth instead of storing a password and token in General Settings.

Can I map Bevy fields to my own custom Salesforce fields?

Yes. The integration supports mapping Bevy fields to custom Salesforce fields.

• Native path: Provide Salesforce field API names (and the Bevy fields to map) to Bevy Support. There is no self-serve mapping UI on this path yet.
• Integration Suite path: Review and adjust mappings in the integration setup flow when that UI is enabled for your community. If a mapping is not available there, contact Bevy Support.

Can I sync Ticket Type as part of my integration?

Yes, as a custom field mapping. Provide Bevy Support with the Salesforce field API name you want Ticket Type mapped to.

Can I sync to Contacts instead of Leads?

We can support syncing to Contact records. If Bevy would create a Contact where a Lead already exists, that record may not sync. Alternatively, Bevy can look up Contact first, then Lead, and create a Lead only if none exists. Contact Bevy Support to configure this.

What happens if Salesforce has two records with the same email?

By default, Bevy does not sync those records and does not create the related Campaign Member when pushing a chapter member or attendee. Bevy can optionally use the last-modified Lead or Contact when duplicates share an email. Contact Bevy Support to enable that option for your community.

Can the dates include date and time in Salesforce?

Not on the standard Campaign date fields. Salesforce’s built-in Campaign Start Date and End Date are date-only — they store the calendar day but not the time of day. That is a Salesforce platform limitation, so even when Bevy sends full date and time, Salesforce keeps only the date on those standard fields.

If you need start/end time in Salesforce:

1. Create custom Date/Time fields on Campaign in Salesforce (for example, Event Start Date/Time).
2. Contact Bevy Support to map Bevy event date/time to those custom fields.

After mapping, full date and time sync to your custom fields, while the standard Start/End Date fields continue to hold the date.

How does Bevy prepare data for Salesforce?

Bevy formats values before sending them so they match Salesforce requirements:

• Dates and times: Converted to ISO-formatted strings (for example, 2025-09-22T10:30:00).
• Decimal numbers: Converted to standard floating-point numbers.
• Empty values: Empty or null fields are omitted.
• Campaign names: Names longer than 80 characters are truncated with ... at the end.
• Campaign types: Appropriate campaign type prefixes are added for Events and Chapters.

How are guest (anonymous) registrations synced?

When guest registration is enabled and an anonymous user registers, Bevy looks up a Salesforce Contact or Lead by the email provided. If one exists, Bevy uses it; otherwise Bevy creates a new record. Guest registrations use the same statuses as logged-in attendees: Registered, Unregistered, and Attended.

How can I test the Salesforce integration?

After you configure credentials (native) or complete Connect (Integration Suite), create a few test events and trigger updates. When possible, use a Salesforce sandbox first, then point production at your live org.

Can I switch to a different Salesforce organization after the integration is already running?

Not without updating object mappings. Bevy stores the Salesforce object ID for each linked object (Campaign, Lead, and related records). Those IDs tell Bevy which Salesforce record to update.

When you move to a new Salesforce organization, object IDs change. If Bevy’s stored IDs are not updated, syncs can fail or write to the wrong records.

Contact Bevy Support before you switch orgs so they can:

• Re-link Bevy objects to the corresponding records in the new organization
• Update stored object IDs in Bevy
• Verify mappings before you resume syncs

Plan your Salesforce organization setup carefully before integrating to minimize the need to switch later.

Can I connect more than one Bevy instance to the same Salesforce organization?

No. This is not a supported configuration. Each Bevy instance must connect to its own Salesforce organization. If you run multiple Bevy instances and want all of them in Salesforce, contact Bevy Support before you begin setup so we can help you plan an approach.

Why isn’t connecting multiple Bevy instances to one Salesforce org supported?

The two instances cannot see each other, and they can silently overwrite each other’s data.

Bevy finds people in Salesforce by email address. When Bevy syncs a person, it searches your Salesforce org for a Contact with that email, then a Lead with that email, and uses the record it finds.

Each Bevy instance also keeps its own private record of which Salesforce records it has already created. One instance has no visibility into another instance’s records.

That means a second Bevy instance connected to the same org can find records the first instance created and treat them as its own. Consequences include:

• Data gets overwritten. If the same person exists in both instances, each instance updates the same Salesforce record with its own values. Names, company, and custom mapped fields are replaced by whichever instance synced most recently.
• Syncing can stop without warning. If both instances create a record for the same person at around the same time, your org can end up with two records sharing one email. Bevy treats that as an unresolvable conflict and stops syncing that person, with no error shown in your dashboard.
• You can’t tell which community a record came from. Bevy does not write a community or instance identifier onto Salesforce records. Leads, Campaigns, and Campaign Members from different communities become indistinguishable, and campaign attribution and reporting will be wrong.
• Communities can see each other’s members. A shared Lead accumulates Campaign Member records from both instances, so one community’s members appear in the other community’s campaign reporting.
• API limits are shared. Salesforce API request limits apply to the whole org. Two instances syncing into one org compete for the same daily budget.
• Privacy requests can’t be honored correctly. If a member asks to be deleted in one instance, the shared Salesforce record may still be owned and updated by the other instance.

These effects compound over time, and untangling them requires manual cleanup inside Salesforce that Bevy Support cannot perform on your behalf.

I have multiple Bevy instances. How should I set up Salesforce?

Choose one of the following:

• A separate Salesforce organization per Bevy instance. This is the supported configuration and the only one we can troubleshoot.
• Connect one Bevy instance only. Leave the integration disabled on your other instances.
• Consolidate onto a single Bevy instance if your communities can share one. Contact Bevy Support to discuss whether this fits your setup.

If none of these work for you, contact Bevy Support and describe your setup. We would rather help you plan around this than have you discover data loss later.