What the Anthology Bankruptcy Means for Your Student Information System
Your SIS vendor just filed for bankruptcy. Now what?
If your institution runs on Anthology’s PowerCampus — or any of its suite products — September 29, 2025 was a date that changed your technology roadmap whether you were ready for it or not. Anthology filed for Chapter 11 protection in the U.S. Bankruptcy Court for the Southern District of Texas, carrying $1.6 to $1.7 billion in debt accumulated largely from its 2021 merger with Blackboard. Support contracts continued. Campuses stayed open. But the strategic calculus shifted immediately for every institution in the portfolio.
This article won’t tell you the sky is falling. What it will do is give you a clear-eyed look at what actually happened, what it means for your operations and compliance posture right now, and the practical steps you should be taking before decisions get made for you.
What Actually Happened
Anthology’s collapse was not a sudden shock — it was a slow bleed made public. The company had skipped interest payments in December 2024 and again in March 2025 before formally restructuring. By the time the Chapter 11 filing landed, revenues had dropped roughly $80 million between 2023 and 2025, and first-lien lenders holding close to 90% of superpriority debt had already negotiated a Restructuring Support Agreement behind the scenes.
The bankruptcy split the company into two tracks. The Teaching and Learning segment — Blackboard and related tools — was acquired by Oaktree Capital Management and Nexus Capital Management. The Enterprise Operations segment, which includes PowerCampus and other SIS and ERP products, was sold to a stalking horse bidder that completed the acquisition on December 31, 2025. That acquisition brought more than 260 institutions into a new ownership structure that few of them had anticipated or planned for.
The transaction closed. The product roadmap question, however, remains open.
What It Means for Institutions Still on Anthology Platforms
Support Is Alive — but the Roadmap Is Frozen
Anthology honored support contracts through the bankruptcy process, and new ownership has committed to platform continuity for existing customers. That is the honest good news. The harder truth is that no major feature development or roadmap acceleration is likely while platforms are being absorbed, staffed, and reassessed under new ownership.
For institutions running compliance-sensitive operations — financial aid disbursements, Title IV reporting, SAP tracking, enrollment certifications — a frozen roadmap is not a neutral status. It is a slow drift toward technical debt. Every regulatory update from the Department of Education, every new FERPA guidance, every state-level reporting requirement creates a widening gap between what your system does and what the rules now require.
According to the U.S. Department of Education’s FSA handbook, institutions participating in Title IV programs must maintain auditable systems that clearly demonstrate proper fund administration. Running software that is no longer actively developed creates measurable audit trail risk — not hypothetically, but in the specific areas auditors are testing right now: Year-Round Pell calculations, R2T4 accuracy, distance education compliance, and Gramm-Leach-Bliley data safeguards.
The Effective Sunset Has Already Started
There is no formal end-of-life date published for PowerCampus. But in higher education technology, a product’s effective sunset often precedes its official one by years. When development resources consolidate, integrations stop getting updated, and the talent that knew the product deeply moves on, institutions are left supporting a platform that is aging faster than the vendor can acknowledge.
The global SIS market is now valued between $11.9 billion and $15.4 billion, with 72% of new deployments moving to cloud-native architecture. Institutions still on on-premise or hybrid legacy systems are running against a current that only moves one direction.
Assessing Your Institution’s Risk Level
Not every Anthology customer faces the same exposure. Before you act, you need an honest read on where you actually stand. Consider four dimensions:
Integration depth. How many other systems — your LMS, your financial aid processor, your CRM, your state reporting portal — connect to your SIS? The more integrations, the higher the migration complexity and the higher the risk of a forced, unplanned transition.
Compliance criticality. Are you a Title IV-participating institution? Do you serve students under Perkins, SAP, or state licensure requirements that generate regular reporting obligations? The more regulatory touchpoints your SIS manages, the less acceptable a frozen development roadmap becomes over time.
Internal capacity. What does your IT team look like? Institutions with lean technology staff face disproportionate risk from vendor instability — they are the least able to manage the workarounds, manual patches, and emergency integrations that come with a platform in transition.
Contract timeline. When does your current support agreement expire? Institutions with contracts expiring in the next 12 to 18 months have a natural decision point. Those with longer contracts face a different calculation — staying put has a cost, but leaving early does too.
Run this assessment with your registrar, financial aid director, IT lead, and CFO in the same room. This is not an IT problem. It is an institutional risk conversation.
What to Do Right Now
Regardless of where you land on the risk spectrum above, three actions should happen immediately — before you commit to any path forward.
1. Audit your data and document your integrations. Pull a complete inventory of every system that touches your SIS: what it sends, what it receives, how often, and through what mechanism. Many institutions discover mid-migration that they have undocumented integrations built years ago by staff members who have since left. Finding these now costs you a few days. Finding them during a migration costs you months.
2. Preserve your compliance documentation. Download and archive your complete student record dataset, your financial aid audit trail exports, and your reporting history. Do this now, while the system is fully operational and you control the timeline. Waiting until a vendor sunset or a rushed migration creates the risk of data loss, format incompatibility, or gaps in records that auditors will later request.
3. Communicate internally and externally. Your board, your accreditor, and your state oversight agency may need to know that your core administrative platform has changed ownership under bankruptcy proceedings. Some accreditation standards explicitly require disclosure of material operational changes. A proactive communication — “here is what happened, here is our assessment, here is our plan” — signals institutional stability. Silence until something breaks does not.
Planning Your Migration: What the Timeline Actually Looks Like
If your risk assessment points toward migration, understand what you are committing to before you start.
For large institutions with 20,000 or more students, a new SIS can cost between $30 million and $100 million over the first five years, with data migration as one of the largest cost drivers. Unplanned migrations — rushed by a vendor failure or an expired contract with no successor — amplify those costs significantly through disorganized data handling, manual rework, and accelerated timelines that leave no room for testing.
The institutions that come through SIS transitions with the least disruption share a few characteristics. They start the process 12 to 18 months before they need to go live. They assign a dedicated internal project lead with real authority — not a committee that meets monthly. They run their legacy system and new platform in parallel for at least one enrollment cycle before cutting over. And they treat data quality as a pre-migration project, not a migration task.
What to look for in a replacement platform:
- Cloud-native architecture with no on-premise infrastructure requirements
- Active development and a published roadmap with a credible vendor
- Compliance module coverage that maps to your specific regulatory environment (Title IV, state licensing, accreditation reporting)
- Implementation timelines that are realistic for your team size — not sales-deck estimates
- References from institutions that are comparable in size, type, and mission to yours
The SIS market has no shortage of options. The question is not which platform has the longest feature list — it is which platform your team can actually implement, maintain, and build on over the next decade without becoming dependent on a vendor whose financial health you cannot assess.
The Bottom Line
Anthology’s bankruptcy is not the end of the world for the 260-plus institutions caught in its wake. New ownership has taken over the SIS and ERP business, support continues, and no one’s system went dark overnight. But the window between “things are fine” and “we’re in a crisis” closes faster than most institutions expect — and it closes faster still for institutions that wait for a formal announcement before acting.
The registrars, IT directors, and CFOs who come through this cleanest are the ones who assessed their risk honestly, documented everything while they had time, and started planning a path forward before the urgency forced their hand. That time is now.
Ready to talk through your migration options? Schedule a consultation with Edular to discuss what a modern, cloud-native SIS looks like for an institution your size.
Frequently Asked Questions
Is PowerCampus shutting down? No formal end-of-life date has been announced. PowerCampus was acquired by a new owner as part of Anthology’s Chapter 11 bankruptcy proceedings, which closed December 31, 2025. The platform continues to operate, but its long-term development roadmap under new ownership remains unclear.
Do I have to migrate immediately? Not immediately — but immediately is when you should start assessing whether migration is right for your institution. The institutions that handle SIS transitions best give themselves 12 to 18 months of planning before going live on a new system.
What are the compliance risks of staying on an unsupported platform? Institutions participating in Title IV programs are required to maintain auditable systems for proper fund administration. Software that stops receiving active updates creates risk in areas auditors are currently testing: R2T4 calculations, Year-Round Pell disbursements, distance education compliance, and data privacy safeguards under Gramm-Leach-Bliley.
Can I negotiate a transition timeline with the new owner? Potentially. If your support contract is active and you are in good standing, you have more leverage now than you will once renewal time arrives. Engage your account representative directly and ask explicit questions about the product roadmap, planned updates, and any end-of-life timeline.
