Before the first OneDrive job: the domain mapping
Section titled “Before the first OneDrive job: the domain mapping”A OneDrive job names its user by their UPN, such as sj@abc.com, but Microsoft 365 builds the address of that user's OneDrive from the tenant's own SharePoint domain, not from the e-mail domain in the UPN. The two often differ — after a company rename, a merger, or when a custom e-mail domain is in use.
Set the mapping once, on the Settings tab under Microsoft OneDrive for Business (M365) Discovery and Migration:
- Map From — the e-mail domain in your users' UPNs, for example abc.com.
- Map To — your SharePoint and OneDrive tenant name, as the hint under the field describes.
Check the Example the tab works out as you type against the address of a real OneDrive in your tenant before saving. Until the mapping is set, a OneDrive job does not validate — unless its UPN is on the tenant's onmicrosoft.com domain, which names the tenant itself. A UPN whose domain differs from Map From does not validate either.
One job per OneDrive, from one scan
Section titled “One job per OneDrive, from one scan”- On the Jobs tab, open New Job and pick Job Import.
- On Import from, choose OneDrive in Tenant, and enter the address of any site in the tenant as the Import SharePoint URL.
- Keep the mode on Discovery for a first look, and the destination type on Nextcloud User.
- Save it and set it to Ready. The SMART Migration server scans the tenant's users and the app creates one job per OneDrive, titled with the user's name and sign-in address.
The scan is described in Import jobs by scanning SharePoint or OneDrive
How each OneDrive finds its Nextcloud user
Section titled “How each OneDrive finds its Nextcloud user”By e-mail address
The app looks for the one Nextcloud user whose e-mail address is the OneDrive's sign-in address, for example anna@contoso.com.
By user name
When no user has that e-mail address, it looks for a user whose user name is that address.
Never by name
The display name, such as Anna Berg, is never used: two people can share a name. An e-mail address that several Nextcloud users have finds none of them.
A Test Migration or Migration job whose user is not found is still created, but marked Not validated, so it cannot run. 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 whether its user is found or not: it reads the OneDrive and writes nowhere. The user is looked up all the same, ready for the day the job is switched to a migration — and the job dialog checks the destination then.
Match the users before you migrate
Nextcloud accounts usually come from your identity provider, such as LDAP or Keycloak, with the same e-mail addresses as Microsoft 365. Make sure every user has an account before the migration wave: once the jobs are switched to a migration, the Readiness filter on the Jobs tab shows the OneDrive jobs that are not validated, which is where a missing user shows up.
Users who have left
Section titled “Users who have left”Choose Nextcloud Team Folder as the destination type instead, and each OneDrive becomes a Team Folder of its own, named after the user. That suits former employees and inactive accounts: 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. Import those users in an Import job of their own, from a CSV file or a second scan.
One OneDrive by hand
Section titled “One OneDrive by hand”A single OneDrive job is made with New Job: Source Type OneDrive, the user's UPN as Source UPN, and optionally a Source Folder inside the OneDrive, such as Documents/Archive. Resolves to shows the OneDrive address the job will read. On the Destination step, choose the Nextcloud user and, if wanted, a folder in their files.
See also