Six Steps to SFTP

GiveCampus uses secure file transfer protocol (SFTP) to allow Partners using GiveCampus Volunteer Management (GC VM) to provide our team with files containing data about volunteers and constituents, and to automatically transfer updated GC VM data back to our Partners on a nightly basis.

Getting Started with SFTP

Get data-ready by following these easy steps to start using SFTP:

1. Select and install a third-party FTP provider

While GiveCampus is not affiliated with any one provider, Partners have used FileZilla and Cyberduck successfully in the past (bonus points: both are free!).

2. Set up SFTP credentials in your School Dashboard

Note: The Data Management menu, which includes Received Files and Import History, is visible only to Volunteer Management administrators with Full access. If you don’t see this menu, ask your institution’s Full-access Volunteer Management administrator to review file receipt and import status on your behalf.

3. Configure your FTP provider with the new server details

Update your existing SFTP application or automation to connect to the new server:

• Protocol: SFTP
• Server: securetransfer.givecampus.com
• Port: 22
• Username: generated by GiveCampus
• Password: generated by GiveCampus (if using the Username/Password method)
• SSH Private Key: required if using the Public SSH Key method

4. Upload files to the correct folder structure

• Files for Volunteer Management imports should be uploaded to: to_givecampus → vm
• Daily exports from Volunteer Management will be available in: from_givecampus → vm

5. Upgrade to the new SFTP server in VM settings

Go to your School Dashboard and navigate to School Dashboard → Integrations → SFTP Access.

Note: The Upgrade to new SFTP server button appears in the Data Import Files section only after you've created at least one SFTP credential in School Dashboard → Integrations → SFTP Access. If you see a prompt to configure credentials instead of the upgrade button, complete Step 2 first and then return here.

6. Test your connection and upload files

Once you have the new SFTP credentials configured, test your connection and upload your first files to ensure everything is working properly.

Important Notes About SFTP Server Migration

Legacy SFTP Server Deprecation: As of March 2, 2026, GiveCampus deprecated the legacy SFTP server (sftp.givecampus.com) for Volunteer Management file imports. All schools must now use the unified self-serve SFTP system.

File Naming Conventions: This change does not affect your file naming conventions—only the server and folder location where you upload your files.

Troubleshooting SFTP Connection Issues

Can't connect to the new server?

• Check that you're using the correct server address: securetransfer.givecampus.com
• Ensure you've clicked "Upgrade to new SFTP server" in VM settings
• The importer will not see files already on the server, so reupload files after upgrading

Quick self-diagnostic checklist — if you can’t connect to SFTP

Before escalating issues, run through these steps using the exact admin UI labels.

1. Check SFTP credentials:

2. Verify connection settings in your FTP client:

   • Confirm you are using these settings:
     • Server: securetransfer.givecampus.com
     • Port: 22
     • Protocol: SFTP
   • Note: The legacy host (sftp.givecampus.com) was deprecated. Update your configuration if necessary.

3. Confirm your VMS migration step:

   • In your VMS admin, open Volunteer Management → Settings.
   • In the Data Import Files section, ensure you clicked Upgrade to new SFTP server. Without this, the importer will ignore files on the new server.

4. Check the file upload directory:

   • Upload import files to the exact folder: /to_givecampus/vm/ (the vm subfolder is required).
   • Daily exports are delivered to: /from_givecampus/vm/.

5. Re-upload files if needed:

   • Files uploaded before clicking Upgrade to new SFTP server will not be processed. Re-upload these files after completing the migration.

6. Verify file receipt in GiveCampus:

   • Open Data Management → Received Files in VMS admin. Your file should appear within a few hours. If it does not, check the host, port, folder, and transfer completion.

7. Review importer status and errors:

   • Open Data Management → Import History to check if the importer is active and review any errors. A paused importer will stop processing new files.

8. Identify common root causes:

   • Missing SFTP credentials: Verify that the credential exists.
   • Incorrect server/port: Check your client’s connection log for the attempted host.
   • Skipped migration step: Confirm that the Upgrade action was taken in the Data Import Files section.
   • Wrong folder path: Files uploaded to /to_givecampus/ or /school_data_importer/ will not be processed.
   • Pre-upgrade files: Files from before the upgrade must be re-uploaded to initiate processing.

9. Final check:

   • If Received Files shows your upload and Import History indicates active processing without errors, your pipeline is functioning correctly. Otherwise, review steps 1–5 to pinpoint the discrepancy.

Tips:

• Always use the exact folder names (/to_givecampus/vm/ and /from_givecampus/vm/).
• If the client log shows a successful transfer but files are not visible in Received Files, confirm that the correct host (securetransfer.givecampus.com:22) is used.
• After upgrading, re-upload any historical files since they will not be reprocessed automatically.
• Use Import History to quickly review any errors related to file naming, structure, or format.

Files not importing?

• Make sure you're uploading to the correct folder: to_givecampus → vm (not school_data_importer)
• Verify your file names and structure match your original configuration
• Check that you've upgraded to the new SFTP server in VM settings