PLATFORM

SharePoint Migration Tool

MigrationFox handles the full complexity of SharePoint Online migrations — document libraries, Lists, permissions, metadata columns, and even InfoPath forms. Whether SharePoint is your source or destination, MigrationFox takes care of path sanitization, permission mapping, and large-file chunked uploads automatically.

Two Migration Modes

Before you start, pick the right mode for your move — the dashboard has both as separate wizards:

• File Migration — generic cross-platform copy. Libraries and files only, mapped permissions, sanitized paths. Works between any two of the 9 file platforms (SP, OneDrive, Google Drive, Dropbox, Box, S3, Azure Blob, SFTP, SMB). Pick this when SharePoint is one side of a heterogeneous move.
• SharePoint & OneDrive (schema-aware) — covers libraries, lists, list views, and native version history out of the box. Optional with one-click toggle in the wizard: content types (site-level only, requires Sites.Manage.All admin scope), site pages with web parts (page structure migrates; web parts referencing source-tenant lists, documents, or images need manual fix-up after the move — especially cross-tenant). True History Mode preserves original Author / Editor / Created / Modified. Pick this for SP→SP, OneDrive→OneDrive, or any move where the schema matters as much as the bytes.

If you’re unsure which wizard to start, the rule of thumb: same platform on both sides → SharePoint & OneDrive wizard; different platforms → File Migration wizard.

Document Libraries

Migrate entire document libraries or specific folders within a library. MigrationFox preserves the complete folder hierarchy, file metadata (created date, modified date, author), and custom metadata columns. Files stream directly between source and destination with no intermediate storage.

True History Mode (SPMT)

Same-tenant SharePoint migrations can optionally use Microsoft’s native SharePoint Migration API (SPMT) so the original Author, Editor, Created, Modified, and the full version stack are preserved on the destination exactly as they were on the source — not on the migration service account, but on the real human who made the change. Toggle it on the Options step of the SharePoint & OneDrive wizard.

Requirements: same-tenant SharePoint, delegated OAuth sign-in (not service-account), and an Azure Blob staging account that we can provision for you. Cross-tenant moves and migrations where the source isn’t SharePoint use the default Microsoft Graph path; original author and timestamp data is preserved in a per-item MigratedVersionHistory sidecar column so the audit trail is intact even when True History Mode isn’t available.

Deep-dive guides: SharePoint Site Migration (full schema-aware walkthrough) and Full SharePoint Site Migration (content types + views + pages + permissions).

Lists, Content Types, and Views

The SharePoint & OneDrive wizard migrates list items alongside libraries: content types (including custom site-collection content types), list views (visible columns, sort/filter rules, view scope), and list items themselves with their column metadata. Phase ordering matters — content types are provisioned first, then libraries / lists, then items — so column references resolve correctly. MigrationFox handles the phase ordering automatically; you don’t configure it.

Permission Mapping

SharePoint permissions are mapped bidirectionally with other platforms:

• Read ↔ Viewer / Download-only access
• Contribute ↔ Editor / Upload access
• Full Control ↔ Owner (where supported)

When migrating into SharePoint, MigrationFox resolves source user identities to Azure AD accounts by matching email addresses. Unmatched users are logged in the migration report for manual review.

Metadata Preservation

MigrationFox preserves file metadata during migration. Created and modified timestamps are carried over, and custom SharePoint columns (choice, text, date, number) are mapped when migrating between SharePoint sites. This ensures your document management workflows remain intact after migration.

Path Sanitization

SharePoint has strict rules for file and folder names — characters like # % & { } are not allowed, and the full path cannot exceed 400 characters. MigrationFox automatically sanitizes names during transfer, replacing invalid characters and truncating paths that are too long. Every rename is logged in the migration report.

InfoPath PDF Archive

MigrationFox offers a unique InfoPath PDF Archive feature. InfoPath forms are being deprecated, and many organizations need to preserve filled-out form data. MigrationFox renders each InfoPath XML submission as a formatted PDF document and stores it in SharePoint — priced at just CA$0.15 per form.

SharePoint Server (on-premises)

MigrationFox supports SharePoint Server 2010, 2013, 2016, and 2019 sources — with support gated by the authentication model your SharePoint environment uses. We list every supported auth path here transparently so you know before signing up whether your specific deployment will work today.

Available today

• NTLM authentication via Windows agent — SharePoint Server 2010 / 2013 / 2016 / 2019 with classic Active Directory authentication. You provide a Windows service account in DOMAIN\user format, install a small Windows agent on a machine that can reach the SharePoint server (local network or VPN), and MigrationFox migrates through the agent. This covers most traditional on-premises deployments where IT can provision a non-MFA service account.

On the roadmap

• App-Only OAuth (SharePoint Add-In credentials) — covers federated environments (ADFS, SAML, MFA-required tenants) without needing a Windows user account. Your SharePoint admin registers an app via appregnew.aspx, grants permissions, and provides a Client ID + Client Secret. Works with federated SSO because app principals bypass user authentication entirely. This is the highest-priority post-launch feature.
• WS-Trust active SAML — headless authentication for ADFS environments where your admin can’t grant App-Only OAuth permissions. Username + password sent directly to the identity provider’s WS-Trust endpoint, exchanged for a federated cookie.
• Internet-direct connection (no agent required) — for SharePoint servers that are publicly reachable behind a Web Application Firewall or Conditional Access. Skips the agent download entirely.
• Pure-Kerberos environments — SharePoint deployments configured for Kerberos without NTLM fallback. Rare in 2026 but still exists in some government and finance environments.

Not sure if your deployment is supported?

Email support@migrationfox.com with three details: your SharePoint version (2010 / 2013 / 2016 / 2019), your authentication setup (classic AD / federated SSO / ADFS / Okta / other), and whether MFA is required on service accounts. We’ll tell you in one business day whether your environment is supported today, on the post-launch roadmap, or needs a custom integration. Full details: SharePoint on-premises support matrix.

Supported Migration Paths

Google Drive to SharePoint

The most common migration path. Google Workspace files are auto-exported to Office formats and landed in the correct document library.

Dropbox to SharePoint

Migrate Dropbox Business team folders to SharePoint sites with permission mapping and folder structure preservation.

Box to SharePoint

Transfer Box Enterprise content including collaborations and metadata to SharePoint document libraries.

File Server to SharePoint

Move on-prem file shares (SMB/CIFS) to SharePoint Online. NTFS permissions are mapped to SharePoint permission levels.

Key Features

• Chunked upload — files over 4 MB use SharePoint's upload session API for reliable large-file transfer
• Auto-split — large jobs split into parallel partitions for maximum throughput
• Delta sync — re-run jobs to catch only files changed since the last migration
• Site provisioning — optionally create destination sites and libraries as part of the migration
• Real-time monitoring — live progress, speed, and ETA in the dashboard

Pricing

SharePoint file migrations are billed at CA$0.50 per GB transferred. InfoPath PDF Archive is CA$0.15 per form. Your account starts with 2 GB free — no credit card required.