SIS vs LMS: Which System Owns Your Product's Data?
Your demo went well. Then the district's IT lead asks: does it sync with our SIS and our LMS?
A simple yes won't cover it, because the two systems hold different versions of the truth. Instructure's June 2026 announcement of its Edtech Top 40 reports that districts have access to an average of 3,001 digital tools, while students and educators each use an average of four LTI tools in Canvas per year. Instructure links that gap to the burden of managing vendors, licenses, and privacy reviews.
This guide covers SIS vs LMS from the product side: which system owns each record, which standard moves it, and the order to build integrations in. It's a companion to our SIS Ownership Ladder, which helps you decide whether to buy, integrate, extend, or build an SIS.
Building a K-12 product that has to connect to both?
See how we approach SIS and SSO integrations.
See Our Integration Approach →What is the difference between an SIS and an LMS?
An SIS manages the official student record: who is enrolled, in which sections, with what attendance and final grades. An LMS manages the learning itself: content, assignments, submissions, and the working scores teachers give along the way. The SIS answers "who is this student officially?" The LMS answers "what are they doing in class?"
The system of record for enrollment, demographics, schedules, attendance, grades, and transcripts.
The platform that delivers, tracks, and manages instruction, from course materials to quizzes and feedback.
Put simply, the difference between SIS and LMS platforms is student data vs learning data. The two still depend on each other: Edlink, an EdTech integration provider, notes that the SIS is the system of record, but the LMS needs accurate rosters and roles to work.
| Dimension | Student information system (SIS) | Learning management system (LMS) |
|---|---|---|
| Primary users | Registrars, office staff, administrators; teachers for attendance and grades | Teachers, students, instructional designers |
| Core data | Enrollment, demographics, schedules, attendance, final grades, transcripts | Content, assignments, submissions, quizzes, working scores, feedback |
| Record status | Official record | Working record |
| Role in integrations | Roster provider | Launch point and gradebook for connected tools |
| Key standards | OneRoster 1.2 Rostering and Gradebook | LTI 1.3 with LTI Advantage; OneRoster Gradebook |
| K-12 examples | PowerSchool, Infinite Campus, Skyward, Follett Aspen | Google Classroom, Canvas, Schoology |
Is Google Classroom an SIS or an LMS?
Google Classroom is an LMS. It holds 31% of active K-12 LMS implementations, ahead of Canvas at 24%, according to ListEdTech's May 2026 market data.
The integration catch: Google's developer documentation says Classroom add-ons and LTI tools aren't directly compatible. The irony is that Google Assignments and Google Drive were the most widely accessed LTI tools in Instructure's 2026 Canvas data. Yet an LTI integration alone won't reach a Classroom school.
Why does the SIS vs LMS split matter to your product?
The SIS vs LMS split matters because your product sits between two gradebooks. Scores your tool sends land in the LMS gradebook first. In the standard LTI flow, your tool never writes to the SIS at all.
Call it the gradebook trap. The LTI Assignment and Grade Services (AGS) specification lets a tool manage gradebook columns and post scores to the LMS. Moving those scores into the SIS is a second hop your tool doesn't control.
That hop depends on what the district has set up and licensed. Google Classroom can export grades to partnered SIS platforms such as Infinite Campus, Skyward, and Follett Aspen, but Google's help center says teachers need one of three paid Google licenses, such as Google Workspace for Education Plus, to use it.
The practical rule: identity and enrollment flow down from the SIS, and scores flow up toward it. A product that creates students locally risks a second record for a student who already exists in the SIS.
What is the Record Ownership Map?
The Record Ownership Map is a one-page table that assigns every data object your product touches to one system of record, one flow direction, and one standard. Build it before you write integration code. Each row forces a decision you'd otherwise make by accident in production.
| Data object | System of record | Flow direction | Standard or API | What your product should do |
|---|---|---|---|---|
| Users and enrollments | SIS | SIS → LMS → product | OneRoster Rostering (direct or via a rostering hub); LTI Names and Role Provisioning Services | Read; don't create district students locally |
| Classes, courses, sections | SIS | SIS → LMS and product | OneRoster Rostering | Read and store each record's identifier |
| Terms and grading periods | SIS | SIS → LMS and product | OneRoster Rostering | Read; use to scope reporting |
| Assignments (line items) | LMS | LMS ↔ product | LTI AGS line items; Classroom CourseWork | Create or attach per platform rules |
| Activity scores | Product generates; LMS stores | Product → LMS | LTI AGS; Google Classroom API | Post scores, then read results back |
| Term and final grades | SIS | LMS → SIS | OneRoster Gradebook; LMS grade export features | Don't write unless a contract requires it |
| Attendance | SIS | Stays in SIS | Not in OneRoster 1.2's core services | Leave alone unless attendance is your product |
| Content resources | Product | Product → LMS | LTI Deep Linking; OneRoster Resources | Publish links; keep content in your product |
The SIS owns who and when, the LMS owns what happens in class, and your product owns the activity data it creates.
The rows also depend on each other. 1EdTech's specification says any system supporting the OneRoster Gradebook service should also support the Rostering service, because gradebook records reference class and student identifiers. Get roster sync wrong, and grade sync breaks with it.
Want a second set of eyes on your Record Ownership Map before you build?
Talk to our EdTech engineering team.
Talk to Our EdTech Team →Which standards power SIS LMS integration?
Three paths cover the SIS and the two largest K-12 LMS platforms: OneRoster 1.2 for roster and grade exchange with the SIS, LTI 1.3 for LTI-based platforms such as Canvas, and the Google Classroom API. Classroom and Canvas alone account for 55% of active K-12 LMS implementations, based on ListEdTech's May 2026 figures.
| Standard | Hop it covers | What it moves | Build note |
|---|---|---|---|
| OneRoster 1.2 Rostering | SIS → LMS or product | Users, classes, courses, enrollments, terms, grading periods, demographics | CSV and REST exchange |
| OneRoster 1.2 Gradebook | LMS or product ↔ SIS | Line items, results, categories, score scales | Push and pull REST endpoints; needs Rostering |
| OneRoster 1.2 Resources | Provider → classes, courses, users | Resource allocations | Adopt independently |
| Rostering hubs (ClassLink Roster Server, Clever) | SIS → hub → product | Class rosters | ClassLink Roster Server is 1EdTech-certified for OneRoster |
| LTI 1.3 + Deep Linking | LMS ↔ product | Secure launch, content links | Teachers pick your content inside the course |
| LTI Names and Role Provisioning Services | LMS → product | Course roster and roles | Course-level, not district-level |
| LTI Assignment and Grade Services | Product → LMS | Line items, scores | Use platform-created columns or create your own |
| Google Classroom add-ons and API | Product ↔ Classroom | Coursework, attachments, submissions, grades, rosters | Sign in with Google; not LTI-compatible |
OneRoster 1.2. 1EdTech split OneRoster 1.2's REST API into Rostering, Gradebook, and Resources so products can adopt only what they need. Districts may deliver that data directly or through a rostering hub such as ClassLink Roster Server. Our custom SIS development guide covers delta vs bulk roster sync and certification.
LTI 1.3 and LTI Advantage. LTI connects your product to the LMS with single sign-on, grade passback, and deep linking. Canvas's developer documentation says new tools should be built on LTI 1.3 and AGS, and notes that the older LTI 1.1 outcomes service can't return a grade before a student opens the assignment. Our LMS guide for EdTech founders compares LTI with SCORM and xAPI.
Google Classroom. LTI uses a 2-legged flow where consent is implied once an administrator configures the tool. Classroom add-ons use Google's 3-legged OAuth with explicit user consent, and Classroom passes no user or institution details by default.
How should you sequence SIS and LMS integrations?
Sequence by dependency, not by feature request. Rosters come first because gradebook records reference roster identifiers, then LMS launch and grade passback, then Google Classroom, then SIS grade sync.
- List your customers' SIS and LMS pairs. A district running PowerSchool with Canvas needs a different map than one running Skyward with Google Classroom. Build for the pairs in your pipeline.
- Ship rostering first. Consume OneRoster Rostering, directly or through a hub, or read course rosters through Names and Role Provisioning Services if you only launch from the LMS. Store each platform's identifiers, such as OneRoster
sourcedIds, so grade sync can match records later. - Add LTI 1.3 launch and AGS grade passback. Post scores, then read results back to confirm they landed.
- Build Google Classroom as its own track. Budget separate authentication, a Google Cloud project, and a Marketplace listing. Add-ons must meet Google's published requirements before they're approved for listing.
- Add SIS grade sync only when a contract needs it. Where the LMS already exports grades to the SIS, let it, after confirming the district has the licenses that feature needs. Build a direct OneRoster Gradebook connection when a customer's grade-of-record workflow can't run through the LMS.
| Question | Why it matters |
|---|---|
| Which SIS do you run, and does the vendor host it? | Google's help center limits its support for Classroom-to-SIS connections to vendor-hosted SIS deployments |
| How do rosters reach vendors today: OneRoster API, a hub like ClassLink or Clever, or CSV files? | Decides whether you build one OneRoster consumer or several connectors |
| Which LMS do you use, and can LTI 1.3 tools be installed? | Decides whether AGS grade passback is available |
| If you use Google Classroom, do teachers have licenses for SIS grade export? | Google requires one of three paid licenses for that feature |
| Where must final grades end up, and who approves them? | Decides whether you need SIS grade sync at all |
| Which privacy agreement or certification do you require? | 45% of the top 40 LTI tools in Instructure's 2026 report held a 1EdTech or iKeepSafe privacy certification |
For the code-level controls behind district privacy reviews, see our FERPA compliance blueprint.
Frequently asked questions
No, because an LMS gradebook tracks working scores and isn't built to be the official record for enrollment, schedules, attendance, and transcripts. Those records belong in the SIS. Treat the two as separate systems with separate owners, and design your product to read rosters from one and send scores to the other.
Not directly, because LTI Assignment and Grade Services posts scores from your tool into the LMS gradebook. Getting final grades into the SIS is a separate step, handled by the LMS, the SIS, or a sync built on OneRoster's Gradebook service. Map that second hop before promising districts end-to-end grade sync.
Google's developer documentation says Classroom add-ons and LTI tools support similar user journeys but aren't directly compatible, so the answer is no. Add-ons use the Google Classroom REST API and Google OAuth instead of LTI launches. If you sell to K-12 schools, plan Classroom as a separate integration alongside your LTI work.
Yes, for partnered SIS platforms: Google's help center lists grade export for Infinite Campus, Skyward, and Follett Aspen through a OneRoster connection. Teachers need one of three paid Google licenses, and Google limits its support to SIS deployments the vendor fully hosts. Confirm both with the district before you promise grade sync through Classroom.
Start through the LMS unless you need district-wide data. LTI gives you course rosters and grade passback inside classes teachers already use. Integrate directly with the SIS through OneRoster when you need district-wide enrollments, terms, and grading periods, or when a contract makes you responsible for grades of record.
The bottom line on SIS vs LMS
SIS vs LMS looks like a school buying decision. For an EdTech product team, it's a data ownership decision, and every integration choice follows from it.
Map ownership on one page before you write integration code. Then build in order: rosters, LMS launch and grade passback, Google Classroom, and SIS grade sync when a contract calls for it.
Building for districts that run PowerSchool, Canvas, or Google Classroom?
Our EdTech engineering team can pressure-test your Record Ownership Map and integration roadmap before your next district pilot.
Talk to Our EdTech Engineering Team →- Instructure, "New Instructure Data Shows K-12 Districts Are Demanding Evidence, Not Just Access to Edtech Tools," PR Newswire (June 29, 2026) — https://www.prnewswire.com/news-releases/new-instructure-data-shows-k-12-districts-are-demanding-evidence-not-just-access-to-edtech-tools-302812840.html
- Instructure, Edtech Top 40: K-12 Edtech Engagement (SY 2025-26) — https://www.instructure.com/edtech-top40
- ListEdTech, K-12 LMS Market Update & Insights: May 2026 — https://listedtech.com/blog/k-12-lms-market-update-insights-may-2026/
- Google for Developers, Compare Classroom add-ons to LTI tools — https://developers.google.com/workspace/classroom/add-ons/get-started/addons-lti-comparison
- Google for Developers, OneRoster for Student Information Systems — https://developers.google.com/workspace/classroom/sis-integrations/validate-your-SIS
- Google for Developers, Add-on requirements — https://developers.google.com/classroom/add-ons/requirements
- Google for Education Help, Connect Classroom to your SIS — https://support.google.com/edu/classroom/answer/9356588
- Google Workspace Updates, Create new classes in Google Classroom using SIS data (August 2024) — https://workspaceupdates.googleblog.com/2024/08/google-classroom-sis-updates-create-new-classes-import-grading-periods.html
- 1EdTech, OneRoster 1.2 Standard — https://standards.1edtech.org/oneroster/specifications/standards/v1p2
- 1EdTech, Rostering, Resources, and Gradebook Standards — https://www.1edtech.org/blog/rostering-resources-and-gradebook-standards
- 1EdTech, OneRoster 1.2 Gradebook Service Information Model — https://www.imsglobal.org/sites/default/files/spec/oneroster/v1p2/gradebook-informationmodel/OneRosterv1p2GradebookService_InfoModelv1p0.html
- 1EdTech, LTI Assignment and Grade Services Specification — https://standards.1edtech.org/lti/specifications/services/assignments_grades/assignment-grade-services-spec
- Instructure Developer Documentation, External Tools: Assignment Tools — https://documentation.instructure.com/doc/api/file.assignment_tools.html
- ClassLink, Roster Server — https://www.classlink.com/products/roster-server
- Edlink, LMS vs SIS: What's the Difference? — https://ed.link/community/whats-the-difference-between-an-sis-and-an-lms/
