SFTP destination, shared unit files, and parent class years

For the established (legacy) Volunteer Management portal. These steps differ from the newer Volunteer Management interface. Administrator controls require the appropriate school or volunteer-management permissions.

Deliver VMS files to the configured GiveCampus SFTP connection and VMS destination. This differs from the school-data-importer destination. If you need GiveCampus to retrieve files from your own SFTP server, ask the integration team to review the requirement before changing your delivery arrangement.

In VMS Settings, Data Import Files displays the configured filenames and required columns and offers a CSV header download. Headers must match the configured specification exactly. Coordinate a server migration with IT and support because it changes the read/write location; do not switch it merely to troubleshoot a missing row.

A shared file can be filtered into units using a configured unit column and unit name. The row value must match that configuration: do not assume the literal values alumni and parents, or a universal column called unit code. Confirm both units' specifications and constituent keys with support before repeating a person across rows. A person who is both an alumnus and a parent needs the agreed representation in each applicable unit, not an invented duplicate identifier.

The child's expected graduation year and the parent's own alumni class year are different data. Have the school's CRM team provide the intended parent-unit value and confirm its destination field in the import mapping. The import does not confirm automatic graduation-year calculation from a student's grade. Do not replace the person's alumni class year simply to represent a parent relationship.