Orphaned Systems
Legacy Banner or Colleague instances nobody fully understands anymore because the person who built them retired
Banner, Colleague, Jenzabar, PeopleSoft, Workday: we've sat on the other side of every one of these systems,
inside real registrar's offices and IT departments, not just in a support ticket queue.
Higher ed runs on systems that were built for a different institution than the one you're actually running today. The ERP that made sense a decade ago is still sitting there, still technically working, but it's carrying a lot more weight than it was ever designed for: financial aid rules that get rewritten almost every cycle, enrollment numbers that swing in ways nobody on your team predicted last spring, compliance deadlines that show up with almost no warning. None of that is a failure on your part. It's just what happens when the technology stands still and everything around it keeps moving. Same ERP doesn't mean "same problem." A registrar's office at a small private college in Ohio and a multi-campus community college system in Texas can both run Banner and still need almost nothing in common from it. Same software, different institution, different pressure points, different fixes.
That's the part a lot of ERP consultants miss — they're selling a standard process, not actually looking at your campus. We work inside three areas that cover the full lifecycle of your ERP and SIS environment:
Most ERP vendors want to sell you a platform. Most consultants want to bill hours. We've built our team around people who've actually worked inside registrar's offices, bursar's offices, and IT departments at colleges and universities, so when your team says "the add/drop period is breaking our reporting again," we already know what that means. We're not learning your institution's calendar on the job, and we're not translating your problem into consultant-speak before we can act on it. We've also sat through the vendor calls where nobody on the other end has ever actually touched a Banner queue or a Colleague batch job, and we built 1EdgeIT specifically because that gap shouldn't exist.
Before founding 1EdgeIT, our team spent years working directly inside Banner, Colleague, and PeopleSoft environments, sitting in registrar's offices and IT departments, not just selling into them. We started 1EdgeIT because we kept seeing the same gaps from the inside, and we're already carrying that experience into the institutions we work with today. We've watched good IT teams get blamed for problems that were baked into the system years before they ever took the job. That's the perspective we bring to every institution we work with now, not as outsiders learning the terrain, but as people who've already paid down the learning curve somewhere else.
Every engagement looks a little different depending on where your institution is starting from. But strip away the specifics, and here's what you can count on across the board:
Legacy Banner or Colleague instances nobody fully understands anymore because the person who built them retired
Financial aid, and other teams working off disconnected spreadsheets because the ERP reports don't give them what they need
A pending Workday or PeopleSoft migration that's stalled as IT doesn't have bandwidth on top of daily Ops
CRM data that never talks to the SIS/ERP, so admissions and student success teams are working blind
A key ERP staff member leaving mid-year with no documented backup plan