Intranet migration

Migrate a legacy intranet to modern SharePoint

Moving from classic SharePoint, an on-prem intranet or a third-party platform? Inventory, decide, rebuild and switch over — with every change reviewed.

Updated

Quick answer

Migrating an intranet is mostly a content decision, not a copy job. Inventory what exists, keep only owned and current content, rebuild on modern communication and hub sites, redirect old links, and launch with a clear owner model. Lift-and-shift moves the mess with you.

Common starting points

  • Classic SharePoint publishing sites
  • SharePoint Server (on-premises)
  • Third-party intranet platforms reaching end of contract
  • A shared drive pretending to be an intranet

The migration plan

  1. 1Inventory pages, documents and owners
  2. 2Decide keep / rewrite / archive for each area
  3. 3Generate the new structure from a template or your website
  4. 4Move documents with metadata; archive the rest
  5. 5Set up redirects and announce the switch-over

Where tools fit

Bulk migration tools move files well. IntraBuilt focuses on the parts they don't: deciding structure, generating modern pages, and cleaning permissions as reviewed change sets.

Keep reading

Talk to a SharePoint specialist

See IntraBuilt build, tidy and govern an intranet live — with every change reviewed before it's applied.