Who should own what in an SIS–LMS integration?
Most integration failures are ownership failures. Before choosing an API, decide which system owns people, course structures, enrolments, activities, grades and official outcomes.
An SIS and LMS both contain users, courses and enrolments, but they hold them for different reasons. The SIS governs academic identity and registration. The LMS runs teaching activity. If both systems can create and correct the same record, differences are inevitable.
A good integration is directional by data domain. It also has an exception path for the moments that do not fit the happy path: late registration, merged sections, instructor change, withdrawn learner or grade resubmission.
SIS–LMS ownership map
Authoritative structures move to the LMS; learning evidence and approved outcomes return through governed paths.
Create a domain ownership table
List each object and choose one owner. The SIS usually owns legal identity, institutional identifier, course catalogue, academic sections and official registration. The LMS usually owns learning activities, submissions, feedback and in-course progress.
Grades require more nuance. The LMS may own working scores while the SIS owns the authorised final result. Document the approval boundary and whether grade return is automatic or held for review.
Choose events and reconciliation
A nightly full-file sync is easy to start but slow to correct. Event-based APIs can be faster but still need reconciliation. Use both: timely events for normal operation and a scheduled comparison that finds missing or divergent records.
Every run should report created, updated, unchanged, rejected and unresolved items. 'Sync complete' without counts gives operations no evidence.
Design withdrawal and re-entry
Removing a learner from a course can hide submitted work and feedback. Decide whether withdrawal disables new activity while preserving authorised access to prior evidence. The academic status and the LMS visibility rule are related but not identical.
Re-entry should restore the right context rather than create a second LMS enrolment. Stable identifiers and effective-dated registration events make that possible.
Questions to settle before configuration.
- Assign one owner to every shared data domain.
- Use stable cross-system identifiers.
- Document direction, timing and deletion behaviour.
- Return counts and errors for every sync.
- Reconcile even when events are real time.
- Test add, drop, merge, instructor change and re-entry.
Sources behind this field guide
These links explain the standards, regulations or evidence referenced above. Product choices should still be tested against your institution's own policy and jurisdiction.