Skip to main content

Why did an NGP VAN sync not update a contact?

Check imported NGP VAN identifiers and data. A spreadsheet import does not create a built-in daily sync.

Raise More does not currently provide a built-in daily NGP VAN sync. An NGP VAN ID on a contact is an identifier, not evidence that the contact is connected to an automatic sync.

If you expected an edit in NGP VAN to appear automatically, check how the data was brought into Raise More. A spreadsheet import does not keep the two systems connected.

Check the imported data

  1. Open Contacts and find the person.

  2. Open the profile and check its contact details and external identifiers.

  3. Compare the profile with the spreadsheet you imported.

  4. Open Import & Export to review the import result and any errors.

Bring in updated information

Export the current data from your source system, then use the appropriate Raise More import type. Map NGP VAN ID when your file contains it, together with the relevant name and contact fields. Review the proposed import before you approve it.

An import uses Raise More's matching and update rules. Do not assume that every field on an existing contact will be overwritten. You can also edit the contact directly when you only need to correct one record.

If you expected a separate integration

If your organization uses an external integration or custom process, contact support with the contact's NGP VAN ID and the time you expected the update. Do not include API keys or passwords. Support can help identify which process owns the update.

Did this answer your question?