SharePoint → SharePoint: which mode to use
The SharePoint & OneDrive wizard (on the web and in MigrationFox for Windows) gives you a few choices that decide what lands at the destination: what to copy, whether to keep version history, whether to keep original authors and dates, and what to do on re-runs. This page explains each one and when to pick it.
See also: Schema-aware coverage: what migrates by default and what needs a toggle.
Decision tree
Do you need the whole site rebuilt (lists, content types, views, pages)? ├─ YES → Full site copy └─ NO → Content only (pick libraries, lists, pages or a folder) Then: do you need original authors and dates on every file and version? ├─ YES → True History Mode (empty destination, Sign in with Microsoft) └─ NO → Need earlier versions anyway? ├─ YES → Migrate version history (dates show migration time) └─ NO → Regular copy (latest version only) Running it again later for changes only? └─ Incremental (only new or changed files; not with True History)
Step 1: Full site copy or Content only
Full site copy
Rebuilds a whole site at the destination, either a new site or one you already have. It brings across every library with its folders and files, every list with its columns and items, site pages with their layout and web parts, site content types and list views, and file sharing permissions if you turn them on.
Still in early access (switching on for every account soon): site look and navigation, library settings, permission levels and groups, subsites, and updating links that point at the old site. See SharePoint site migration for the details.
Content only
Moves the libraries, lists and site pages you pick (or a single folder) into a site that is already set up. It leaves the destination site’s settings, content types, views and navigation alone. Use it to add content to an existing site, consolidate sites, or move OneDrive content into SharePoint.
Step 2: How much history to keep
Regular copy (both options off)
Copies the current version of each file through Microsoft Graph. The file keeps its original Created and Modified dates, but Created By and Modified By show the migrating account. This is the simplest path.
Migrate version history
Copies earlier versions too. Each version is uploaded oldest first, so the destination gets one version per upload. Outside True History Mode, those versions show the migration time and the migrating account, not the original ones. The Per-file version cap limits how many recent versions are copied per file: leave it empty to copy every version up to 500, or enter a number from 1 to 500 to keep only that many of the most recent. For list items, the version history is stored in a hidden _VersionHistory column.
True History Mode
Sends the content through Microsoft’s own SharePoint Migration API, so every file, version and list item keeps its original Author, Editor, Created and Modified. It works in one tenant and across tenants (with a user mapping).
- Needs a SharePoint destination connected with Sign in with Microsoft. Microsoft’s migration API doesn’t accept service accounts.
- The destination must be empty. The wizard won’t start a True History run into a folder that already has files.
- Files up to 45 GB each. Larger files are skipped and listed in the migration log; re-run them with True History Mode off.
- Files whose destination path would pass SharePoint’s 400-character limit are skipped before staging and listed in the log.
- No Azure account of your own is needed. SharePoint provides the staging storage for each run.
Full details: True History Mode.
Step 3: Transfer mode and existing files
Transfer Mode
- Copy: keeps the source intact (the default).
- Move: deletes each source file after it transfers.
- Sync Changes: copies changed files only.
If a file already exists at the destination
- Skip existing: leaves the existing file alone (the safe default).
- Copy and replace: replaces the destination file with the source version.
- Keep both: adds a suffix to the new file so both stay.
- Incremental: replaces a file only if the source is newer. Site pages follow the same rule.
Incremental re-runs (“only new or changed files”) work for SharePoint and OneDrive destinations, on MigrationFox web and in MigrationFox for Windows. Unchanged files are skipped, so a second pass copies only what changed since the first.
Quick reference
| Capability | Regular copy | Migrate version history | True History Mode |
|---|---|---|---|
| File contents and folders | Yes | Yes | Yes |
| Earlier versions | No | Yes | Yes |
Original Created / Modified dates (current version) | Yes | Yes | Yes |
Original Created By / Modified By | migrating account | migrating account | original |
| Original version dates and authors | n/a | migration time and account | original |
| Per-file size limit | SharePoint’s own limit | SharePoint’s own limit | 45 GB |
| Destination connection | Sign in with Microsoft or your own app | Sign in with Microsoft or your own app | Sign in with Microsoft only |
| Destination must be empty | No | No | Yes |
| Incremental re-runs | Yes | Yes | No (one pass) |
Lists, content types, views and site pages depend on Step 1 (Full site copy or Content only), not on these options.
Common questions
Can I use True History Mode first and then catch up later changes?
Yes. Run True History Mode once into an empty destination. For later changes, run a regular migration with Incremental. Files copied in the catch-up pass show the migration time and account.
What happens to files over 45 GB in True History Mode?
They are skipped before staging and listed in the migration log. Run a second migration for those files with True History Mode off.
The destination site looks unavailable while a True History run is importing. Is this broken?
SharePoint imports the staged content on its side, and pages in the destination library can be slow or show an error while that happens. Wait for the migration to finish before checking the destination.
How do I know which options a migration used?
Open the migration from History. The header shows Site Migration, with a True History tag when that mode was on. The Configuration card shows the mode (for example Copy, Sync Changes or Site Migration).
Can I change options mid-migration?
No. Options are set when the migration is created. To change them, cancel the migration and start a new one.
Related
- True History Mode reference: keeping original authors and dates
- SharePoint site migration overview
- Migration Rehearsal: a read-only scan of a site before the real run