Titles and descriptions of the imported jobs
Section titled “Titles and descriptions of the imported jobs”A template is free text with placeholders in braces. Any text around the placeholders is kept, and a line whose placeholders all come out empty is left out. Pick one of the presets, or write your own; the Example under each template shows what it makes of a sample library or user.
- Right-click a template to insert a placeholder where the cursor is. Shift+right-click opens the browser's own menu.
- A placeholder must be spelled exactly as listed, in one pair of braces. A brace left open, or a name the scan does not fill, is marked, and the Import job does not validate until it is corrected.
Placeholders for SharePoint libraries
Section titled “Placeholders for SharePoint libraries”The SharePoint Site, Site and Sub Sites and Tenant scans fill these:
| Placeholder | What it holds |
|---|---|
{siteTitle} | The site's title, as users see it |
{siteName} | The site's internal name, from its URL |
{libraryTitle} | The library's title, as users see it |
{libraryName} | The library's internal name, from its URL |
{guid} | The library's ID |
{itemCount} | How many items the library holds |
{lastModified} | When any item in it was last changed |
| Template | Default | Presets |
|---|---|---|
| Job title | {siteName}/{libraryName} ({libraryTitle}) | Site and library titles, Library title, With item count |
| Description | Site, library, item count and last change, one per line | Item count and last change, Site and library titles, The description the scan sends |
Placeholders for OneDrive users
Section titled “Placeholders for OneDrive users”The OneDrive in Tenant scan fills these, from each user's Microsoft 365 profile:
| Placeholder | What it holds |
|---|---|
{displayName} | The user's full name |
{upn} | Their sign-in address |
{onedrivePrincipalName} | The principal name their OneDrive belongs to |
{jobTitle}, {department} | Their job title and department |
{businessPhone}, {mobilePhone} | Their phone numbers |
{accountEnabled} | Yes or No: whether their account is enabled |
{guid} | Their object ID |
The default title is {displayName} ({upn}), so every job says whose files it moves; the presets offer the sign-in address alone, name and department, or department then name.
Team Folders for scanned libraries
Section titled “Team Folders for scanned libraries”With Nextcloud Team Folder as the destination type on Destination defaults, the scan's libraries are spread over Team Folders in one of two layouts:
One Team Folder for each library
Every library becomes a Team Folder of its own, with its own members and permissions. Best when the libraries belong to different teams or departments, who should not see each other's files. Default name: {siteName} - {libraryTitle}
One Team Folder for each site, with a folder for each library
Every site becomes one Team Folder, and each of its libraries a folder inside it, so the site carries over as it is. Best when a site's libraries belong to one team that shares one set of members and permissions. Default names: {siteName} and {libraryTitle}
- Team folder name is one name, without folders inside it. Characters a folder name cannot hold —
/ \ : * ? " < > |— are replaced with a dash. A Team Folder that does not exist yet is created when the job runs. - Folder inside the Nextcloud Team Folder is optional with one Team Folder per library. A
/makes a folder inside a folder, such asMigrated/Archive. - A Destination Folder set on Destination defaults goes around it: the template's folder is created inside it.
User folders for scanned OneDrives
Section titled “User folders for scanned OneDrives”With Nextcloud User as the destination type, each OneDrive is copied into the personal files of one Nextcloud user. The app finds that user like this:
SMART Migration reports the OneDrive's sign-in address
For example anna@contoso.com.
The app looks for the Nextcloud user with that e-mail address
Exactly one user must have it: an address several Nextcloud users share finds none of them.
Then for a user whose user name is that address
When no user has the e-mail address, a user named anna@contoso.com is used.
The name, such as Anna Berg, is never used to find the user, because two people can have the same name. When no user is found, a Test Migration or Migration job is still created, but marked Not validated: create the user, or add the e-mail address to their Nextcloud account, then open the job and save it again. A Discovery job validates either way, because it writes nowhere.
The optional folder template places the files inside the user's files: none, a folder named OneDrive, or one named after the user.
A Team Folder per OneDrive, for users who have left
With Nextcloud Team Folder as the destination type, each user's OneDrive becomes a Team Folder of its own, named after the user. That suits users who have left or are no longer active: their files land where the Team Folder's members can go on working with them, rather than in a personal account nobody signs in to.
Library scans into one user's files
Section titled “Library scans into one user's files”A SharePoint scan with Nextcloud User as the destination puts every library into the files of the one Destination User set on Destination defaults, each in the folder its template names. A library has no user of its own.
See also