OneDrive to Nextcloud user

The OneDrive to Nextcloud user mapping defines which Nextcloud user account will receive the personal files from each Microsoft 365 OneDrive user during migration. Because OneDrive is tied to a single user identity in M365 while Nextcloud uses its own user directory, Content Governance must know exactly which source user maps to which destination user — and it must be able to authenticate as that Nextcloud user in order to upload files on their behalf with full version history and metadata preserved.

Each row in the grid represents one user-to-user mapping and consists of three columns:

• M365 user name (UPN) — the source OneDrive owner in the connected Microsoft 365 tenant.
• Nextcloud user name — the destination Nextcloud account that will receive the migrated files.
• Nextcloud App Password — the application password used by Content Governance to authenticate against Nextcloud as that user.

*Only the raw identifier is used at migration time — the M365 user name column needs just the
UPN (e.g. peter@mytenant.com) and the Nextcloud column needs just the Nextcloud login name
(e.g. christian). The friendly “Display Name <identifier>” format shown after import is generated for readability only; when editing rows manually or pasting from Excel it is perfectly fine to enter the bare UPN and login name on their own.

Populating the grid

The grid is normally built by using the two import buttons in sequence:

1. Click Import M365 OneDrive users. Content Governance connects to the configured Microsoft 365 tenant and adds one row for every OneDrive user found. Users whose UPN is already present in the grid are skipped, so the button is safe to re-run after tenant changes (for example when new users have been onboarded).
2. Click Import Nextcloud users. Content Governance fetches all users from the connected Nextcloud instance and, for each existing row, matches the Nextcloud user to the M365 user by e-mail address. When a match is found the Nextcloud user column is filled in automatically.
3. Add the Nextcloud App Password for each row manually. App passwords cannot be retrieved through the Nextcloud API and must be generated per user inside Nextcloud. See Generating Nextcloud app passwords for the step-by-step procedure.

Bulk editing via Excel

*For tenants with many users it is often faster to maintain the mapping in Excel. Use Export to Excel to get the current grid, edit it there — including pasting app passwords from a password manager — then select the three columns in Excel and click Paste from clipboard/Excel to load the updated mapping back into the grid. This is also the recommended way to hand the app-password collection task to a Nextcloud administrator without needing to give access to Content Governance.

Validating the mapping

Clicking Validate selected mapping runs two checks against each selected row:

• The M365 OneDrive user exists and the OneDrive site is reachable in the source tenant.
• The Nextcloud user can actually be logged in with the supplied app password (an authenticated WebDAV call is performed against Nextcloud).

A green indicator on the row means both checks passed; a red indicator means the row will fail at migration time and must be corrected first.

!Running a migration with an invalid, revoked or expired app password will cause every file transfer for that user to fail. Always validate the mapping before starting the job, and re-validate after any Nextcloud password policy or user provisioning change.