Destinations

Nextcloud Team Folder

A folder shared by a group of people, who all get the same permissions on it. The usual home for a SharePoint or Teams library, and for a file share.

Nextcloud User

One person's own files. The usual home for a OneDrive, and for anything that belongs to a single user.

Migrate into a Team Folder

For Destination Type Nextcloud Team Folder:

Nextcloud Team Folder is the name of one Team Folder, without slashes. A Team Folder that does not exist yet is created when the job runs.
Destination Folder is an optional path inside it, for example Archive/2026. Leave it blank to migrate into the top of the Team Folder. Every folder in the path is created if it is not there yet.

Pick the Team Folder and folder from a list

Instead of typing, use the buttons at the end of the fields:

Select team folder… lists the Team Folders on this Nextcloud. Search to narrow the list, click one and Select — or double-click it.
Select folder… opens the Team Folder named in Nextcloud Team Folder and lists the folders inside it. Click a folder to open it, the path above the list to go back up, and Select to put the folder that is open in Destination Folder. It needs the Team Folder named first.
New team folder and New folder create one on the spot and pick it: type its name and Create. A new folder goes inside the folder that is open. A new Team Folder starts with no members — give it its members and their permissions under Administration settings → Team folders.

Only names are listed — never files. A Team Folder or folder that is not there yet can also just be typed in the field: it is created when the job runs. The lists are read by Nextcloud itself, not by the SMART Migration server. The source of a file share job has no such button: a browser cannot read a folder path from the computer it runs on, and the path has to be one the SMART Migration server can reach.

Team Folders need Nextcloud's Team folders app. Who can open a Team Folder, and with which permissions, is set in Nextcloud — under Administration settings → Team folders — not in the job: SharePoint permissions are not migrated. Decide the members before users start working in the new folders.

One library, one Team Folder — or several in one

Each document library can get a Team Folder of its own: best when the libraries belong to different teams who should not see each other's files. Or several libraries can share one Team Folder, each job writing into its own Destination Folder — best when they belong to one team with one set of members.

An import scan can lay out either for you; see Naming and placing scanned jobs

Migrate into a user's files

For Destination Type Nextcloud User:

Destination User is the Nextcloud user whose personal files receive the content. Search by full name, user name or e-mail address. A user who does not exist yet can be typed in as a user name: the job can still be saved, but the user must exist before the job runs.
Destination Folder is an optional path under that user's files, for example Documents/Archive. Leave it blank to migrate into the top of their files. Every folder in the path is created if it is not there yet.
The files are written as that user. A Nextcloud administrator cannot write into another user's files, so when a Migration or Test Migration starts, the app makes an app password for the user, for that run alone, and gives it to the SMART Migration server — encrypted with a key only that server holds, so it never travels in clear text. It shows in the user's Security settings as SMART Migration run and the run's number, and the app revokes it when the run is over. How it is protected: The destination user's app password

What the run's app password cannot reach

It is made without the user's own login password. External storage the user signs in to with their own credentials, and files encrypted with the user's own keys, are out of its reach; server-side encryption with the master key is not a problem. Revoking it in the user's Security settings stops the run from writing.

MetaVox columns live on Team Folders, so a job writing into a user's files has no metadata mapping.

Rules for folder names

A Destination Folder is written with / between folders. The app refuses a path that Nextcloud could not store:

an empty folder name, such as a doubled //, and folders named . or ..,
a folder name that starts with a dot, or contains a backslash or control characters,
a folder name longer than 250 characters,
a folder name that ends with .part or .filepart, which Nextcloud reserves.

More settings on the Destination step

Rules for adding and overwriting files (Advanced Settings) — what happens to a file that is already there. See Rules for adding and overwriting files
Metadata Mapping — on the Metadata step, in Advanced Settings; see Metadata, MetaVox and SharePoint views
Include empty folders — on the Source step; see Choose which files a job takes

See also