Why an Opportunity in Salesforce did not sync to WeGive

If you have Opportunities in Salesforce that you expect to see in WeGive but they are missing, the most common cause is one of a small number of data conditions on the Opportunity or its related records. This article gives Salesforce admins a checklist to work through on a specific Opportunity before escalating to WeGive support.

This article is written for orgs using Salesforce NPSP. Field names below use NPSP API names so you can search them on the Opportunity record.

How to use this checklist

Pick a single Opportunity that did not sync. Work through the checks in order. The first check that fails is almost always the reason. Once you find a pattern across multiple Opportunities, you can fix the underlying data issue in bulk.

Quick-pass requirements

At a glance, every Opportunity that syncs to WeGive meets all of these conditions:

Each of these is explained in more detail below.

Checklist

1. Does the Opportunity have a Payment with Paid = TRUE?

Most WeGive orgs sync transactions from the Payment object, not directly from the Opportunity. Open the Opportunity and look at the related Payments list.

• If there are no Payment records, the Opportunity will not sync. NPSP normally creates a Payment automatically when an Opportunity is moved to Closed Won, so a missing Payment usually means the Opportunity never made it to Closed Won, or a workflow blocked Payment creation.

• If there is a Payment but npe01__Paid__c is FALSE, the Opportunity will not sync. Mark the Payment as paid and it will pick up on the next sync.

2. Is there a Contact or Account on the Opportunity?

Open the Opportunity and confirm at least one of these fields is populated:

• ContactId (for individual donations, typically via the NPSP Primary Contact)

• AccountId (for organization donations)

If both are blank, the Opportunity has no owner and WeGive cannot attach the transaction to anyone. This is one of the most common reasons a recent Opportunity does not appear.

3. Does that Contact (or Account) already exist in WeGive?

Even if the Opportunity has a Contact, that Contact must already be synced to WeGive for the Opportunity to attach. Search for the Contact in WeGive by name or email. If the Contact is not there:

• Check whether the Contact has an email address in Salesforce. If your org has the Contacts with emails only setting enabled (most do), Contacts without an email never sync to WeGive, and any Opportunity attached to that Contact will be skipped.

• Add an email to the Contact in Salesforce, wait for the next Contact sync, and the Opportunity will follow.

For organization gifts attached by AccountId, the Account must already be synced to WeGive. Accounts sync as supporters of company type.

4. Is the household linked correctly?

For Contacts on NPSP, the Contact's Household Account must also have synced to WeGive. If the Household is missing, the Contact sync can fail, which in turn prevents the Opportunity from syncing.

Open the Contact, look at the Account Name field, and confirm the Household Account exists. If the Account is brand new and has not had time to sync yet, give it a sync cycle and recheck.

5. Is the individual vs. organization flag correct?

Check npe01__Is_Opp_From_Individual__c on the Opportunity.

• For donations from an individual, this should be TRUE and the Opportunity should have a ContactId.

• For donations from a company, this should be FALSE and the Opportunity should have an AccountId.

If this flag does not match the owner type that exists in WeGive (for example, the Opportunity is flagged as individual but only the company Account is in WeGive), the Opportunity will not attach.

6. Is the Record Type one the integration can see?

The WeGive integration user in Salesforce needs field-level and Record Type access to the Opportunity. If your team added a new Opportunity Record Type and did not grant the integration user access, Opportunities of that Record Type will silently skip.

Open the Opportunity, note the Record Type, and confirm the WeGive integration user's profile or permission set has access to it.

7. Is the Opportunity inside the sync window?

WeGive's incremental sync looks at Opportunities by LastModifiedDate. If the Opportunity was created or last modified outside of the active sync window (for example, a backfill of very old records imported with a past LastModifiedDate), the regular sync will not pick it up. In that case, contact WeGive support to schedule a targeted backfill.

8. Has the Opportunity been manually added to the Ignored Integrations list?

WeGive has an Ignored Integrations list under Settings → Integrations that excludes specific records from sync. Records are added to this list manually (typically by WeGive support during prior troubleshooting), not automatically based on failure counts. If a record is on this list, it will not sync even after the underlying data is corrected.

If you have fixed the data on an Opportunity and it still does not appear after the next sync cycle, ask WeGive support to check whether the record is on the Ignored Integrations list for your org.

WeGive integration config checklist

If the Salesforce-side data on an Opportunity looks correct and the Opportunity still is not syncing, the cause may be on the WeGive side, in the Salesforce integration configuration. Org admins can review these settings under Settings → Integrations → Salesforce. If you do not have access, ask WeGive support to verify them.

The settings most likely to cause an Opportunity to be filtered out or misrouted:

Common config-side patterns

If you suspect a config-side cause but do not have access to change these settings, escalate to WeGive support with the specific setting you want verified and the symptom you are seeing.

What to send to WeGive support if you have checked everything

If you have walked through this checklist and the Opportunity still is not in WeGive, escalate with:

• The Salesforce Opportunity 18-character ID

• The related Contact's 18-character ID and email

• The related Account's 18-character ID

• The Payment record ID and whether npe01__Paid__c is TRUE

• A note confirming you have already walked through this checklist

That gives WeGive support enough to look at the sync logs for that exact record without going back and forth on the basics.

Common patterns and what they usually mean

Once you have walked through a handful of missing Opportunities, you will often see a pattern. A quick guide to common patterns: