Replacing Valo Intranet is becoming increasingly relevant for many organizations. Read what alternatives are available and how an intranet can be built directly on SharePoint.

Updated May 5, 2026

Valo Intranet’s active development has ended, and the solution has entered the final stage of its lifecycle. The intranet no longer evolves alongside the organization’s needs in the same way as before.

This shift has led many organizations to explore alternatives that offer more modern and continuously evolving intranet solutions. A native SharePoint intranet is one of the most common alternatives, providing flexibility and a wide range of capabilities.

Valo runs on top of SharePoint and utilizes its structures and features. It is designed as a packaged intranet solution that includes ready-made functionalities, page templates, and themes. These components have enabled faster deployment and reduced implementation effort.

Some organizations have moved from Valo Intranet to Fresh intranet, which is also a SharePoint-based product. At the same time, many are taking a broader look at their intranet strategy. Replacing Fresh intranet or building an intranet directly on SharePoint’s standard capabilities is increasingly part of the discussion.

A packaged intranet solution often introduces a separate license, its own development path, and dependency on a single vendor. Development, updates, and new features are tied to the product’s roadmap.

An intranet built directly on SharePoint simplifies IT environment management. It provides a long-term and sustainable solution. The intranet operates as part of the Microsoft 365 environment without an additional application layer, keeping licensing, integrations, and management within a single ecosystem.

Replacing and migrating Valo Intranet to SharePoint – how the transition works

One of our customers decided to replace the existing Valo Intranet with SharePoint’s standard features to provide a modern and secure intranet experience. The goal was to ensure a smooth and user-friendly transition.

In this case, the change focused primarily on a light redesign of the user interface and visual structure. The fastest way to replace Valo Intranet with SharePoint is to recreate equivalent functionalities using SharePoint’s standard features and then remove customizations, especially if the existing concept and content are retained.

For example, the homepage was rebuilt to closely match the previous structure and visual layout, making it easier for users to adapt.

The navigation was also recreated using SharePoint’s native capabilities. Navigation links in the new intranet point to existing content, allowing users to find information as easily as before.

After updating the homepage and navigation, Valo-specific components were removed from all intranet sites and connected to a new hub site. Existing sites, pages, and documents retained their original URLs.

The new SharePoint-based intranet provides many of the same benefits as Valo Intranet, but on a modern and continuously evolving platform. The project ensured a smooth user experience throughout the transition.

SharePoint advantages and similar features

A SharePoint intranet offers many of the same capabilities as Valo Intranet, along with several additional benefits:

• Ease of use
  • SharePoint’s user interface is intuitive and user-friendly. A short learning period is typically enough for users to find the information they need efficiently.
• Content management
  • The modern interface supports clear and straightforward content management without requiring technical expertise. Pages can be updated and created directly in the browser.
• Flexibility and adaptability
  • SharePoint offers extensive customization options. The intranet structure can be tailored to organizational needs and continuously developed.
• Quick links, news, and feeds
  • SharePoint includes many familiar elements such as quick links and news. These can be placed similarly to the previous intranet, easing the transition.
• Collaboration features
  • SharePoint supports interaction through discussions, blogs, and social feeds, improving internal communication and collaboration.
• Security and governance
  • Microsoft continuously develops security and compliance capabilities. SharePoint meets international standards and offers comprehensive access control.
• Microsoft 365 integration
  • SharePoint is a native part of Microsoft 365. Integration with Teams, Outlook, OneDrive, and Power Automate supports collaboration, information sharing, and automation.
• Cost-efficiency and centralized management
  • SharePoint is included in Microsoft 365 subscriptions, reducing the need for separate intranet licenses. Centralized management simplifies administration and can reduce total costs.
• Continuous development
  • Microsoft continuously evolves SharePoint, with new features and improvements delivered regularly.

Valo, Fresh intranet or SharePoint – comparing intranet solutions

Organizations evaluating their intranet future typically compare three options: continuing with Valo, moving to Fresh intranet, or building directly on SharePoint.

Many organizations are also looking for a Valo intranet alternative or evaluating whether Fresh intranet is the right alternative for their needs.

Feature	Valo intranet	Fresh intranet	SharePoint intranet
Concept	Packaged intranet on SharePoint	Modern intranet on SharePoint	Built directly on Microsoft 365
Development status	End of lifecycle	Actively developed	Continuously developed by Microsoft
Deployment	Fast, ready-made	Fast, ready-made	Light or tailored implementation
Customization	Limited by product	Limited by product	Fully customizable
Vendor dependency	Vendor-specific	Vendor-specific	No separate product
Microsoft 365 integration	Good	Good	Native
Licensing	Separate license	Separate license	Often included
IT management	Additional layer	Additional layer	No separate layer
Flexibility	Product roadmap	Product roadmap	Organization-driven

An intranet built directly on SharePoint provides a long-term and flexible solution. It runs natively on Microsoft 365 without an additional application layer, simplifying architecture and maintenance.

How can Valo Intranet be replaced?                                             

Replacing Valo Intranet can be a straightforward project at its simplest. Updating the homepage and navigation is often sufficient when the existing structure and content are retained.

Another option is to redesign the intranet concept entirely based on organizational needs. In this case, the intranet can better support daily work, communication, and information management.

Intranet design typically starts with definition workshops, where service design principles are applied. These workshops define the structure, content, and governance model, ensuring that users can easily find what they need.

A smooth transition ensures continuity

Replacing Valo Intranet with a SharePoint intranet can be a straightforward process when the concept and content are preserved. SharePoint’s flexible structure enables a solution that adapts to organizational needs and supports communication, collaboration, security, and employee experience.

Keep your intranet up-to-date and user-friendly – ​​ contact us to plan your next step.

Henry Scheinin
Leading Consultant, Partner