Import jobs

Where an Import job finds its jobs

The Import from step chooses how wide the import looks for job definitions:

Import from	Creates one job for	Run by
SharePoint Tenant	every document library, in every site of the tenant, that holds items	The SMART Migration server
OneDrive in Tenant	every user's OneDrive in the tenant	The SMART Migration server
SharePoint Site	every document library of one site that holds items	The SMART Migration server
SharePoint Site and Sub Sites	every document library of a site and every sub site below it that holds items	The SMART Migration server
CSV in Nextcloud Files	every line of a CSV file in Nextcloud Files	The job dialog, at once

The four scans and the CSV file are described in:

Create an Import job

On the Jobs tab, open New Job and pick Job Import. The job dialog opens with the Import job's steps.
Job — a title for the Import job itself, and under Notifications what its own runs notify of.
Import from — the scan or the CSV file, and its address.
Job defaults — the group, tags, status, schedule, Notifications boxes and Notify to the new jobs start with. See Notifications when a job runs
Action defaults, Source defaults, Destination defaults and Metadata defaults — the mode, filters, destination and metadata settings every new job is given.
Run it: a CSV import with Save and import CSV now in the dialog; a scan by setting the Import job to Ready, so the SMART Migration server claims and runs it.

The defaults steps are marked in teal in the dialog: their settings are handed to the jobs the import creates, and do not describe the Import job itself. The Import job has to validate first, because the new jobs are built from it.

Job defaults: group, tags, status, schedule and notifications of the new jobs

Field	What the new jobs get
Import Group	Every import files its jobs in a new group: the group chosen here followed by the date and time the import started, such as Wave 1 2027-01-20 14:05 — or Imported 2027-01-20 14:05 when no group is chosen.
Import Tags	The tags every new job is given.
Imported Job Status	Hold, Ready or Deferred. A new job that does not validate starts on Hold instead of Ready.
Disable job	When on, every new job starts disabled: it keeps its status, but SMART Migration never picks it up until it is enabled.
Scheduled Date	When the new jobs are scheduled to start. Empty: the moment of the import. Shown with Advanced Settings on, as are the three below.
Priority	High, Medium or Low for every new job. The Import job's own priority, on its Job step, decides only when the Import job itself runs.
Recurrence	None, Daily, Weekly or Monthly for every new job.
Retention schedule	How long the new jobs' runs are kept before they are deleted from Run History, as on any job. An Import job has no retention schedule of its own.
Notifications	Job start, Job finish, First warning and First error for every new job — all ticked on a new Import job — shown with Advanced Settings on. The Import job's own boxes are in its Job step.
Notify to	The users and groups every new job notifies — you, on a new Import job. Shown with Advanced Settings on.

Check the batch, then merge it

Leave the Imported Job Status on Hold for a first import. The new jobs wait in their own group: check them — the Readiness filter shows any that did not validate — then merge the group into the wave they belong to with Manage groups, and release the wave with Set all to Ready.

What every new job is given

From the defaults steps: the mode, the source type, Include Subfolders, the version history settings, the date, size and file type filters, the .url link option, the destination type, user and folder, empty folders, the rules for adding and overwriting files and the metadata settings.
From the line or the scan: its title and description, and its source — a library URL, a UNC path or a OneDrive user — and, from a CSV line, its destination.
From Job defaults: the group, tags, status, scheduled date — the moment of the import when it is left empty — priority, recurrence, retention schedule and notifications.

Every default is given to every new job, whatever its mode.

Every line or library makes a new job, whatever jobs exist already: an import never changes or replaces an existing job. Importing the same file or tenant twice makes the jobs twice — the Duplicates filter on the Jobs tab finds them, see Change many jobs at once

Discover first, migrate later: set up every mode

The mode on Action defaults is only the mode the new jobs start in. A Discovery job reads its source and writes nowhere, so while Discovery is picked the dialog hides the Destination defaults step, the Metadata defaults step and the destination templates. They are hidden, not gone: switching the mode never clears a setting, and every new job is given them all. Set them up before the import runs, and a job imported for discovery needs only its mode switched to migrate.

Pick Migration on Action defaults
On Action defaults, pick Migration. The Destination defaults step appears, and for a SharePoint source going to a team folder the Metadata defaults step as well.
Set the destination
On Destination defaults, choose the destination type, where the jobs land, and the rules for adding and overwriting files.
Set the destination templates, or the CSV file's Destination
For a scan of SharePoint or OneDrive: on Import from, turn on Advanced Settings and set the destination templates — how the site, library and OneDrive names the scan finds fill in each job's team folder, user and folder in Nextcloud. They show only while a migration mode is picked. For a CSV file: fill in each line's Destination column, written as the destination type on Destination defaults expects it.
Set the metadata
On Metadata defaults, when the step is there, set how the SharePoint columns are carried into MetaVox.
Pick the starting mode and save
Back on Action defaults, pick Discovery again — or whichever mode the jobs should start in — and save.

When the discovery is done and the scope decided, switch the jobs you want to Migration, or to Test Migration first. They already hold their destination, templates and metadata settings, so they are ready to run.

After the import

The import is a run. It is recorded in Run History like any other job's run, with its counts, its messages and its log.
Show imported jobs, in the Import job's row menu, shows the jobs it created on the Jobs tab. Each run of the import files them under a group of its own, named for the Import job's group and the time the run started, and the tab is filtered to all of those groups. On the Run History tab, an import run's row menu offers the same for that one run.
Each new job validates on its own. A job whose source does not suit its type is created Not validated, and so is a Test Migration or Migration job whose destination does not suit its type or whose Nextcloud user cannot be found. A Discovery job writes nowhere, so its destination does not count. A job that is not validated cannot be set to Ready until it is corrected.

See also