Look what this software can migrate without losing its structure.
| SharePoint Data | Migration Support |
| Documents | |
| Libraries | |
| Folders | |
| Sites | |
| Site collections | |
| Site Web Parts | |
| Lists | |
| Site region | |
| List Items | |
| Attachments | |
| Sensitive Labels [Within tenant (site level & file level)] | |
| Metadata | |
| Version History | |
| Permissions |
| SharePoint to SharePoint Migration | Move data from one SharePoint environment to another while maintaining the existing structure. |
| SharePoint Online to Online Migration | Migrate SharePoint Online sites & data between Microsoft 365 environments. |
| SharePoint Tenant to Tenant Migration | Move SharePoint content when changing tenants, organizations, & Microsoft 365 environments. |
| Selective SharePoint Migration |
Choose specific sites, libraries, folders, or data instead of migrating everything. |
When You Need a Certificate
If you're using Client ID, Tenant ID, and Client
Secret authentication and want to migrate mailbox permissions, a certificate upload is required
as
part of your Azure App Registration setup.
Steps to Set It Up
If You're Using Modern Authentication
No certificate upload is needed. When Modern Authentication is used, mailbox permissions are
migrated automatically - no extra configuration required.
| Authentication Method | Certificate Required? |
| Client ID + Tenant ID + Client Secret | Yes |
| Modern Authentication | No |
Move specific SharePoint sites without touching the rest of your environment. This works well when only certain sites need to move right now. Instead of migrating everything at once, teams can target exactly what's needed. The associated content, libraries, and pages tied to that site move together. This keeps the process focused, reducing both migration time and unnecessary risk.
Handling one site at a time becomes unmanageable once numbers start growing. This feature lets multiple sites move together in a single coordinated batch. Instead of repeating the same steps site after site, everything runs together. Administrators save hours that would otherwise go into manual repetition and oversight. Larger organizations especially benefit when dozens of sites need to be migrated.
![]()
Every organization structures SharePoint differently, and destinations rarely mirror the source exactly. Mapping lets teams define where each source folder should land at the destination. This avoids a messy dump of files that no longer make sense together. Instead of manually moving things later, the structure gets defined before migration starts. The result is a destination that reflects real planning, not random placement.
Not everything sitting in SharePoint needs to move to the new environment. This feature allows specific sites, libraries, or folders to be chosen individually. Outdated files, unused libraries, or irrelevant data can simply be left behind. Teams get to decide exactly what qualifies for migration and what doesn't. This keeps the new environment relevant, organized, and free from old clutter.
Folder hierarchies often took years of decisions, corrections, and organizational effort to build. Losing that structure during migration means employees must relearn where everything lives. This feature keeps folders and files arranged exactly the way they originally were. Nothing gets flattened, renamed, or scattered during the transfer to the destination. People can log in afterward and find things exactly where they expect them.
Migrations rarely happen in one sitting, especially with large or active environments. This feature detects and moves only data that's new or recently changed. There's no need to repeat an entire migration just to catch updates. This saves time, reduces resource strain, & avoids duplicate content at the destination. It's especially useful for phased migrations that stretch across several days or weeks.
Sometimes only certain types of data are relevant for a given migration. Filters let administrators narrow results using criteria like date, size, or file type. This means outdated files or oversized items can be excluded from the start. Instead of migrating everything and cleaning up later, filtering happens upfront instead. This gives administrators tighter control over exactly what moves and what stays.
Access rules matter just as much as the files and folders themselves. This feature carries supported permissions along with the content during migration. Without this, administrators would need to manually reassign access after every transfer. That manual process is slow, error-prone, & risky for sensitive company data. Migrating permissions alongside content keeps access control consistent from day one onward.
Moving content from SharePoint to OneDrive doesn't have to mean manual copying & lost folder structure. This migration moves document libraries directly into OneDrive while keeping everything organized. Whether shifting personal workspaces or restructuring how teams store data, the process stays straightforward, accurate, & free from the guesswork of doing it by hand.
Once a migration runs, administrators need clarity on what actually happened. Reports outline which items completed successfully, were skipped, or failed outright. This removes the guesswork of manually checking each site or folder afterward. Failed items can be identified quickly and addressed without delaying the entire project. Clear reporting gives administrators confidence and accountability throughout the migration process.
Migrations don't always run smoothly, & problems are easier to fix early than after they pile up. This feature keeps an eye on the connection between source & destination throughout the transfer. Administrators can spot interruptions or failed connections as they happen instead of discovering them later. Catching issues in real time means less troubleshooting & once the migration is already underway.
Where data physically moves through matters, especially for companies bound by compliance or data residency rules. This feature lets administrators pick the data center region used during migration instead of relying on a default location. Choosing a nearby or compliant region can also improve transfer speed and reliability. It gives teams control over both performance and where their organization's data is allowed to travel.
Connect Source SharePoint
Enter the required source SharePoint details and authenticate.
Connect Destination SharePoint
Add the destination SharePoint environment.
Select SharePoint Data
Choose sites, libraries, folders, lists, or other supported content.
Start Migration
Run the migration and monitor the progress through the dashboard.
| Manual SharePoint Migration | Cigati SharePoint Migration Tool |
| Time-consuming | Faster bulk processing |
| Manual file handling | Automated migration |
| Difficult for large datasets | Designed for larger migrations |
| Limited processing tracking | Migration dashboard |
| Repetitive work | Selective and bulk migration |
During SharePoint migrations or regular usage, duplicate files and documents can build up across sites, libraries, and folders - leading to wasted storage and confusion over which version is the correct one. The Deduplication Suite scans your SharePoint content and automatically identifies and removes these duplicates, keeping your document libraries clean and organized.
What it offers:
Mailboxes, Teams, SharePoint, OneDrive, and deduplication? Try the Cigati Microsoft 365 Tenant to Tenant Migration Tool for an all-in-one solution.
Technical Specification
| Software Name: | Cigati SharePoint Migration Tool |
| Version Support (for Windows) | Windows 11, 10, 8.1, 8, 7, Vista, and XP (32-bit & 64-bit) |
| Software Size: | 304 MB |
| Minimum RAM: | 8 GB RAM (16 GB Recommended) |
| Version: | 26.09 |
| License: | S/A/T/E |
| Download Link: | Download for Win |
Processor:
Intel® Core™ i5 or higher (3.0 GHz or above recommended)
Hard Disk:
Minimum 500 MB for installation. Additional free space depends on data size (recommended: 2× input file size)
Memory:
8 GB RAM (16 GB recommended for large files)
Operating System:
Windows 11, 10, 8.1, 8, and 7
FAQ:
Yes, it can save PST files to SAN & NAS storage locations.
FAQ
You can migrate sites, document libraries, folders, files, lists, & associated content. It also supports permissions and metadata moving along with the data, keeping context intact at the destination.
Migration time depends on factors like data volume, number of sites, file sizes, & network speed. Small migrations may finish within hours, while larger, more complex environments can take longer to complete.
Yes, this SharePoint Data Migration Tool offers a free trial so users can test the migration process. It lets users migrate files less than 20 MB.
Client Reviews
Customers appreciate the structured approach and smooth SharePoint migration process. Many users find the software helpful for transferring large volumes of sites and libraries while maintaining folder hierarchy and permissions. Our technical support team assists customers throughout the migration process whenever needed. Users also value the reliable migration results and flexible options available for managing SharePoint data. These experiences reflect our focus on making SharePoint migration easier for individuals & businesses.