Allow any changes made in Every HR, from absences, contract changes and address changes, to be synced back into Arbor. Any changes to Arbor to be reflected in Every HR after the initial sync.
Admin
Julia Vekrikas
Dec 1, 2025
Thank you for submitting your idea. We are excited to let you know that the development is in progress. We’d like to share the current direction and clarify how the integration will work. Please note that development is still in progress, so some details may evolve as the design is finalised.
Vision & Core Principles
Our goal is to streamline data flow between EveryHR and Arbor by making EveryHR the single source of truth for both employee and absence information.
Arbor (MIS) will receive the operational data it needs via writeback in near real time, ensuring schools maintain accurate records without duplicating effort across systems.
Planned System Capabilities
EveryHR as the Primary Data Source
Employee details and absences will be created and maintained in EveryHR.
Arbor will receive selected data fields from EveryHR for operational needs such as cover and identity management.
Once the integration is live, changes made in Arbor won’t sync back—updates will need to happen in EveryHR.
Initial Data Import for New EveryHR Customers
New customers will be able to complete an initial import of core employee data from Arbor into EveryHR.
After go-live, updates from the MIS to EveryHR will no longer be supported.
All ongoing employee and absence management will occur within EveryHR.
We hope this provides clarity on the integration approach. If you have any further questions or need additional details, please don’t hesitate to reach out.
Thank you for submitting your idea. We are excited to let you know that the development is in progress. We’d like to share the current direction and clarify how the integration will work. Please note that development is still in progress, so some details may evolve as the design is finalised.
Vision & Core Principles
Our goal is to streamline data flow between EveryHR and Arbor by making EveryHR the single source of truth for both employee and absence information.
Arbor (MIS) will receive the operational data it needs via writeback in near real time, ensuring schools maintain accurate records without duplicating effort across systems.
Planned System Capabilities
EveryHR as the Primary Data Source
Employee details and absences will be created and maintained in EveryHR.
Arbor will receive selected data fields from EveryHR for operational needs such as cover and identity management.
Once the integration is live, changes made in Arbor won’t sync back—updates will need to happen in EveryHR.
Initial Data Import for New EveryHR Customers
New customers will be able to complete an initial import of core employee data from Arbor into EveryHR.
After go-live, updates from the MIS to EveryHR will no longer be supported.
All ongoing employee and absence management will occur within EveryHR.
We hope this provides clarity on the integration approach. If you have any further questions or need additional details, please don’t hesitate to reach out.
Thank you
EveryHR Product Team
It would be very useful to have a two-way sync to save our teams from double-entry of data