SharePoint: Intranet Survival in Mergers

Key insights

• SharePoint Hub Site  – This summary covers a YouTube video by Dougie Wood (MVP) showing how to preserve existing intranets during an intranet merger.
  It explains connecting mature intranets with a hub instead of rebuilding them from scratch.
• Group site  – Create a group-level site above each existing intranet and use hub registration so sites can join a central layer.
  This keeps each team’s current site while presenting a single, joined-up employee experience.
• Global navigation  – The hub provides one consistent navigation bar across multiple intranets without forcing one site structure.
  Use content roll-ups to surface news, documents, and events from all connected sites into the hub.
• Flexible branding  – Each organization can retain its own look and feel while the hub adds a shared corporate layer.
  Keep site-level controls so permissions and security stay clear and auditable during integration.
• Reduced disruption  – Avoid a “big bang” migration to preserve familiarity and improve trust.
  This pattern boosts better user adoption and supports phased rollouts, spin-offs, or future acquisitions.
• Tenant-to-tenant migration  – For deeper consolidation use tenant-to-tenant or hybrid migrations and extend with SPFx customizations and AI-driven tools.
  Plan ahead: legacy server support timelines mean many organizations move to SharePoint Online soon.

Overview of the Video

In a recent YouTube presentation, Dougie Wood [MVP] explains how modern intranets can survive corporate mergers by linking existing systems instead of replacing them. He shows real-world examples and demonstrates a pattern that uses a SharePoint Hub Site combined with a group-level site to create a single employee experience, while preserving familiar sites. Accordingly, the video argues that organizations can avoid a disruptive, all-at-once migration and instead adopt a layered architecture that reduces change for users.

How the Hub-and-Group Pattern Works

First, the pattern places a group intranet site above the existing, separate intranets and registers the group site as a hub. Then, existing team or organisational intranets associate with that hub so navigation, news, and events can roll up into the shared layer. As a result, employees see a unified global navigation and aggregated content while their familiar sites remain intact, which preserves established workflows and trust.

Second, the design maintains separate branding and identities for each legacy intranet while presenting a corporate overlay on the hub site. Consequently, teams retain local styles and customisations that users prefer, yet the hub provides consistent corporate links, search scope, and announcements. This balance helps sustain engagement because people do not suddenly lose the sites they rely on day to day.

Benefits and Tradeoffs

The main benefit is reduced disruption: organizations avoid a risky, "big bang" migration and instead let sites keep working while leaders add a unifying layer. Moreover, the hub approach supports scalable growth, because new acquisitions or spin-offs can attach to the same hub without reshaping every site. However, there are tradeoffs: while the hub simplifies navigation and roll-ups, it also introduces governance complexity because multiple sites must align on metadata, search filters, and content lifecycle policies.

Another tradeoff involves performance and search scope. Although hubs can roll up news and events efficiently, cross-site search and content aggregation may require careful planning to avoid noisy results or duplicate content. Therefore, teams must decide whether to centralize taxonomy and retention rules or to accept some duplication in exchange for local autonomy. In short, the hub model reduces immediate disruption but increases the need for coordinated governance.

Technical and Organizational Challenges

Technically, teams will face challenges around permissions, tenant boundaries, and customised components. For example, tenant-to-tenant migrations remain complex when organisations need to consolidate accounts, and custom solutions built with the SharePoint Framework may need updates to work across new hub associations. Furthermore, synchronising permissions while preserving secure access to sensitive resources requires careful mapping and testing to avoid unintended exposure.

Organizationally, the biggest hurdles are alignment and communication. IT, communications, and business owners must agree on navigation conventions, content owners, and what content should roll up to the group intranet. Without clear responsibilities, the hub can become a chaotic aggregation of out-of-date news and events, which undermines the user experience that the pattern seeks to protect.

Practical Recommendations

Start small and iterate: register a hub, create a group site, and pilot associations with a few friendly teams to validate navigation and roll-up behaviour. Next, define a lightweight governance plan that sets standards for news metadata, event publishing, and navigation priorities so roll-ups remain relevant and searchable. Also, involve communications early to align branding and messaging so the corporate layer feels cohesive without erasing local identity.

Finally, plan for future change by documenting patterns and automation scripts; this makes it easier to onboard new sites after further acquisitions or restructures. Testing is crucial: validate cross-site search, permissions, and performance before wider rollout so users encounter a stable, familiar experience. By doing so, organizations reduce migration risk and preserve employee engagement during uncertain transitions.

Key Takeaways and Video Chapters

The video by Dougie Wood [MVP] highlights a practical alternative to ripping out intranets during mergers: use a hub site to unify navigation and content while maintaining existing sites. This approach lowers disruption, preserves user trust, and scales with future corporate changes, but it does demand stronger governance and technical coordination. Overall, the hub-and-group pattern offers a balanced path between full consolidation and unchecked fragmentation.

• 00:00 SharePoint Merger
• 01:21 SharePoint Homepage Examples
• 02:24 Create Group Site
• 04:25 Brand Colours
• 06:00 Register as Hub Site
• 07:30 Inherit Hub Site and Navigation

Keywords

SharePoint intranet migration, merger SharePoint consolidation, post-merger intranet strategy, SharePoint merger best practices, intranet governance after merger, SharePoint integration for mergers, change management SharePoint merger, preserving intranet during merger