The four scans
Section titled “The four scans”| Import from | Import SharePoint URL | One job for |
|---|---|---|
| SharePoint Site | The address of the site itself, for example https://contoso.sharepoint.com/sites/Finance | Each document library of that site that holds items |
| SharePoint Site and Sub Sites | The address of the top site of the tree | Each document library of the site and of every sub site below it that holds items |
| SharePoint Tenant | The address of any site in the tenant — it only identifies the tenant | Each document library of every site in the tenant that holds items |
| OneDrive in Tenant | The address of any site in the tenant — it only identifies the tenant | Each user's OneDrive in the tenant |
The address is always a site, never a document library or a folder in one. For a tenant, the root site will do, for example https://contoso.sharepoint.com. Libraries that hold no items are skipped.
Run a scan
Section titled “Run a scan”- On the Jobs tab, open New Job and pick Job Import, and on Import from choose the scan and enter the Import SharePoint URL.
- Set the defaults the new jobs get — group, tags, status, schedule and notifications on Job defaults, mode on Action defaults, filters on Source defaults, and where they land on Destination defaults.
- Save the Import job and set it to Ready. The SMART Migration server claims it like any other job, scans, and sends what it found to the app, which creates the jobs.
The scan reads SharePoint with the server's own Microsoft 365 app registration, so that registration needs the permissions to list the tenant's sites, libraries and users. See How to create and configure the app registration
How long a tenant scan takes
Expect 30 to 50 sites a minute — about 30 to 40 minutes per 1,000 sites. While the scan runs, the Progress of its Run History row is updated with the number of sites scanned so far.
What each scanned job is given
Section titled “What each scanned job is given”| Scan | Source of each job | Title and description | Destination |
|---|---|---|---|
| SharePoint Site, Site and Sub Sites, Tenant | Source URL: the library's URL | Built from the site and the library by the title and description templates | A Team Folder and a folder in it named by their templates — or, for a Nextcloud User destination, the user set on Destination defaults |
| OneDrive in Tenant | Source UPN: the user's e-mail address | Built from the user's Microsoft 365 profile by the templates | The Nextcloud user with that e-mail address — or a Team Folder of their own, named by its template |
A site scan also reads each library's item count — SharePoint's own figure, of its files and folders together, not counted by SMART Migration. Each job keeps that count, and the Jobs tab shows it in its Items column until the job's first run: a quick view of how large each library is before its first Discovery. See Jobs and job modes
How the templates are written, and how the Team Folders are laid out, is described in Naming and placing scanned jobs
Good to know before you scan
Section titled “Good to know before you scan”- Each run creates new jobs. Running a scan again creates the jobs again, beside the ones it created last time. Give a scan no recurrence, and use the Duplicates filter to clear up after a second run.
- The source type is fixed by the scan: SharePoint Library for the site and tenant scans, OneDrive for the OneDrive scan. The destination type starts as the most likely one — Team Folder for libraries, Nextcloud User for OneDrives — and can be changed.
- Start small. A scan of one site is a quick way to see what the templates make of your names before you scan a whole tenant.
- Discover before you migrate. Leave the scanned jobs in Discovery mode first: the Power BI report then shows every library of the tenant side by side, and you switch the ones you want to Migration when the scope is decided.
See also