The On Suite data sync process is an automatic nightly process which pulls data from the On Suite Products into SchoolAdmin. It can be optionally enabled for any Pro customers currently using the On Suite integration. The goal of this process is to keep the two database systems in sync in regards to demographic data, so schools can avoid having to dual maintain vital contact information between two systems. This integration is meant to be used in addition to the regular On Suite integration, which pushes data from SchoolAdmin to On Suite. 


The data sync must be enabled by the SchoolAdmin client services team. Once the sync is enabled, a new user notification will become available to all admins of the school with the Data permission.  This notification will send an email with the results of the data sync, every time the sync process is run.  To set the data permission, a System Admin will navigate to Settings-->Portal-->Admin Portal Accounts and check the data permission checkbox for all admins that need access.  


Once enabled, the sync process runs every night, at approximately 3:30 AM Central and will pull a list of all contacts updated in the On Suite System since the last time the sync process was run. Then it will compare that list to those contacts within SchoolAdmin. 

If a contact was updated within the same time period within both systems and has different data, the sync process will flag this as a conflict. The notification email will list all conflicts, which must be resolved manually. This is to prevent a situation in which a piece of data was simultaneously updated in both systems.

If a contact was updated in On Suite with different information than is currently in SchoolAdmin and there is no conflict, the sync will overwrite the data in SchoolAdmin with the data from the On Suite system. The notification email will list all overwritten data. 

At this time, the process will sync the following pieces of information:

  • Address_1

  • Address_2

  • City

  • State

  • Zip

  • Country

  • Phone_1_number*

  • Phone_2_number*

  • Phone_3_number*

  • Email

*Keep in mind that phone numbers will write back from BB in the order of home, cell and work. So, home will write into phone_1, cell into phone_2 and work into phone_3.


Can we push Emergency Contacts?

No, unless your school has reserved some of your BB custom fields for this.  Please note, the integration allows for up to 10 custom fields. 

A student was pushed in first batch and sibling was pushed in second batch. Why are they not listed as siblings in ON?

Siblings need to be pushed together in order to be linked in ON. You will need to re-push the siblings to link them in ON.

Relationship linking – what relationships are pushed?

  • Candidate

  • Incoming Student

  • Student

Each role requires specific fields to be pushed to correctly place a student into that role within BB. The OnBoard standard export should be used for Candidates and the OnRecord standard export should be used for Incoming Student/Students.

Our school has both admissions and enrollment in SA and would like to know if we should push into OnBoard or OnRecord. 

It depends on your process. If you need to adjust Candidates (Applicants) within BB before rolling them over in BB, you should push into OnBoard. If your entire process from admissions to enrollment is done within SchoolAdmin, you should push into OnRecord once students have enrolled.

Relationship linking – what relationships are pushed?

All parents are currently pushed with a relationship of ‘parent’. Siblings are only linked if they are all pushed together.

Additional Resources

Did this answer your question?