If your intranet is still on SharePoint Server 2016 or 2019, the clock is ticking — but the bigger risk is not the deadline. It is what happens when organizations rush. They move everything, carry forward the same cluttered structure and brittle workflows, and then wonder why adoption does not improve.

This checklist is designed to prevent that. It is a phase-by-phase plan to help you migrate with control: discover what you actually have, cut scope before it cuts you, modernize workflows early, and roll out in waves so employees are never left stranded.

If you need the broader context — including replacement paths like SharePoint Server Subscription Edition (SPSE), SharePoint Online, and dedicated SharePoint intranet replacement platforms — start with the SharePoint 2016/2019 end of life and replacement options guide, then come back here.

A note on speed: migrations do not have to be multi-quarter projects. With tight scope control and a phased rollout, some organizations migrate from SharePoint on accelerated timelines measured in weeks, not months — especially when the intranet experience is rebuilt cleanly instead of dragged forward. MangoApps has supported 98% of deployments delivered on time and within budget. Learn more about MangoApps Success Services for Migration.

Who this checklist is for

This migration checklist is written for the cross-functional team that owns a SharePoint 2016/2019 intranet from different angles. It is most useful for:

• IT and SharePoint administrators responsible for the SharePoint Server 2016/2019 environment, identity, security, and technical dependencies
• Internal Communications, HR, and Operations leaders who own the intranet experience employees actually see and rely on
• Security and compliance stakeholders who need a defensible plan for risk reduction, data retention, and governance
• Department site owners and publishers who manage policies, procedures, training, and operational updates
• Organizations with multiple locations, multiple languages, and frontline-heavy workforces, where intranet access and adoption cannot be desk-worker only

Use this as a shared checklist across teams — not an IT-only plan. The organizations that migrate fastest are the ones where IT, Comms, HR, and Operations are aligned from day one.

Before you migrate: choose your destination

Your destination changes the work. Migrating SharePoint Server 2016/2019 to SPSE, SharePoint Online, or a dedicated SharePoint intranet replacement platform are all valid paths — but they do not share the same workflow, customization, and access assumptions.

• SPSE: best when you must stay on SharePoint on-prem and want a supported path forward
• SharePoint Online: best when you are all-in on Microsoft 365 and ready to modernize workflows and classic-era patterns
• Dedicated intranet platform: best when the goal is a clean rebuild that improves adoption, findability, and frontline reach

If you are still deciding, use the SharePoint 2016/2019 end of life and replacement options guide first, then return to this checklist once the destination is set.

What changes based on your destination

Workflows and forms: If you are moving into Microsoft 365, plan for workflow modernization — do not assume old workflows come along. If moving to SPSE, decide whether you are keeping legacy patterns or using the migration as an opportunity to simplify. If moving to a dedicated platform, validate how requests, approvals, and intake processes work natively.

Customizations and web parts: If your SharePoint 2016/2019 intranet relies on classic web parts, scripts, or custom master pages, modernization is usually the real work item — not content copying. If you are replacing the platform, decide which customizations employees truly rely on versus which exist out of habit.

Identity and access for frontline employees: If your workforce includes deskless roles, validate how employees authenticate and how content is targeted by role, location, shift, and language before you start moving anything. Check our article on Frontline Intranet Requirements here.

Governance: No matter where you migrate, governance determines whether the new intranet stays healthy or decays back into sprawl. Define roles, review cycles, and publishing standards before your first wave goes live. See our Intranet Governance Plan article for more.

Phase 1: Inventory and discovery

This phase is where SharePoint migrations either stay manageable or turn into a slow, expensive surprise. The goal is simple: build a factual map of what exists today, what it depends on, and what people actually use. That gives you the leverage to cut scope, sequence the work, and avoid breaking business-critical processes.

Environment inventory

Capture the basics in one place. Skipping environment details is what slows down cutover and decommissioning later — not content.

• Farms, web apps, site collections, and subsites
• Authentication model and SSO patterns
• External access points and any internet exposure
• Storage, SQL configuration, backups, and disaster recovery posture
• Search configuration: service applications, crawl schedules, content sources

Customizations and dependency inventory

This is where SharePoint intranets usually hide their real complexity. Prioritize anything that affects authentication, affects publishing, or drives an operational process.

• Custom solutions (.wsp), features, and anything deployed server-side
• Classic pages and scripted elements
• Custom master pages, page layouts, and branding dependencies
• Third-party add-ons and connectors
• Integrations: HR systems, ticketing, learning, file storage, identity, and directories

Workflow and forms inventory

Treat workflows as a risk list, not a nice-to-have. In many intranets, workflows are the backbone of how work actually moves — and legacy workflow dependencies are the most common source of migration surprises.

• SharePoint Designer workflows
• Any SharePoint 2013 workflow engine dependencies (these stop working April 2, 2026)
• InfoPath forms and legacy form solutions
• Approvals tied to business processes: HR requests, policy approvals, service requests, onboarding steps

Usage and value assessment: what actually matters

Most SharePoint 2016/2019 intranets have more content than anyone realizes. Migrating everything is how projects blow up. Focus on identifying:

• The top destinations employees actually use today
• Mission-critical journeys: find a policy or SOP, submit a request, complete onboarding tasks, get location-specific updates, see leadership or operational communications
• Areas that are duplicated, abandoned, or have no clear owner

If you cannot name an owner for a section of the intranet, it is already decaying — and it does not deserve to be migrated.

Phase 2: Content cleanup and scope control

Content cleanup is not busywork. It is scope control. Done well, it reduces migration effort, improves search trust, and gives employees a cleaner intranet on day one. Skipped, it means paying for the migration twice: once to move the mess, and again to fix it after people stop using it.

Content triage rules

• Keep and migrate: current, accurate, actively used content with a clear owner
• Keep but rewrite: important content that is outdated, inconsistent, or poorly structured
• Consolidate: duplicates spread across departments and sites — common with policies and procedures
• Archive: content required for retention but not needed day-to-day
• Delete: stale content with no owner and no requirement to keep

ROT cleanup (redundant, outdated, trivial)

ROT content is the main reason employees do not trust intranets. It also makes search worse, because outdated content competes with current answers. Common ROT hotspots in SharePoint 2016/2019 intranets:

• Duplicate policy libraries across departments
• Old PDFs that were replaced but never removed
• Announcements and news items that never got retired
• Departmental sites that outlived the org structure they were built for

Simple rule: if a page has no clear owner and no known audience, it does not get migrated.

File and document hygiene

Before moving documents, address:

• Duplicate files and multiple versions labeled "final"
• Orphaned documents with unclear ownership
• Broken permission inheritance and one-off access grants
• Naming conventions and minimal metadata standards

Permissions and findability are significantly harder to fix after migration. Clean them now.

Multi-language and multi-location planning

If your intranet serves multiple locations or languages, decide early: will content be centralized with localized variants, or owned locally? Who owns translation and review cycles? What content must be location-specific — policies, schedules, safety procedures? How will content targeting work in the new platform?

Localization is the most common place where timelines slip, because the work gets discovered late. Surface it now.

Strategic note: content cleanup is one of the simplest ways to accelerate a SharePoint migration. When organizations tighten scope early, phased rollouts compress significantly.

Phase 3: Redesign site structure, navigation, and findability

Migrating content without redesigning how people find and use it recreates the same intranet problems on a new platform. This phase is about building a structure employees can actually navigate and a search experience they will trust.

Build an employee-first structure

Start with what employees come to the intranet to do — not with the org chart. In most organizations, the highest-value destinations are predictable:

• Policies and benefits
• How-to procedures and SOPs
• Tools and requests: forms, services, approvals
• Onboarding and training resources
• Location or department updates
• Leadership and operational communications

Keep the top navigation short and scannable. Create consistent hubs for the major employee needs. Put services and requests in one place so employees are not hunting through departmental sites. Treat locations as first-class citizens if you operate across sites.

If your SharePoint intranet also needs to serve frontline teams, validate early that the destination supports content targeting by role, location, and shift — and that the mobile experience makes those areas easy to reach. See the Frontline Intranet Requirements guide for the full checklist.

Standard templates that prevent sprawl

Templates prevent 80% of intranet sprawl. Define a small set of standards and enforce them:

• News and updates template: consistent structure, targeting rules, and expiry guidance
• Policy template: owner, effective date, review date, versioning, and what changed
• SOP template: steps, tools needed, safety notes, escalation path, and contact
• Request or service template: required fields, who approves, and how status is communicated
• Location template: hours, contacts, safety, local SOPs, and local updates

Search and findability plan

Intranet migrations fail quietly when employees stop trusting search. Do not tune it later — plan findability as part of migration.

• Define a small metadata and tagging model that people will actually use
• Add synonyms for the words employees use, not the words the system uses
• Create featured results for critical policies, SOPs, and forms
• Standardize page titles so search results are readable and consistent

A practical technique: identify the top 25 searches employees run today — or the top 25 questions HR and IT receive repeatedly — then design your new intranet so those answers surface in seconds. McKinsey research shows employees spend 20% of their workday searching for information. AI-powered search can cut that by 25–30%, turning search improvement into a measurable operational win.

MangoApps callout: If reducing repetitive HR and IT questions is a goal, factor AI-powered self-service into your content structure early. MangoApps AI is grounded in your internal knowledge base — so employees get trusted answers, not guesses. Learn more at mangoapps.com/ai.

Phase 4: Governance design

Governance is what keeps an intranet healthy after launch. Without it, content gets stale, ownership becomes unclear, and employees revert to asking people instead of using the platform. Governance does not start at go-live — it starts during discovery.

Roles and responsibilities

Define these roles before you migrate content:

• Executive owner: keeps the intranet aligned to business priorities and removes blockers
• Platform owner: accountable for the intranet as a product, not a project
• Department owners: accountable for accuracy of their content
• Publishers and approvers: keep publishing distributed without losing control
• Local or location owners: critical for frontline-heavy organizations

If you cannot assign an owner to an area of content, that content is already at risk.

Publishing workflows and guardrails

Your governance model should answer: who can publish what? When is approval required? What content must have review dates? What content expires or gets archived automatically? What are your permission standards?

Guardrails matter because they prevent well-meaning teams from creating their own intranets inside the intranet.

Measurement and continuous improvement

Pick a small set of metrics that tell you whether the intranet is working:

• Adoption and return usage — a healthy intranet targets 60–70%+ employees using it regularly
• Search success: did people find what they needed?
• Content freshness: how much is out of date?
• Reduction in repetitive questions and support tickets

MangoApps callout: The organizations that keep their intranet strong treat it as an ongoing partnership between platform owners and business owners — not a project with a go-live finish line. See MangoApps Ongoing Partnership for how we support customers after launch.

Phase 5: Workflow, forms, and customization modernization

This phase is where SharePoint 2016/2019 projects often get stuck. The intranet is rarely just pages and documents — it is also processes, procedures, and workflows. Separating what employees truly rely on from what exists because it was built at the time is the most important judgment call in this phase.

Workflow modernization checklist

• Identify workflows tied to real operational outcomes: approvals, requests, escalations
• Remove steps that exist only because the old process was clunky
• Decide your target approach based on destination: Microsoft 365 path → rebuild as modern workflows; SPSE path → modernize where possible to reduce future upgrade friction; replacement platform path → use platform-native workflows and approvals
• Ensure auditability for anything compliance-sensitive

Note: SharePoint 2013 workflows are removed from all Microsoft 365 tenants on April 2, 2026. If your environment has any of these, treat them as urgent modernization items — not migration cargo.

Forms modernization checklist

• Inventory all forms and identify who owns them
• Identify forms tied to real workflows and approvals
• Standardize intake fields and routing rules
• Decide what data must be retained, and where

Customizations modernization checklist

• Inventory custom web parts, scripts, and classic pages
• Identify what employees truly use versus what exists out of habit
• Retire custom master pages where possible
• Standardize how you will handle new needs going forward — so you do not rebuild the same complexity

Data and integration checklist

• Identity mapping: groups, roles, locations
• HR profile data and org structure inputs
• Document repositories and retention rules
• Ticketing and request systems
• Integrations required for frontline workflows

Validate integration ownership as well. Integrations often fail post-launch because nobody owns data quality and mapping long-term. MangoApps connects with 200+ enterprise systems — see mangoapps.com/integrations for the full list.

Phase 6: Migration execution

This is where you stop planning and start proving.

Pilot design

Pick two to three areas that will clearly demonstrate whether the new intranet is better than the old one. Good pilots are high-use and high-visibility:

• Policies and SOPs
• A major service or request flow
• A location hub for frontline teams
• Leadership communications

Define success criteria up front: can employees find what they need faster? Are key tasks completed without support intervention? Are publishers able to keep content current?

Strategic reminder: MangoApps has supported SharePoint-to-modern-intranet migrations on accelerated timelines measured in weeks, not months — when pilots are tightly scoped and run as repeatable waves. 98% of MangoApps deployments are delivered on time and within budget.

Wave-based rollout

Avoid a big-bang launch unless you have no choice. Common rollout models: by department, by location, or by function (policies first, then services, then communities). Operational rules that prevent chaos:

• Define what content is frozen and when
• Publish old-to-new mapping so employees know where to go
• Train publishers separately from general employees
• Schedule office hours for the first few waves

Change management that actually works

Employees do not resist change. They resist confusion. What consistently works:

• Simple "where to go now" guidance for top tasks
• Short videos or one-page guides
• An internal feedback loop that results in visible improvements
• Office hours for the first 30–60 days after launch

If you have a frontline workforce, plan change management around how those employees actually access information — not how corporate teams do.

MangoApps callout: When a migration is also an experience rebuild, the platform matters. The easiest way to reduce confusion is to consolidate communications, resources, and actions in one place so employees stop bouncing across tools. Learn more at mangoapps.com/why-mangoapps.

Phase 7: Cutover, decommissioning, and risk controls

A migration is not complete until the old intranet is retired responsibly.

Cutover checklist

• URL mapping and redirects — protect your top pages and common entry points
• Final permissions validation
• Final content freeze window and communications plan
• Post-launch validation: search returns expected results, top workflows function end to end, mobile experience works for key roles, frontline access works in real conditions

Decommission checklist

• Archive and retention requirements confirmed
• Legal holds handled
• Final exports and backups stored appropriately
• Shutdown sequence documented and executed
• Licenses and contracts cleaned up
• Support processes updated so tickets do not route to the old system

If you must run SharePoint Server 2016/2019 past end of support

Sometimes timelines do not cooperate. If you have to run past the July 14, 2026 deadline, treat it as a controlled exception — not business as usual:

• Restrict access to only what is necessary
• Reduce external exposure
• Tighten monitoring and review cadence
• Document risk acceptance and compensating controls
• Keep the retirement plan visible, time-bound, and actively managed

Common pitfalls to avoid

These are the patterns that consistently derail SharePoint 2016/2019 intranet migrations:

• Treating the migration as an IT-only project
• Migrating everything instead of triaging content and reducing noise
• Leaving workflows and forms to the end
• Keeping the same site structure and navigation
• Launching without governance and review cycles
• Ignoring frontline access until after go-live
• Not defining what success looks like — and then arguing about it at launch

Suggested timeline

Timelines vary based on customization depth and how much content you choose to carry forward. The biggest drivers are discovery quality, scope discipline, and rollout approach. A practical way to think about it:

• Discovery and inventory: typically measured in weeks, not days
• Cleanup, site structure redesign, and governance setup: commonly another few weeks
• Pilot and workflow modernization for critical processes: varies most, depending on what you find during discovery
• Wave rollout and decommissioning: fastest when designed as repeatable waves

MangoApps note: With tight scope and repeatable rollout waves, migrations can move quickly. MangoApps has supported SharePoint-to-modern-intranet migrations on accelerated timelines measured in weeks — when the prerequisites are handled early and scope is disciplined. Our typical implementation timeline is 8–12 weeks.

Next steps and support

The fastest way to reduce migration risk is to do two things early: map dependencies and cut scope.

A migration readiness assessment answers: what you have (content, workflows, customizations), what you can retire or archive, what must be rebuilt, and what your phased rollout should look like.

MangoApps provides services that help customers migrate and set up the new intranet for long-term success — including accelerated migrations when scope and rollout are designed well:

• Success Services: mangoapps.com/success-services
• Implementation process: mangoapps.com/services/implementation-process
• Add-on services for specialized needs: mangoapps.com/services/add-ons
• Ongoing partnership after launch: mangoapps.com/services/ongoing-partnership

If you are considering a replacement platform (not just an upgrade), these are good starting points:

• MangoApps AI-Powered Intranet: mangoapps.com/solutions/modern-intranet
• Why MangoApps: mangoapps.com/why-mangoapps
• MangoApps Integrations: mangoapps.com/integrations
• MangoApps AI: mangoapps.com/ai

FAQ

How long does a SharePoint Server 2016/2019 intranet migration take?

It depends on how customized the intranet is and how much content you choose to carry forward. The biggest timeline drivers are workflow modernization and content cleanup. Teams that triage content early and roll out in waves move fastest and avoid rework. MangoApps' typical implementation timeline is 8–12 weeks, and 98% of deployments are delivered on time and within budget.

What should we migrate versus archive?

Migrate what is current, used, and owned. Archive content required for retention but not needed day-to-day. Delete what is stale and ownerless. If you migrate everything, you import clutter and reduce employee trust in the new intranet from day one.

What do we do with SharePoint Designer workflows and legacy forms?

Treat them as modernization work items — not migration cargo. Inventory them early, identify which ones drive real business processes, and rebuild them in a modern workflow approach or platform-native workflows depending on destination. Note that SharePoint 2013 workflows are removed from all Microsoft 365 tenants on April 2, 2026 — any dependencies on these are time-sensitive.

What are the most common SharePoint 2016/2019 migration pitfalls?

Skipping discovery, migrating everything without triage, leaving workflows to the end, keeping the same site structure and navigation, and launching without governance. The teams that avoid these five mistakes consistently move faster and land with higher adoption.

What is the difference between moving to SharePoint Online versus replacing the intranet?

Moving to SharePoint Online keeps you in the Microsoft ecosystem and typically reduces infrastructure overhead, but it often requires significant modernization of classic-era patterns. Replacing the intranet with a dedicated platform like MangoApps is usually chosen when the goal is a cleaner rebuild with better adoption, findability, and frontline reach — and when the current SharePoint environment has accumulated too much customization debt to migrate cleanly.

How do we avoid recreating the same intranet problems in the new system?

Redesign the site structure and navigation around employee needs, clean up content before migration, standardize templates, modernize workflows early, and put governance in place before launch — not after. The intranet should be treated as a product with a continuous operating model, not a project with a finish line.