Behind the patient portals and course websites, many of Rhode Island’s hospitals, colleges and public agencies run on a quieter piece of technology: Microsoft SharePoint. It holds policies, procedures, committee minutes, research files and the internal intranet that staff use every day. In many organizations, that SharePoint environment was installed on local servers years ago and has been running ever since.
That era is ending. Microsoft ended support for SharePoint Server 2016 and 2019 in July 2026, which means no more security updates for those on-premise versions. For institutions that store sensitive health, student or financial information, running unsupported software is a risk that auditors, insurers and IT security teams will not accept for long.
The good news is that the deadline creates a chance to do more than move files. It is an opportunity to rebuild the intranet around how people actually work today.
Why this matters for hospitals and campuses
Large institutions such as hospital systems and universities like Brown University share a few traits that make SharePoint decisions complicated:
- Many departments, many owners. Each department built its own sites, often with different structures and permission settings.
- Regulated content. Clinical procedures, HR files and research data carry legal and compliance requirements.
- Long memory. Some content is decades old, and nobody is sure what can be archived.
- Hybrid work. Staff, faculty and students now expect to reach the same information from home, a clinic or a phone.
Moving all of that to SharePoint Online in Microsoft 365 is not a simple copy and paste.
Phase one: plan the migration carefully
A sound migration starts with an inventory. Teams that specialize in Centric SharePoint migration projects usually begin by answering a few questions:
- What exists? A full list of sites, libraries, lists, workflows and custom solutions.
- What is still used? Usage data often shows that a large share of old sites have not been opened in years.
- What must be kept? Retention rules for medical, academic and financial records decide what moves, what is archived and what is deleted.
- Who should see what? Permissions are reviewed rather than copied as-is, since years of ad hoc sharing often leave sensitive files too open.
- What will break? Older workflows, custom web parts and integrations need replacements in Microsoft 365, often through Power Automate.
The migration itself is then run in waves, starting with low-risk departments, so issues are found early and fixed before clinical or academic teams move.
Phase two: rebuild the intranet people want to use
Once content is in Microsoft 365, organizations face a choice. They can recreate the old intranet page by page, or they can design something better. The second path usually pays off.
Modern SharePoint supports news hubs, personalized home pages, Microsoft Teams integration and mobile access out of the box. Custom SharePoint application development fills the gaps that standard features leave, such as:
- A clinical policy center where nurses find the current version of a procedure in seconds.
- Department portals for research teams with structured metadata and approval workflows.
- Onboarding hubs that guide new staff or faculty through training and forms.
- Request forms for IT, facilities or HR that route automatically and track status.
The aim is an intranet that answers questions instead of hiding them. When staff can find what they need quickly, they stop keeping private copies of documents, which also improves security and compliance.
Common mistakes to avoid
- Lifting and shifting everything. Migrating unused content increases cost and clutter.
- Copying broken permissions. Old access problems become new access problems in the cloud.
- Skipping change management. Staff need training and clear communication, especially clinical teams with little time.
- Treating the project as IT only. Department leaders should own their content and help design the new structure.
Security and compliance in the new environment
Moving to Microsoft 365 also changes how security works. On-premise SharePoint relied heavily on the network perimeter: if you were inside the building or on the VPN, you were trusted. In the cloud, access depends on identity, device and context.
Hospitals and universities should use the migration to put modern controls in place:
- Sensitivity labels that mark clinical, HR or research content and control who can open, share or download it.
- Multi-factor authentication and conditional access, so a login from an unknown device or location triggers extra checks.
- Retention policies that apply legal and regulatory retention periods automatically instead of relying on staff to remember them.
- External sharing rules that allow collaboration with partners and affiliated researchers without opening sensitive libraries to the world.
- Audit logs that show who viewed or changed important documents, which helps with HIPAA and FERPA reviews.
Setting these up during the migration is far easier than adding them later, once thousands of users have already settled into new habits.
Turning a deadline into an upgrade
End of support is rarely welcome news, but for Rhode Island’s hospitals, universities and agencies it is a natural moment to clean house. A careful migration protects sensitive information, and a thoughtful rebuild gives staff an intranet they will actually use. Institutions that treat these as two connected phases, rather than a single rushed move, will come out with a safer and more useful digital workplace.
The best time to start is before the pressure peaks. Planning, content cleanup and permission reviews take longer than the technical move itself, and institutions that begin early can schedule migration waves around academic calendars, budget cycles and clinical peak periods instead of rushing everything at once.
Frequently asked questions
Can we keep running SharePoint Server 2016 or 2019?
The software will keep working, but it no longer receives security updates from Microsoft, which increases risk over time and may raise concerns with auditors and cyber insurers.
How long does a SharePoint migration take?
It depends on size and complexity. Smaller environments can move in a few months, while large hospital or university environments are often migrated in phases over a longer period.
Do we need custom development after migrating?
Not always. Many needs are met by standard Microsoft 365 features, but custom development helps with specialized workflows, structured records and integrations with other systems.

