SIS Integration: Start Here
Last updated: Oct 27, 2026
New to SIS integration? You do not need to understand the technical setup before you start.
First identify the people who will actually do the work. Then contact [email protected]. SIRAS can help your team identify the correct setup path and the articles each person should use.
First identify the people who will actually do the work. Then contact [email protected]. SIRAS can help your team identify the correct setup path and the articles each person should use.
What do you need to do?
| I don't know anything about this yetStart here. Identify the doers, contact SIRAS, then assign the setup tasks. | We use AeriesChoose the Aeries path for a new implementation or an integration already running in Production. |
| We use another SISUse the file-based integration path for PowerSchool, Q, SchoolWise, School Pathways, Synergy, or another SIS program. | Our integration already existsSee what a live integration can update, understand a “System” change, or troubleshoot a problem. |
I Don't Know Anything About This Yet
That is a normal place to start. A district does not need one person who understands every part of SIS integration.
Just someone who can follow up locally with those taking part in the project.
Know the context of what the integration is.
A complete integration may involve one or both directions. The district can implement in stages. First testing, review, approval then going live.
SIS → SIRAS
The SIS keeps SIRAS current with demographic, enrollment, school, and contact information updates. Update results may vary.
The SIS keeps SIRAS current with demographic, enrollment, school, and contact information updates. Update results may vary.
SIRAS → SIS
Where the SIS supports it, SIRAS can provide current Special Education and, when applicable, Section 504 information back to the SIS. Service information is also available for local SIS use as well. With this information, the SIS can know IEP status or recently exited from IEP. Possibly 504 as well but requires more setup.
Where the SIS supports it, SIRAS can provide current Special Education and, when applicable, Section 504 information back to the SIS. Service information is also available for local SIS use as well. With this information, the SIS can know IEP status or recently exited from IEP. Possibly 504 as well but requires more setup.
Many districts function with one way integrations to SIRAS only, even with Aeries. That is a local decision but is a real time saver if implemented.
Districts doing SIRAS best practice dedicate someone to daily monitor the integration logs. It only takes a few minutes to see if there is anything to follow up with.
The first job towards completing the SIS/SIRAS integration is to identify who can do each part.
1. Identify the doers
| Who you may need | What that person helps do |
|---|---|
| District integration coordinator | Directly works with SIRAS to keep the setup moving. Knows who the local contacts are, and coordinates questions or approvals with SIRAS. This may be the SEDS Coordinator, SPED administrator, SIS administrator, or even SELPA. |
| SIS / Aeries administrator | Works inside the district SIS. For Aeries, this person can create the SIRAS API Certificate/key and configure the Aeries Special Ed Data Import. For other SIS products, this person helps produce or consume the required integration files. |
| SIRAS / SPED / SEDS administrator | Knows the district's Special Education records and can review whether the information arriving in SIRAS or returning to the SIS looks correct. This person is also a good candidate for ongoing integration monitoring. |
| IT / network / SFTP support | Helps when secure file transfer, firewall, network access, or an SFTP client requires technical support. Some districts will not need a separate person for this role. |
| SIRAS Support | Helps the district choose the right integration path, configures the SIRAS side when needed, assists with Training review, and helps the district investigate integration problems. |
One person may fill several of these roles.
The goal is not to create a large project team. The goal is to know who can perform each task when it is needed.
The goal is not to create a large project team. The goal is to know who can perform each task when it is needed.
2. Need Help? Contact SIRAS
Email [email protected] and tell us:
- your district/LEA;
- which SIS you use or are moving to;
- whether this is a new SIRAS implementation or a change to an existing integration; and
- who the local doers are, if you already know them.
Do not email passwords, API Certificates/keys, or other secret credentials.
When a credential needs to be delivered to SIRAS, use the secure method identified in the applicable setup article.
When a credential needs to be delivered to SIRAS, use the secure method identified in the applicable setup article.
3. Give each doer the article for their task
| Aeries setupAeries–SIRAS Implementation: Configure, Test & Go Live Use for the district's complete Aeries setup, testing, scheduled-import activation, Training review, and Production handoff. |
Other SIS productsFile-Based SIS Integration: Implementation Guide Use for PowerSchool, SchoolWise, School Pathways, Synergy, and other file-based SIS integrations. |
| SFTP / secure file transferSIRAS SFTP: Secure File Exchange & Connection Settings Use when a doer needs to test SFTP access, understand connection settings, or securely exchange integration files. |
Established integration problemSIS Integration Troubleshooting & Ongoing Monitoring Use after an integration has been established and a scheduled job, file, or expected update is not working as expected. |
You are ready to move forward when:
You know which SIS path applies, the people doing the work know their part, and SIRAS knows who to coordinate with. The technical setup can then be completed one task at a time.
You know which SIS path applies, the people doing the work know their part, and SIRAS knows who to coordinate with. The technical setup can then be completed one task at a time.
We Use Aeries
Use Aeries–SIRAS Integration: Start Here when you need the Aeries-specific big picture or are not sure which Aeries article fits.
| We are setting up or rebuilding the Aeries integrationConfigure both directions, test in Training, verify the Aeries completion email, enable scheduled processing, and approve Production. | Our Aeries integration is already liveUse the Production monitoring routine for Aeries completion emails and Aeries → SIRAS API evidence. |
| We need to know what Aeries may update in SIRASUse the Aeries → SIRAS field/default/mapping reference. | Something is not working or the result looks wrongUse the troubleshooting workflow after you identify an exception. |
We Use Another SIS
For PowerSchool, Q, SchoolWise, School Pathways, Synergy, or another non-Aeries SIS, start with File-Based SIS Integration: Implementation Guide.
Product-specific extraction and import capabilities vary. Use SIRAS file specifications for the data being exchanged and contact [email protected] when you need help determining the correct vendor-specific path.
| Task | Reference |
|---|---|
| Send demographic data from the SIS to SIRAS | Data Import: Demographic File Specification |
| Send contact data from the SIS to SIRAS | Data Import: Contact File Specification |
| Send Special Education / Section 504 data from SIRAS to the SIS | Data Export: Special Education and Section 504 Data from SIRAS to SIS |
| Securely exchange files | SIRAS SFTP: Secure File Exchange & Connection Settings |
Our Integration Already Exists
Once an integration is established, the district should know who reviews its scheduled-task logs, completion emails, or other recurring results.
- Aeries is live and you are doing the normal recurring review: use Aeries–SIRAS Production Monitoring.
- Aeries is already live and you want to know what it may update in SIRAS: use Aeries to SIRAS API Reference: Fields, Defaults & Optional Mapping.
- Student History shows “System” as the updater: use Student History Help to understand automated background updates and where to investigate next.
- An expected update stopped working or the result does not make sense: use SIS Integration Troubleshooting & Ongoing Monitoring.
Monitor logs for errors or warnings.
Assign an ongoing owner for integration monitoring. For Aeries, use Aeries–SIRAS Production Monitoring; for other SIS workflows, review the applicable logs or completion evidence on the district's established cadence.
Assign an ongoing owner for integration monitoring. For Aeries, use Aeries–SIRAS Production Monitoring; for other SIS workflows, review the applicable logs or completion evidence on the district's established cadence.
