This article covers automated SFTP data exports from AwardSpring. To send student data into AwardSpring instead, see SIS Integration FAQ; to export via API, see SpringAPIs & Webhooks Overview.
Overview
An automated data export sends a report out of AwardSpring on a recurring schedule. AwardSpring generates a CSV file, up to once per day, and leaves it on the AwardSpring secure SFTP server. AwardSpring does not send the file to the institution. The file remains on the AwardSpring server, and the institution's IT team (or another system) sets up a scheduled job to retrieve the file and load it into the receiving system, such as a financial aid, finance, or reporting system.
An export is scoped much like a custom report. The institution defines which students and data points to include, and AwardSpring builds the report and the SFTP connection.
File delivery: AwardSpring does not email, upload, or push the export to institutional systems. The institution receives the file only when its retrieval job connects to the AwardSpring SFTP server and downloads it.
Compared with in-app reports: Reports downloaded from the platform are one-time, manually generated files. Automated exports run on a schedule and don't require manual initiation.
Separate from imports: If your site also uses SIS integration, the export has its own SFTP username and folder.
Cost and availability: Automated exports are included with the Enterprise tier or the Integrations add-on, which bundles automated SIS integrations, SSO, and SpringAPIs. Customers with existing automated SIS imports also have access to automated exports.
Timeline: Allow about one month from your request to your first file, covering the SFTP connection setup, the report definition, and the build. The build itself takes about 7 to 10 business days once the report definition is final. How quickly IT sets up the retrieval job also affects when you receive your first file.
If something goes wrong: If a file is missing or looks wrong, contact AwardSpring Support.
Task | Owner |
Request the export and choose a connection method (SSH key or password) | Scholarship Admin and IT |
Set up the SFTP folder and confirm IT can connect | AwardSpring and IT |
Decide which students and data the export includes | Scholarship Admin and IT |
Submit the report definition to AwardSpring Support | Scholarship Admin |
Build the report and the automated file drop | AwardSpring |
Build the job that retrieves the file and loads it | IT |
Review the first files | Scholarship Admin and IT |
Getting started
Step 1: Set up the SFTP connection
Contact support@awardspring.com to request an automated export, and tell AwardSpring Support your connection method: an SSH public key (recommended) or an AwardSpring-generated password.
AwardSpring sets up your export SFTP folder and username. Your IT team then confirms it can connect (see Connection details below). AwardSpring can place a sample file on the server so IT can test access and retrieval.
Step 2: Submit the report definition
Once the connection works, send AwardSpring Support the following information:
Use case: The export’s intended use and the destination system that will ingest it.
Population: Which students to include (for example, awarded students only, or all students who applied).
Data points: The exact columns required.
Frequency: How often the file should refresh (up to once per day).
Cycles: Which award cycles to include, and when a past cycle can be removed.
Step 3: AwardSpring builds the export
AwardSpring builds the report and the automated file drop. Allow about 7 to 10 business days for the build once the report definition is final.
Example report
A typical export for a financial aid office lists awarded students with one row per award. Columns are selected when the report is defined. Commonly requested data points:
Student ID | Last Name | First Name | Scholarship Name | Fund ID | Award Amount | Award Cycle | Application ID |
A19001 | Ellison | Naomi | First Gen Forward Award | GEN-005 | 1000 | FY2026 | 8416846297 |
Include an Award Cycle field when the file includes more than one cycle. Application ID uniquely identifies each award and is included when needed.
You can add additional data points, such as the number of payments per award or post-award follow-up status, when you define the report.
Choosing what the export includes
The export file is a snapshot of the data on the day it is generated. Its contents depend on two choices made with AwardSpring Support, and each choice affects how changes appear in the file.
Decide both with IT before building the report.
Which students or application statuses are included
Which award cycles are covered
Example configurations
Option | What the file contains | Best for |
Awarded students only | Students who currently hold an awarded status, as of the day the file is generated | A clean list of students to fund |
All applied students | Students who applied, were awarded, or were denied | Tracking every applicant's status in another system |
All students who started or completed the general application | Students who answered at least one application question or submitted the general application | Tracking application completion rates |
Awarded students only. This is a point-in-time view. A student remains in the file as long as they have an awarded status. If an admin later changes the decision (for example, from awarded to denied or back to applied), the student is removed from the next file. The file does not include a removal flag, so it does not explicitly signal that a student was removed.
All applied students. Students remain in the file for the whole cycle, and their status updates in place instead of the row disappearing. Each daily file shows that day's status and does not keep history.
Example. An admin awards a student on 3/13 and changes the decision on 3/14. The 3/13 file shows the student as awarded. If the report is limited to awarded students, the 3/14 file does not include the student.
Detecting changes between files
Each file is a snapshot, so IT can compare the current file with the previous one to find changes. Include a data point that uniquely identifies each award (an application ID) so rows can be matched from one file to the next, even if a scholarship or cycle name changes.
Post-award follow-up status
Post-award follow-ups track requirements students complete after being awarded, such as thank-you letters. Institutions that fund only students who have completed them can:
Filter the file to awarded students whose follow-ups are complete, so the file lists only awarded students who are ready to be funded.
Include the follow-up status as a column and handle it in the receiving system.
Include the follow-up completion date as a column.
Follow-up status | Meaning |
In Progress | The follow-up is actively being worked on by its owner. |
Pending | Work has started but is blocked or waiting on others' input or response, including students. |
Complete | The owning admin has finished their work on the follow-up and closed it. |
Award cycles
Awarding does not always finish within a single cycle. The export can handle cycles in one of the following ways:
All cycles: Includes every cycle, with an Award Cycle column so you can filter records by cycle. Use this when awarding spans cycles, or you need a complete history.
Active cycle only: Includes only the open cycle. If awarding continues after a cycle has ended, extend that cycle's end date until awarding is complete. Otherwise, students are missing from the file.
Last two cycles: Includes the current and previous cycles. Use this when awarding for one cycle is still in progress while the cycle is open. Include the cycle name column.
You can edit award cycle names in the platform. If the receiving system matches on cycle, also request the cycle ID, because the ID does not change when the name changes.
Connection details
Item | Detail |
Host |
|
Port | 22 |
Username | Provided by AwardSpring during setup. It is different from the import username. |
Authentication | SSH public key (recommended) or AwardSpring-generated password |
File type | CSV |
Folder | The file is placed in the top-level folder of your account. Retrieve it from there. |
SSH key: Provide your public key as a single line in the form <key type> <key data>. Accepted types:
ssh-rsa(2048-bit minimum)ecdsa-sha2-nistp256ecdsa-sha2-nistp384ecdsa-sha2-nistp521
Ed25519 is not supported. Share only the public key, never the private key. For full requirements and examples, see SSH Public Key Requirements.
Password: AwardSpring provides the password during setup and does not retain it, so record it in a secure, access-controlled location. If you lose it, contact AwardSpring Support to reset it.
Test connection: AwardSpring can place a sample file on the server so IT can confirm access and retrieval before the first scheduled file is added.
File retrieval
AwardSpring places the export file on the AwardSpring server on the agreed schedule.
Your IT team creates a scheduled job that connects over SFTP, retrieves the file, and loads it into the receiving system.
Each file is a new snapshot. The job should replace or reconcile the previous data rather than append to it.
The most recent file remains on the server after retrieval. Your IT team has delete access to its export folder and can remove files that should not remain there.
An export file contains no rows until students meet the report's criteria. For example, an awarded-students report is empty until awarding begins.
Export file changes
To change the columns, population, cycles, or connection method, contact AwardSpring Support. Coordinate changes with IT first, because column changes can break the retrieval job.
Questions? Contact support@awardspring.com or call 888.258.5628 ext. 2.
