What Tauri Migration migrates, and what it does not
The exact list, phase by phase, so you know before you start what will land in the target and what you will have to rebuild by hand.
Short answer
Taxonomy, site structure, files and items with all their versions, original authors and dates, permissions and groups. Not migrated: modern pages and web parts, workflows and Power Automate flows, Teams, sharing links.
By phase
| Item | Migrated | Details |
|---|---|---|
| Global term store | Yes | GUIDs kept within one tenant, copied otherwise |
| Site collection term groups | Yes | New GUIDs, with a mapping table applied to columns and values |
| Site columns and content types | Yes | Copied one by one: a refusal is reported without blocking |
| Lists, libraries, settings, views | Yes | Lookup columns migrated in dependency order |
| Subsites | Yes | Created by the tool; the target site collection must exist |
| Files and list items | Yes | Including attachments |
| Version history | Yes | Replayed in order; major and minor versions respected; version count can be capped |
| Created by, Modified by, dates | Yes | Original values, translated to target accounts |
| Permission levels and SharePoint groups | Yes | Built-in levels matched by type: works across sites in different languages |
| Broken inheritance | Yes | Sites, lists, folders and items |
| OneDrive | Yes | Documents library and lists; folder and file sharing carried over |
| Document sets | Partial | Migrated as folders |
| Modern pages and web parts | No | Site Pages library excluded by default |
| Workflows and Power Automate flows | No | Rebuild them in the target |
| Teams (channels, conversations) | No | Only the files of the connected sites can be migrated |
| Sharing links | No | Direct sharing with people is carried over |
| Branding and navigation | No |
By source and target
| Pair | Scope | What is kept |
|---|---|---|
| Site to site | Whole site or folder pairs | Everything listed above |
| OneDrive to OneDrive | Whole OneDrive or folder pairs | Versions, metadata, sharing |
| Site to OneDrive, and back | Folder pairs | Versions, metadata, unique permissions |
| File share to site or OneDrive | Folder pairs | File dates, NTFS owner as author; one version per file |
| Site or OneDrive to file share | Folder pairs | Current version, created and modified dates |
| Site to site in the same tenant | Whole site or folder pairs | Everything; a single sign-in; accounts stay the same |
NTFS permissions on a file share are not carried over: files take the permissions of the target library. Details are on the file share to SharePoint page.
Re-runs and cutover
- Incremental mode: only items that are new, changed at the source or deleted from the target are sent again. An interrupted run resumes at the exact version.
- Full mode: everything is sent again and the target overwritten, while keeping existing item IDs so lookup columns and permissions keep working.
- Target re-checked on every pass: an item deleted in the target is recreated, even if it did not change at the source.
- Fast mode: new library files are imported in packages through the SharePoint Migration API, with several jobs in parallel.
Planning and tracking
- Projects and actions: a project holds the connections to both tenants; each action is one migration with its own sources, options and state database. Several actions can run at once.
- Excel template: one row per source and destination pair. The whole file is checked before import, each error with its row number.
- Identity mapping: rules by domain, user, Entra group, and by SID for file shares. A fallback account replaces unknown authors, and never receives their permissions.
- Live tracking: phases, counters, volume gauge, throughput, time remaining, filterable log, stop and resume.
- Reports: a CSV per run with successes, warnings and errors; the full log is archived.
- Command line: the same actions run without the interface, for scheduled runs.
Installation and security
- Windows 10, Windows 11 or Windows Server, 64-bit. The installer runs per user, without admin rights, and ships its own .NET runtime.
- Sign-in to each tenant through the tool's Entra application after admin consent, or through your own app registration. Certificate mode is available for unattended runs.
- Tokens are kept in a cache encrypted by Windows (DPAPI), tied to the workstation.
- The licence is checked on the workstation and works for 30 days without reaching the licence server.
Frequently asked questions
Do target sites need to exist before migrating?
Yes for site collections and OneDrive accounts: they must exist. Subsites, lists, libraries, columns and content types are created by the tool.
Do users need to exist in the target tenant?
Yes. The tool never creates Entra accounts or groups. It translates source accounts to target accounts with the identity mapping table.
Are version numbers preserved?
The order of versions and their type, major or minor, are preserved. The numbers themselves are recalculated by SharePoint in the target.
Can I migrate only some folders?
Yes. A site pair can be limited to folder pairs, each going to any folder in the target, with or without recreating the source folder.
Test it on your own tenant
The 14-day trial migrates 10% of every library, with versions, metadata and permissions. After you subscribe, an incremental run migrates the rest.