Integration / Salesforce

Sembr for membership. Salesforce for relationships.

Member records flow into Salesforce as contacts linked to accounts. Renewal dates, dues tier, and event participation become fields your CRM team can query.

Join the waitlist All integrations
How it works

One source of truth per concern.

One-way sync

Sembr is the source of truth for membership records. On member create, update, or status change, Sembr pushes the record to Salesforce. Edits in Salesforce do not flow back by design.

Configurable field mapping

Map Sembr fields to any standard or custom Salesforce field. Sembr suggests sensible defaults (name, email, tier, join date, renewal date, dues paid YTD). Sensitive fields can be excluded.

Contact and Account objects

Members can sync as Salesforce Contacts linked to an Account (the organization), or as standalone Contacts. Your Salesforce admin picks the object model during setup.

Status: post-launch.

Salesforce is a heavier integration than accounting or marketing tools. It requires careful data model alignment per tenant, and NPSP (Nonprofit Success Pack) has a different object structure from standard Salesforce. Post-launch timeline: standard Contact/Account first, NPSP support following after the standard release is stable. Targeted Q4 2027 or later.

Join the waitlist All integrations
# Standard Salesforce (first release)
> member.create -> Contact + Account
> member.update -> Contact field push
> member.lapsed -> Opportunity: lost
> member.renewed -> Opportunity: closed/won
# NPSP (follows standard release)
> Household + Affiliation model
FAQ

Common questions.

Does this work with Salesforce Nonprofit Cloud (NPSP)?
NPSP support is on the post-launch roadmap, sequenced after the standard Contact/Account integration is stable. The Household, Affiliation, and Soft Credit objects in NPSP need careful mapping rather than a generic field push. If your organization runs NPSP, flag it on the waitlist form so we can track demand.
Is this an AppExchange managed package?
The initial release is API-based using standard Salesforce REST and OAuth. A managed package on AppExchange is post-launch scope, once we have enough Salesforce-running tenants to justify the security review process.
Can we control which Sembr fields go to Salesforce?
Yes. Field mapping is configurable per tenant. You choose which Sembr fields to push and which Salesforce fields they target. Sensitive fields (member notes, internal risk flags) can be excluded from the sync entirely.
What about organizations that use Salesforce for both CRM and fundraising?
The integration covers membership records. If your Salesforce setup includes fundraising (Opportunities linked to donors), those flows are independent. Sembr does not touch fundraising objects. The integration is scoped to member records only.

Membership ops in Sembr. Relationship management in Salesforce.

Both tools doing what they are built for.

Join the waitlist All integrations