MIGRATION PATH · SCHEMA-AWARE

Migrate SharePoint to SharePoint

MigrationFox handles SharePoint Online to SharePoint Online migrations end-to-end — document libraries, lists, content types, list views, native version history, site pages with web parts, and cross-tenant permission mapping — in a single coordinated job. Same-tenant moves can route through Microsoft’s native SharePoint Migration API for original Author / Editor / Created / Modified preservation. The wizard at /sharepoint/new in the dashboard is the entry point.

Which Dashboard Wizard to Use

The dashboard has two wizards that both accept SharePoint — the difference matters:

• SharePoint & OneDrive (this guide) — for SP→SP or OneDrive→OneDrive. Schema-aware: lists, content types, views, native versions, optional True History Mode. Same platform on both sides.
• File Migration — for moving SP→Google Drive, SP→Box, Dropbox→SP, etc. Generic cross-platform copy with permission mapping. Different platforms on either side.

If you’re unsure: same platform on both sides → SharePoint & OneDrive wizard; different platforms → File Migration. The walkthrough below assumes the schema-aware wizard.

What Gets Migrated

• Document libraries — files, folder hierarchy, custom metadata columns, and version stacks
• Lists and list items — all list types including custom lists, with column values preserved
• Content types — site-collection and list-scoped, including custom site columns and inheritance
• List views — visible columns, sort and filter rules, view scope (all items / personal / etc.)
• Native version history — full version stack on libraries and lists; optionally backed by True History Mode for original Author/Editor preservation
• Site pages and web parts — modern pages with classic and SPFx web parts (custom SPFx web parts need to be deployed to the destination app catalog first)
• Cross-tenant permissions — per-item permissions mapped by email; unresolved users logged for review

True History Mode

MigrationFox ships two version-history paths; the SharePoint & OneDrive wizard lets you pick per job:

• Graph path (default). Service-account or delegated OAuth via Microsoft Graph. Works across any tenant pair — same-tenant, cross-tenant, GCC, GCC High. Top-level Author and Modified columns on newly-created list items reflect the migration account; original values live in a per-item MigratedVersionHistory sidecar column you can query for audit.
• True History Mode. Runs the site through Microsoft’s native SharePoint Migration API. Original Author, Editor, Created, Modified and the full version stack are preserved on the destination exactly as they were on the source. Same-tenant SharePoint only, delegated OAuth sign-in (not service-account), and an Azure Blob staging account — we can provision the staging account for you. Toggle on the Options step.

Six-Step Walkthrough

1. Connect both tenants. Sign in to source and destination from the Credentials page using delegated OAuth (required for True History Mode). The Verified Publisher badge on the consent screen confirms it’s MigrationFox Inc.
2. Open the SharePoint & OneDrive wizard. Dashboard → Migrations → SharePoint & OneDrive card → Start Migration.
3. Pick source and destination sites. The path browser surfaces every site and library you have permission to read. Both /sites/<name> and /teams/<name> styles work.
4. Configure scope on the Options step. Toggle libraries, lists, content types, views, version history, True History Mode, and permission mapping. Defaults are sensible for typical migrations; the system list defaults are unchecked because most teams don’t want them.
5. Review and start. Pre-flight scan runs first and surfaces blockers (long paths, case collisions, reserved names) before you commit. Start the job once findings are addressed.
6. Monitor and verify. Live progress with per-phase percentages, plus a CSV manifest on completion that lists every item migrated, every permission mapped, and every skipped item with reason. Re-run as Delta to catch anything changed since.

Common Scenarios

Tenant Consolidation (M&A)

Two SharePoint tenants merging into one. Use the schema-aware wizard with cross-tenant permissions enabled and a CSV mapping file for user accounts. True History Mode isn’t available across tenants — the sidecar version-history column handles the audit-trail requirement.

Site Restructuring (Same Tenant)

Splitting a hub site into multiple sub-sites or merging fragmented sites into a single hub. Same-tenant means True History Mode is on the table — original Author and timestamps land natively on the destination. Pair with the Restructuring assessment for the inventory side.

Migration to a New Information Architecture

Moving content into a new content-type model. MigrationFox can remap content-type IDs during migration so legacy items adopt the new schema as they arrive on the destination.

Pricing

SharePoint to SharePoint migrations are billed at $0.50 per GB transferred (CAD). True History Mode doesn’t carry a premium — same rate as the Graph path. Your account starts with 2 GB free — no credit card required. Pre-flight scans are always free and unlimited.

Related Reading

• SharePoint platform page — the full connector reference
• Full SharePoint Site Migration — deep-dive on schema-aware mode
• SharePoint Site Migration — alternate framing focused on phase ordering
• Cross-tenant SharePoint permissions — how the user-resolution logic works for M&A
• SharePoint migration best practices — what to do before pressing Start