A modern SharePoint intranet in 2026 is built on a home site, hub-and-spoke hub site architecture, mega menu navigation, the SharePoint app in Teams (formerly Viva Connections) for mobile and Teams surfacing, sensitivity-label-protected containers, and Microsoft Purview Audit (Premium) for HIPAA / SOC 2 / FedRAMP defensibility.
SharePoint Modern Intranet Design
Best practices for home sites, hub site architecture, mega menu navigation, custom branding, web parts, mobile responsiveness, multilingual sites, and enterprise adoption strategies.
Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group
How to Design a Modern SharePoint Intranet
How do you design a modern SharePoint intranet? Start with a Home Site as the organization-wide landing page with global navigation. Build a hub site architecture grouping related sites by department or region. Design mega menu navigation providing access to critical resources within 2 clicks. Apply custom branding with organizational colors, logos, and accessible contrast ratios. Configure dynamic web parts — News, Events, Hero, Quick Links, Viva Engage — with audience targeting for personalized content. Test on mobile devices and deploy the SharePoint app in Teams (formerly Viva Connections) for the mobile app experience. Launch in phases with executive sponsorship and adoption tracking.
Your intranet is the digital front door to your organization. It is where employees find news, policies, tools, people, and answers. A well-designed intranet drives engagement, reduces support tickets, accelerates onboarding, and builds culture. A poorly designed intranet becomes a ghost town that employees actively avoid — reverting to email, Teams chats, and shared drives for information they should find in one place.
EPC Group designs and deploys SharePoint intranets for organizations across healthcare, financial services, education, and government. This guide shares the intranet design methodology we apply to every engagement — covering architecture, navigation, branding, content strategy, and launch planning.
Whether you are building a new intranet from scratch, modernizing a classic SharePoint environment, or optimizing an existing modern intranet that is not meeting adoption targets, this guide covers every decision point.
Modern vs Classic SharePoint Architecture
SharePoint modern experience (introduced in 2017, now the default) fundamentally changes how intranets are architected. Classic SharePoint used managed paths, site collections, and master pages. Modern SharePoint uses flat site architecture, hub sites, and component-based web parts.
| Aspect | Classic SharePoint | Modern SharePoint |
|---|---|---|
| Site Hierarchy | Managed paths with parent/child site collections | Flat site architecture — all sites are equal, organized by hub association |
| Navigation | Structural navigation tied to site hierarchy | Hub navigation shared across associated sites, mega menu support |
| Branding | Master pages, CSS, custom layouts | Themes, header layouts, brand center, no custom CSS |
| Mobile | Separate mobile views, often broken | Responsive by default, Viva Connections mobile app |
| Permissions | Inherited from parent site collection | Independent per site, hub does not control permissions |
| Search | Scoped to site collection or farm | Organization-wide, hub-scoped, or site-scoped search |
Migration Note: If you are migrating from classic to modern, do not attempt an in-place upgrade of your existing site hierarchy. Build the modern intranet as a new Home Site + Hub architecture and migrate content site by site. EPC Group migrates classic intranets in 6-12 week sprints, decommissioning legacy sites as content moves to the new architecture.
Six Pillars of Modern Intranet Design
Every enterprise SharePoint intranet must address these six design pillars. Neglecting any one leads to poor adoption, user frustration, or governance failures.
Home Site Configuration
Designate a communication site as the organization-wide landing page. Powers global navigation, intranet-wide search, and the SharePoint app in Teams (formerly Viva Connections).
Hub Site Architecture
Group related sites under departmental or regional hubs. Shared navigation, branding, and search scope across 5-20 associated sites per hub.
Mega Menu Navigation
Full-width dropdown navigation organized in columns with headers. Maximum 7 top-level items with 5-8 sub-links each for optimal usability.
Custom Branding
Organization theme (colors, header, footer), logo placement, custom fonts (SharePoint brand center), and WCAG 2.1 AA accessible contrast ratios.
Mobile-First Design
Test on actual devices. Single-column critical content. SharePoint app in Teams (formerly Viva Connections) for a mobile experience with dashboard, News, and resources.
Audience Targeting
Personalize News, Quick Links, Navigation, and Hero web parts by security group, M365 group, or Entra ID attribute. Show relevant content to each user.
Home Site Setup and Configuration
The Home Site is the most important site in your SharePoint tenant. It serves as the organizational landing page, the global navigation host, the base of the SharePoint app in Teams (formerly Viva Connections), and the intranet-wide search scope (Microsoft Learn, accessed 2026-10-27). Microsoft 365 E, F, and A licenses cover one experience; up to 50 experiences require a Viva Suite or Viva Communications and Communities license for every user (Microsoft Learn, accessed 2026-10-27).
Home Site Configuration Steps
- Create a communication site with the "Topic" or "Blank" template — not a team site (team sites have a left navigation panel that consumes screen space)
- Designate the site as the Home Site via SharePoint Admin Center > Settings > Home Site, or via PowerShell: Set-SPOHomeSite -HomeSiteUrl https://tenant.sharepoint.com/sites/intranet
- Enable the global navigation bar — this appears across all sites in the tenant and is managed from the Home Site navigation settings
- Configure the SharePoint app in Teams (formerly Viva Connections) by setting up the dashboard (cards for key actions), News, and resources (curated links)
- Set up the home page layout with Hero web part (featured content), News web part (organizational news), Quick Links (top tools), and Events (company calendar)
- Apply the organizational theme and logo — the Home Site sets the visual tone for the entire intranet experience
- Configure search — the Home Site search bar becomes the organization-wide search entry point with custom result sources and verticals
Hub Site Strategy for Enterprise Intranets
Hub sites are the organizational backbone of your intranet. They group related sites under a shared navigation, theme, and search scope — without controlling permissions (a critical distinction from classic site collections). EPC Group designs hub architectures based on how employees think about the organization, not how the org chart looks.
Recommended Hub Structure
Departmental Hubs
Examples: HR Hub, IT Hub, Finance Hub, Marketing Hub, Legal Hub
Scope: 5-20 associated sites per hub (policies, forms, team sites, project sites)
Group all sites related to a business function under one hub with shared navigation.
Regional Hubs
Examples: North America Hub, EMEA Hub, APAC Hub, LATAM Hub
Scope: 10-50 associated sites per hub (regional offices, local news, compliance)
For multinational organizations — regional news, events, and resources with local language support.
Project/Initiative Hubs
Examples: Digital Transformation Hub, M&A Integration Hub, Office Move Hub
Scope: 3-10 associated sites (project sites, workstreams, stakeholder sites)
Time-limited hubs for major organizational initiatives. Decommission when complete.
Leadership Hub
Examples: Executive Communications Hub
Scope: 2-5 associated sites (CEO blog, town halls, strategy updates)
Executive-sponsored hub for leadership visibility. Drives engagement and culture.
Hub Limit: An organization can have up to 2,000 hub sites (Microsoft Learn, accessed 2026-10-27), but plan before you create them: too many hubs creates navigation confusion and dilutes the organizational structure. If a department only needs 1-2 sites, associate them with a broader hub rather than creating a dedicated hub.
Navigation Design: Mega Menu, Footer, and Global Nav
Navigation is the make-or-break element of intranet design. If employees cannot find what they need within 2-3 clicks, they abandon the intranet and revert to email, Teams, or asking a colleague. EPC Group designs navigation using card sorting and tree testing with actual employees — never based on assumptions.
Three Navigation Layers
- Global Navigation (Home Site) — visible across all sites in the tenant. Contains 5-7 top-level links to the most critical organizational resources (HR, IT Support, Company Directory, News, Tools). Managed from the Home Site.
- Hub Navigation — shared across all sites associated with a hub. Contains department-specific links organized in mega menu format. Each hub manages its own navigation independently.
- Site Navigation — left navigation or top navigation specific to an individual site. Contains page links, document libraries, and lists relevant to that site only.
Mega Menu Best Practices
- Maximum 7 top-level items — research shows 7 is the upper limit before cognitive overload degrades usability
- Use labels (non-clickable headers) to organize sub-links into logical groups within each mega menu column
- Limit sub-links to 5-8 per top-level item — deep mega menus overwhelm users and perform poorly on mobile
- Include audience-targeted links — show "Manager Tools" only to people managers, "New Hire Resources" only to employees under 90 days
- Add a search shortcut within the mega menu for users who prefer searching over browsing
- Test mobile behavior — mega menu items stack vertically on mobile; ensure the most important items appear first
Footer Configuration
Enable the site footer for the Home Site and all hub sites. Include: company legal links (privacy policy, terms of use), social media links, contact information (IT helpdesk, HR), and quick links to the most-requested resources that did not fit in the mega menu. Footer links are consistent across associated sites when configured at the hub level.
Branding: Themes, Headers, and Visual Identity
Branding makes the intranet feel like your organization — not a generic Microsoft template. Modern SharePoint provides structured branding surfaces that balance visual customization with maintainability. Do not attempt to replicate your marketing website pixel-for-pixel — the intranet is a productivity tool, not a brochure.
Branding Layers
Tenant Theme
Apply via SharePoint Admin Center or PowerShell. Sets primary, secondary, accent, and neutral colors across all sites. Affects buttons, links, headers, and web part accents. JSON-based using the SharePoint theme generator tool.
Header Layout
Choose Extended (large with background image), Standard (logo + title), or Compact (minimal). Set header background color and site logo. Extended headers work well for Home Sites; Compact for team sites.
Site Footer
Enable per-site or per-hub. Contains 8 link slots organized in two rows. Include legal links, social media, contact info, and frequently requested resources.
Brand Center
Manage organizational colors, fonts, and images centrally. A Global Administrator turns it on in the Microsoft 365 admin center, and it uses the Public CDN (Microsoft Learn, accessed 2026-10-27).
Accessibility Requirement: All branding must meet WCAG 2.1 AA contrast ratios — minimum 4.5:1 for normal text and 3:1 for large text. EPC Group tests every theme against accessibility standards before deployment. A branded intranet that fails accessibility excludes users with visual impairments and creates legal liability.
Essential Web Parts for Enterprise Intranets
The right web part configuration transforms a static page into a dynamic, personalized experience that brings employees back daily.
Hero Web Part
Full-width visual banner showcasing 1-5 featured stories. Use for CEO messages, major announcements, and seasonal campaigns. Rotate content weekly.
Highest visual impact on the page
News Web Part
Dynamic news feed filtered by site, hub, or organization-wide. Enable audience targeting to show department-relevant news. Boost important stories.
Primary content driver
Events Web Part
Company calendar pulling from SharePoint Events lists or Outlook/Exchange calendars. Show upcoming town halls, training, and deadlines.
Drives recurring visits
Quick Links
Icon-based grid linking to top 8-12 applications and resources — HRIS, IT ticketing, expense reports, room booking. The most-clicked element on any intranet.
Highest utility — points people to self-service tools
Viva Engage (Yammer)
Embedded social feed showing organizational conversations, leadership posts, and community highlights. Creates two-way communication culture.
Builds community across departments
People Web Part
Spotlight employees — new hires, work anniversaries, featured team members, executives. Humanizes the intranet and builds connection.
Culture builder
Multilingual Sites and Personalization
For global organizations, multilingual support is a requirement — not a nice-to-have. SharePoint modern communication sites support multilingual pages where translators create localized versions of each page, and users see content in their preferred language automatically based on their browser or profile settings.
Multilingual Configuration
- Enable multilingual features at the site level — Site Settings > Language Settings > Add languages (up to 49 languages supported)
- Create translation pages — SharePoint creates a copy of each page for each enabled language; assign translators to localize content
- Navigation translation — navigation labels are translated separately via the navigation editing interface
- Audience targeting by region — combine multilingual pages with audience targeting to show region-specific content alongside language-localized content
- Machine translation — SharePoint does not auto-translate; use Microsoft Translator or Azure AI Translator for initial drafts, then have human translators review
Personalization with Audience Targeting
Audience targeting shows different content to different users based on Microsoft 365 group membership, security groups, or Entra ID attributes. Apply audience targeting to: News web part (department-relevant stories), Quick Links (role-specific tools), Navigation links (manager vs individual contributor), and Hero web part tiles (region-specific campaigns). The intranet feels personally relevant to each employee rather than a one-size-fits-all broadcast.
Analytics, Adoption Metrics, and Launch Strategy
An intranet is only successful if people use it. EPC Group measures success not by how many pages were built, but by how many employees actively use the intranet weekly.
Key Metrics to Track
| Metric | Target | How to Measure |
|---|---|---|
| Monthly Active Users (MAU) | Rising month over month after launch | SharePoint Site Analytics > Unique viewers |
| Daily Active Users (DAU) | Rising month over month | SharePoint Site Analytics > daily unique viewers |
| Pages per Session | 3+ pages | Azure Application Insights (custom telemetry) |
| Search Success Rate | Rising share of queries with clicks | Search Analytics in SharePoint Admin Center |
| News Engagement Rate | Rising click-through on news | News web part analytics > click-through rate |
| Mobile Usage | Tracked against your workforce mix | Viva Connections analytics + site analytics by device |
Phased Launch Strategy
Soft Launch
Week 1
50-100 champions from each department. Collect feedback on navigation, content, and mobile experience. Fix usability issues before broader rollout.
Department Rollout
Weeks 2-4
One department per week starting with the most engaged (HR, Communications). Department champions lead local adoption and content migration.
Organization-Wide
Week 5
Full launch with CEO announcement, email campaign, Teams notification, all-hands demo. Decommission old intranet links to force adoption.
Optimization
Weeks 6-12
Monitor analytics weekly. Address usability feedback. Add requested features. Optimize search. Decommission legacy intranet completely.
Frequently Asked Questions
How do you design a modern SharePoint intranet?
Designing a modern SharePoint intranet requires five foundational decisions: 1) Set up a Home Site as the organization-wide landing page with global navigation, news, and search, 2) Design a hub site architecture that groups related sites by department, region, or function — with shared navigation and branding, 3) Build mega menu navigation that provides access to critical resources within 2 clicks, 4) Apply custom branding with organizational colors, logos, and header layouts, 5) Configure key web parts — News, Events, Hero, Quick Links, Viva Engage, and People — to surface dynamic, personalized content. EPC Group designs SharePoint intranets with a focus on adoption, governance, and measurable engagement metrics.
What is a SharePoint Home Site and why is it important?
A SharePoint home site is a communication site that serves as the landing page and gateway for your intranet; its search covers the entire intranet, its news is official organizational news by default, and it hosts global navigation in the SharePoint app bar (Microsoft Learn, accessed 2026-10-27). It is also the base of the SharePoint app in Teams, formerly Viva Connections (Microsoft Learn, accessed 2026-10-27). Users with Microsoft 365 E, F, or A licenses can create and use one experience; two or more experiences, up to 50, need a Viva Suite or Viva Communications and Communities license for every user (Microsoft Learn, accessed 2026-10-27). Without a Home Site, users land on the generic SharePoint start page with no organizational branding or navigation. EPC Group configures the Home Site as the first step in every intranet deployment — it is the front door to your digital workplace.
How should hub sites be structured for an enterprise intranet?
Hub sites provide shared navigation, branding, and search scope across groups of related sites. Enterprise hub site architecture follows a two-level pattern: 1) Organizational hubs at the top level — HR Hub, IT Hub, Finance Hub, Operations Hub — each containing 5-20 associated sites, 2) Regional or divisional hubs for geographically distributed organizations — North America Hub, EMEA Hub, APAC Hub. Best practices: plan before you create hubs, even though an organization can have up to 2,000 hub sites; remember that hubs associated with other hubs show content and search results up to three levels of association (Microsoft Learn, accessed 2026-10-27); use consistent naming conventions; and assign hub owners responsible for navigation and branding maintenance.
What are the best web parts for a SharePoint intranet home page?
The most effective SharePoint intranet home page web parts are: 1) Hero web part — large visual banner highlighting 1-5 featured stories, events, or campaigns, 2) News web part — organizational news filtered by hub or site, with audience targeting to show relevant content, 3) Events web part — upcoming company-wide events from a centralized calendar, 4) Quick Links web part — icon-based links to top 8-12 most-used applications and resources, 5) Viva Engage (Yammer) web part — live social feed showing organizational conversations and leadership posts, 6) People web part — spotlight team members, executives, or new hires, 7) Countdown Timer — for upcoming launches, deadlines, or events, 8) Weather — simple but high-engagement widget that brings users back daily. EPC Group configures these web parts with audience targeting so different user groups see personalized content.
How do you implement mega menu navigation in SharePoint?
SharePoint mega menu navigation replaces the standard link-based navigation with a full-width dropdown displaying links organized in columns with headers. To enable: 1) Go to Site Settings > Navigation > select Mega Menu, 2) Structure navigation with top-level headers (HR, IT, Finance, Operations) and sub-links organized by category, 3) Add labels (non-clickable headers) to group related links within each column, 4) Keep the mega menu to a maximum of 7 top-level items with 5-8 sub-links each (more causes cognitive overload), 5) Test on mobile — mega menu items stack vertically on mobile devices, so prioritize the most-used links at the top. For the Home Site, the mega menu becomes the global navigation visible across all sites. EPC Group designs mega menus using card sorting exercises with real users to ensure the information architecture matches how employees actually look for resources.
How do you brand a SharePoint modern intranet?
SharePoint modern branding covers four layers: 1) Theme — apply a custom theme with organizational primary, secondary, and accent colors using the SharePoint theme generator (JSON format) or the admin-applied company theme, 2) Header layout — choose Extended, Compact, or Standard header; set the logo, site title, and background color, 3) Footer — enable site footer with company links, legal disclaimers, and social media icons, 4) Custom fonts — turn on the SharePoint brand center, which a Global Administrator sets up in the Microsoft 365 admin center, to manage organizational fonts, colors, and images (Microsoft Learn, accessed 2026-10-27). Limitations: SharePoint Online does not support custom CSS or master pages in modern sites — all branding must use the supported customization surfaces. EPC Group creates brand-compliant themes that maintain accessibility standards (WCAG 2.1 AA contrast ratios) while reflecting the organization visual identity.
How do you make a SharePoint intranet mobile-responsive?
SharePoint modern sites are mobile-responsive by default — the page layout, web parts, and navigation automatically adapt to screen size. However, mobile optimization requires specific design decisions: 1) Test every page on actual mobile devices (not just browser resize) — web parts render differently on iOS and Android, 2) Use single-column sections for critical content — multi-column layouts stack vertically on mobile and may push important content below the fold, 3) Keep Quick Links to 8 items or fewer — long lists become unwieldy scroll lists on mobile, 4) Use the Hero web part with 1-2 tiles on mobile-first pages (5-tile layouts compress poorly), 5) Deploy the SharePoint app in Teams (formerly Viva Connections) for a mobile experience with the dashboard, News, and resources (Microsoft Learn, accessed 2026-10-27). EPC Group validates every intranet deployment on iPhone, Android, iPad, and the Teams mobile app before launch.
How do you measure SharePoint intranet adoption and engagement?
SharePoint provides built-in analytics at three levels: 1) Site analytics — unique viewers, page views, site visits over time (available to site owners via Site Usage), 2) Page analytics — individual page views, unique viewers, average time on page, traffic sources, 3) Hub analytics — aggregated usage across all sites associated with a hub. For deeper insights, integrate with Microsoft Viva Insights (workplace analytics), Microsoft 365 usage reports (admin center), and Azure Application Insights (custom telemetry). Key metrics to track: Daily/Monthly Active Users (DAU/MAU), pages per session, search success rate, news article engagement rate, and mobile vs desktop usage ratio. EPC Group establishes baseline metrics at launch and tracks adoption weekly for the first 90 days, with monthly reporting thereafter.
What is the best strategy for launching a SharePoint intranet?
A phased launch strategy maximizes adoption and minimizes disruption. EPC Group recommends: Phase 1 (Soft Launch, Week 1) — deploy to a pilot group of 50-100 champions from each department, collect feedback on navigation, content, and usability. Phase 2 (Department Rollout, Weeks 2-4) — launch to one department per week, starting with the most engaged departments (often HR or Communications). Phase 3 (Organization-wide, Week 5) — full launch with CEO announcement, email campaign, Teams notification, and all-hands demo. Phase 4 (Optimization, Weeks 6-12) — monitor analytics, address usability feedback, add requested features, and decommission the old intranet. Critical success factors: executive sponsorship (CEO or CHRO sends the launch announcement), a dedicated intranet content team (minimum 2 FTEs), and training sessions (live and recorded) covering search, news, and mobile access.
What are the best tips for setting up a SharePoint intranet site?
The best tips for setting up a SharePoint intranet site are to agree on goals and priority content with business owners, then build the home site, hubs, and sites in that order (Microsoft Learn, accessed 2026-10-27). Start the home site from a communication site, swap it into the root site location, turn on page approval, and check performance with the Page diagnostics for SharePoint tool (Microsoft Learn, accessed 2026-10-27). Test the site architecture with real users before launch; EPC Group sets up that testing for clients.
What is the best way to set up a SharePoint intranet structure?
The best way to set up a SharePoint intranet is a flat structure: one site for each discrete topic, task, or unit of work, connected by hub sites instead of subsites (Microsoft Learn, accessed 2026-10-27). Subsites aren’t recommended in modern SharePoint, and hubs model relationships as links, so sites can move between hubs when the organization changes (Microsoft Learn, accessed 2026-10-27). For the end-to-end picture, see EPC Group’s answer: How does an intranet work, and how is one built on SharePoint?
Should a SharePoint intranet site be a team site or a communication site?
Use a communication site for intranet pages that broadcast news, policies, and services to a wide audience, and a team site where a group works together on shared files and tasks (Microsoft Support, accessed 2026-10-27). Communication sites have a small number of authors and many readers, while every team site member is an author and the site connects to a Microsoft 365 group by default (Microsoft Learn, accessed 2026-10-27). Hub sites then connect both types into families of related sites (Microsoft Learn, accessed 2026-10-27).
What are SharePoint design best practices for intranet pages?
Good SharePoint page design puts the most important information at the top and tells readers where they are, what they can do there, and where they can go next (Microsoft Support, accessed 2026-10-27). Use sections, headings, and bullets, favor pages over documents, give every image alt text, and build the home page last (Microsoft Support, accessed 2026-10-27). For design ideas, Microsoft points site owners to the SharePoint Look Book (Microsoft Learn, accessed 2026-10-27).
How should you design a SharePoint department site?
Design a SharePoint department site as a communication site that showcases the department’s services to everyone, and give the department’s own working group a separate team site (Microsoft Learn, accessed 2026-10-27). When a department offers several distinct services, such as HR benefits, pay, and recruiting, Microsoft suggests one site per function joined by a department hub that shares navigation, branding, and a scoped search (Microsoft Learn, accessed 2026-10-27). Keep at least two owners on each site (Microsoft Support, accessed 2026-10-27).
Related Resources
SharePoint Consulting Services
Enterprise SharePoint implementation, migration, and managed services from EPC Group.
Read moreSharePoint Intranet Examples
Real-world enterprise intranet designs with screenshots, architecture diagrams, and adoption metrics.
Read moreViva-Powered Intranet Guide
Integrating Viva Connections, Viva Engage, and Viva Learning into your SharePoint intranet experience.
Read moreDesign Your Modern SharePoint Intranet
Schedule a free intranet assessment with EPC Group. We will evaluate your current intranet architecture, identify adoption gaps, and deliver a modern SharePoint intranet design built for measurable adoption.
SharePoint Architecture: 2026 Considerations for SharePoint Modern Intranet Design Best Practices 2026
Microsoft Purview information protection on SharePoint Online has matured significantly through 2026: sensitivity labels can now auto-classify based on Microsoft 365 Copilot grounding hints, container labels enforce sharing controls at the site level, and Purview content explorer surfaces unauthorized PHI/PII exposure in real time. For HIPAA-regulated tenants, the combination of auto-labeling plus sensitivity-aware DLP plus Audit (Premium) retention policies — one year by default for SharePoint and OneDrive records, up to ten years with the 10-Year Audit Log Retention add-on (Microsoft Learn, 'Audit log retention policies', accessed 2026-10-21) — is the audit-defensible posture.
SharePoint Premium (formerly Syntex) document processing brings AI-powered metadata extraction, unstructured document classification, and prebuilt Document Understanding models to enterprise content management. Since Microsoft retired the per-user licenses, the services are billed pay-as-you-go against an Azure subscription (Microsoft Learn, Licensing for document processing, read 2026-10-22); at Fortune 500 scale the annual total scales with document volume, justified primarily through reduced manual data-entry labor and tighter retention compliance.
Decision factors EPC Group evaluates
- Audit (Premium) retention policies for SharePoint and OneDrive activity — one-year default, up to ten years with the 10-Year Audit Log Retention add-on
- Sensitivity label rollout with auto-classification rules
- Microsoft Purview content explorer for unauthorized PHI/PII discovery
- Hub-spoke information architecture redesign vs legacy flat-IA
- Migration tool selection (Microsoft native vs ShareGate vs AvePoint) by complexity tier
See related EPC Group services or schedule a discovery call.