5 Tips for Surviving (and Thriving) in a New SIS

From a Retired Tech Director Who’s Been There 

Taking on a new Student information system (SIS) is one of the most complex and critical transitions in K-12 tech.

The first two years of working with a new Student Information System are critical. Year one is often about survival: cleaning up legacy data, getting through your first scheduling cycle, and making sure state reporting goes smoothly. Year two is where you build on that foundation, improve your workflows, and start making the system work for you—not the other way around. 

I’ve guided multiple SIS transitions over the course of my career, and while every system has its quirks, the core truths remain the same. So here’s my advice, passed on from one tech leader to another.

Clean Data is Your Best Friend

Before you even touch a training video or join your first implementation call, make sure your data is report-ready. A new SIS won’t magically clean up years of inconsistent entries or fields used in six different ways. If your data is messy, your workflows will be, too—and you’ll spend more time troubleshooting bad imports than learning the new system.

Be Patient—and Persistent

Learning the ins and outs of a new platform takes time. It’s not just clicking buttons—it’s figuring out how those buttons affect every classroom, every report, every parent portal. You’ll hit roadblocks. That’s normal. Just keep at it, and don’t be afraid to lean on the people around you – including your implementation team, your customer success manager or support staff. 

Speak the Language

One of the biggest frustrations in a new SIS is simply figuring out how to talk about it. Each SIS has its own lingo but the concepts are the same—enrollment, attendance, schedules, grading—but the terms might be different. Say things like: “In our old SIS, we did XYZ. How does that translate here?” Frame things in a way that helps you bridge the gap between systems.

The Setup Phase Matters—A Lot

I can’t emphasize this enough: the early setup decisions are foundational. How you build courses, set terms, assign user roles—those details shape everything that follows. Tech directors need to understand the why and how behind the scenes. Don’t delegate it away completely.

Ask Questions. Then Ask More.

No question is too small, too technical, or too obvious. I’ve seen districts stumble because someone didn’t want to look uninformed. Ask. And if you don’t get a clear answer, ask again. 

There’s no such thing as a perfect transition, but with the right mindset and support, it can be a smooth one. Stay curious. Stay patient.  

Curious about what implementation process looks like for a new SIS? Read about implementation or download a sample implementation guide here.