Configure and run constituent and gift imports

Start at School Dashboard → Data Import → Import Files. Use the existing configuration for a repeat upload, or the displayed new-data/configuration workflow for a new source. After running an import, open School Dashboard → Data Import → Import History and select the run to review its result.

How to use

Open the platform data/import area, select or create the appropriate file-import configuration, and map the source fields to their intended destinations. Review transformations and identifier handling before running a test or initial import. Use Import History to inspect the resulting run and record-level issues.

GiveCampus supports multiple import-interface versions, direct file uploads, some Salesforce-based configurations, initial/test imports, and full-import options. Use the actual configured source and current interface.

Important distinctions

Import configuration is separate from an import run. The established upload flow excludes configurations already pending/processing from the offered run list. Newer screens can expose progress based on feature access.

Troubleshooting

Record the configuration, source filename, import ID, run state, and a redacted sample of the failing row/error. Do not repeatedly upload the same file to cure an in-progress run or promise every imported record immediately appears in every product.

Import VM2 volunteer assignments

Volunteer assignment imports are released for all VM2 schools as of November 3, 2026. Volunteer roster imports are not yet released. An assignment file connects existing volunteers to constituents; it does not add people to the volunteer roster.

1. Have a school administrator with Data Import access open School Dashboard → Data Import → Import Files and the appropriate new or existing import configuration. VM management access alone does not guarantee access to the school data importer; ask the school's Superadmin if the Data Import area is unavailable.
2. In the configuration's Portfolio Assignments section, set What type of portfolio is this? → Volunteer. Keep Gift Officer imports on their existing product setting; they continue to work as before.
3. Map the assigned constituent's identifier, Portfolio Owner ID (the volunteer's constituent ID), and Role Name (the existing VM volunteer role used for the assignment). Preserve leading zeros and the identifiers used in your constituent data.
4. Confirm that the volunteer already exists in VM and holds that role. The importer rejects missing/ambiguous volunteers or roles and a role the volunteer does not hold. A staff administrator role name is not the volunteer Role Name.
5. Review mappings and run the configured import. Open School Dashboard → Data Import → Import History, select the run and review row-level results before assuming assignments changed successfully.

Later files synchronize the assignments managed by the import. Assignments created in the app are not removed by a file. Do not assume an assignment import replaces every manually maintained assignment or that an arbitrary omitted row clears unrelated assignments.

Add volunteers through Volunteer Management → Volunteers → Add Volunteers first when needed. A future volunteer-roster import and an assignment import require separate files; the released assignment feature does not establish a combined roster-and-assignment upload. Import Segment is different again: it builds a constituent audience, not volunteers or assignments.