Securly Sync School Year Rollover

Overview

This year Securly Sync is implementing a global pause for all API connections syncing from your SIS (Student Information System).

The global sync pause will affect API syncs from June 5-July 26, 2026. You can request to modify the dates of your sync pause (or remove the pause altogether) by contacting support at support@securly.com

There will be NO impact on SFTP file uploads, they will continue to process upon receipt.

While in an API sync pause, Securly Sync will not process updates from your SIS API, which allow districts to update their SIS data without downstream effects, like interrupting user access.

During the sync pause, whatever data was last synced into Securly Sync (ideally current school year data) will be retained in Securly Sync for the duration of your district’s sync pause.

To prevent disruption to your data in Securly products, we maintain data in Securly Sync and your Securly products year-round, including over the summer. However, in order to prevent data corruption or deletion, we recommend a sync pause while the district is completing the school year rollover. Please note that some SIS may attempt to delete user data during a school year rollover, which is why we are implementing a global pause sync. 

If the district wishes to keep this school year’s data (including, but not limited to classes, users and enrollments) within Securly Sync (and the connected products) over the summer, we advise setting your sync pause to a date before the last day of school. Once the API sync pause has ended, Securly Sync will automatically resume the district's sync via their SIS API connection.

Unless specified otherwise by your district, Securly Sync automatically removes pauses on July 26 to allow the Securly team enough time for data review (e.g. reviewing data changes to confirm they are only related to school year rollover and will not have negative impacts on your Securly products) before the start of school. The 'Sync Pause Start Date' and ' Sync Pause End Date' can be viewed and modified by the Securly Support team on your behalf.

Sync Pause Start

While your district’s SIS API sync to Securly Sync is paused, you can expect the following things to occur:

• Updates to data in your SIS will not sync into Securly Sync during a pause, so changes made in your SIS will not show up in Securly products.This helps prevent user access issues over the summer and into the next school year.

• SFTP files WILL continue to be processed upon arrival, even if the API sync is paused.

  • If you are augmenting SIS API data with file data (instead of all data coming from the file and none coming from an API), only data that matches in the file to the data in Securly Sync from the API will be added to Securly Sync. i.e. if you are sending us via file guardians information for students and the new student guardians arrive via file before your pause sync is over, we will not add the new student’s guardians to Securly Sync until the pause has ended and the new student themselves has been added to Securly Sync from the API.

• Securly can still perform a manual sync from your SIS into Securly Sync during a sync pause. This will bring in any data current in your SIS, even if it’s in the middle of a rollover. Securly will still review data from any manual syncs to ensure it doesn’t interrupt access for students, teachers or admin to Securly products.

• Securly products will still receive data from Securly Sync over the summer, even if a district's SIS sync into Securly Sync is paused.

Sync Pause End

When your district's API pause sync ends, Securly will resume syncing with your SIS (based on your scheduled sync frequency & time). 

If data going to Securly Sync changes significantly once the sync resumes, your sync will be placed in a “circuit break” as a safeguard to allow us time to review the data changes before they are processed. During this busy season circuit break reviews can take more time than usual to complete. We encourage you to edit your pause schedule to unpause once your school year rollover or summer school is complete to ensure your data is reviewed and approved before school starts.

Files that augment data to the API data will not automatically reprocess after the API sync pause is over. The next file that is received after the API sync pause has ended will augment the information in the file to your API data.

Pause Date Selection

Admins can request adjustments to the ‘Sync Pause Start Date' and 'Sync Pause End Date' from Securly Support. 

*If you will be using Securly products like Classroom, Pass or Flex during summer school, we want to handle your pause dates strategically to ensure your summer school rostering information is up-to-date in Securly Sync and these products. 

We recommend the following settings for your dates:

• Pause Start Date: This will be the first day your sync goes on pause, which should coincide with the last day of the current school year’s correct data.

  • Please note: Your current school year data should still be active in your SIS on this day.

  • Summer School specifics: If your summer school starts BEFORE your school year rollover, your sync pause start should start on the last day of your summer school schedule to ensure our products receive all of your summer school rostering information. If your summer school starts AFTER your school year rollover, your pause should follow the general pause start date recommendations, i.e. the last day of your current school year.

• Pause End Date: This will be the last day your sync is paused, which should be the day your SIS data is active for the upcoming school year. 

  • For example: If next school year's data will be active in your SIS on 8/15/25, your Pause End Date should be set for 8/15/25. This might also be your last day of summer.

  • Summer School specifics: If your summer school starts BEFORE your school year rollover, your sync pause end should follow the general pause end date recommendations, i.e. the day your data becomes active for next school year. If your summer school starts AFTER your school year rollover, your sync pause end date should be before summer school starts, but after the rollover is complete to ensure our products receive summer school rostering information. 

Sync pauses apply to the uniquely scheduled sync time for your district (most are set between 7-11pm local time, however some are scheduled for early morning hours) The sync pause start would then begin at the specified time (most likely evening) and the pause end date would resume syncs on the evening of that date, local time. For example, if you wish to resume syncing with Securly Sync on August 10th, please note that it would most likely sync in the evening of August 10th.

Recommendation: If possible, we recommend unpausing your district's sync a week or two in advance of the new school year to give us time to review the circuit breaks from data changes and address any data concerns before school starts.  

Files

Files received during the global sync pause will still be processed upon arrival. 

If you send files for full rostering data, we recommend you pause the file send in your SIS or SFTP manager during your school year rollover. Please be sure to restart it after your rollover is complete and it sends the exact same files, data, etc. to ensure processing continues as normal.

If you send files to augment your API data, we will process these files upon arrival and augment it to the API data that was available prior to the sync pause. Once the sync pause is over, any new files received will be augmented to the new API data. Prior files will not be re-processed against the new API data after the API sync is unpaused unless a request is placed to Securly Support.

Changing your SIS

If you are changing your Student Information System (SIS), please contact Securly Support to notify us of the upcoming change. Our team will partner with you to create a migration plan and timeline based on your new SIS and available sync methods. Please allow at least 2-3 weeks to complete the migration with Securly Support and our Integrations team. We highly recommend starting this process at least a month before your first day of school.

SyncUI Beta Live

SyncUI will allow you to view the status of Securly Sync retrieving data from your SIS as well as the data within Securly Sync. SyncUI is currently in Beta with new features being added regularly. It is currently only available to Google SSO clients with MFA. You can request access to SyncUI Beta through Securly Support.