Jobs and job modes

One job per source

Create one job for each document library, each OneDrive and each file share. The Jobs, Run History and File Issues tabs file their rows by source, the Power BI report breaks the migration down the same way, and a run that fails affects only that one source.

For a whole tenant, a site with all its libraries, every OneDrive or a list in a spreadsheet, an Import job creates the jobs for you. See Import jobs

Not sure where to begin — one job, or a Job Import? See Which jobs to create first

A job is the plan; each time SMART Migration carries it out, it leaves a run on the Run History tab — the record of what that run found or moved. See Run History

The four job modes

Mode	What the job does	Files written
Discovery	Scans the source and reports which files are there, without moving anything. A complete result in its own right, not an unfinished migration.	None. The run's report and its data for the Power BI report.
Test Migration	A trial run that shows a migration's outcome without moving anything: which files it would add as new and which it would overwrite under the job's rule, that the source and destination can be reached, and that the metadata maps onto the destination. Its files show in the Power BI report as `Test Migration`.	None
Migration	Copies the files into a Nextcloud Team Folder or a user's personal files.	The migrated files, the report and the data for the Power BI report.
Job Import	Creates jobs rather than moving files: one per line of a CSV file, or one per library or OneDrive a SharePoint scan finds.	New jobs on the Jobs tab

A job keeps its mode until you change it, so the usual path is to discover first and switch the same job to Migration when the scope is decided — with a Test Migration first when you want to see which files it would add and which it would overwrite. Everything else in the job stays as it was. See Discovery

To see what is in a source, use Discovery; to see files arrive, use Migration. All three modes feed the Power BI report, where each file's File status is Discovery Report, Test Migration or Migration after the last run that handled it — see Follow every file from discovery to migration. What a Test Migration is for, and the rules it tests: Advanced options for discovery and migration

Create a job

On the Jobs tab, open New Job and pick the mode the job starts in: Discovery, Test Migration or Migration. Job Import, in the same menu, creates an Import job instead.
Fill in the job dialog: a title, the group it belongs to, the mode, the source and — for a migration — the destination. See The job dialog
Save. A job whose definition is complete is Validated.
Set it to Ready, in the dialog or in the Status column. The SMART Migration server claims it once its scheduled date has come.

A fresh install has no jobs: the Jobs tab then suggests a first Discovery job, to see what is in a library, OneDrive or file share before anything moves.

Validated or not validated

The app checks every job's definition as it is edited: a required field that is empty, or a value that does not suit its field — a site address where a library is needed, a UNC path that is not one — leaves the job Not validated. The fields in question are marked, and so is the wizard step they are on.

A job that is not validated can still be saved, so it can be finished later. It is saved with the status Hold, whatever the form shows; if Ready was picked, a warning says it cannot be Ready.
It cannot be set to Ready, so the server never claims a job that would fail at once.
The footer of the job dialog says Validated or Not validated — this job cannot run, and the Readiness filter on the Jobs tab shows the jobs of each kind.
The filter under the Status column offers Hold + Validated and Hold + Not validated under Hold: the jobs on hold that are ready to be set to Ready, or the ones still to be finished.

The Jobs table

The Jobs tab shows one row per job, with these columns: Title, Source, Destination, Mode, Status, Result, Group, Tags, Modified and Archived. The scheduled date shows when you rest the pointer on a title. Result comes from the job's latest run of the mode it has now: a job changed from Discovery to Migration shows no result until its first Migration run ends, and shows its Discovery result again when it is changed back. Beside it, a job that has run shows the runs mark and how many runs it has — red when its latest run of its mode logged an error, yellow for a warning, green when it logged neither. Rest the pointer on it for the runs card: how many runs of each mode, how they ended, the time they took, what the latest Discovery found and what the migrations moved, and the latest ten runs one per line, with their status, result, start, duration, files, versions, volume and version volume. A figure of none, or one not reported yet, reads as a dash rather than 0. A run's mode is its own: a job set to Discovery today lists its earlier Migration run as one. A click on a run's line shows that run, and the mark pins the card: Open on Run History tab shows all the job's runs there and Go to latest run the latest — each run narrowed to the job's runs, under Showing runs of job …, with every other filter cleared, Latest run per job too, so all its runs are listed and the run is the current row. A job that has not run yet shows nothing there. A job a SharePoint scan imported shows, in the Items column on a teal wash after Destination, how many items its library holds, until the job's first run — SharePoint's own count, passed on by the scan rather than counted by SMART Migration, and of files and folders together, so a high count does not necessarily mean many files. Rest the pointer on the column's title for a card that explains it, or on a row's count for that job's card — the count, how to read it, the job's mode, status and library — and click the count to pin the card, with Open, Open library, Run now and Hide Items column; the column is there only while some job not archived still has a count to show, and it sorts like the others. Hide Items column in the ⋯ menu at the far right of the tab bar takes it out of the table, and Show Items column puts it back; this browser remembers the choice. Source and Destination are as narrow as their titles: rest the pointer on a path to read it whole. Each source starts with its kind's mark — the SharePoint or OneDrive logo, or the network folder of a file share — and a migration's destination with the mark of a team folder or a user. The filter under Source picks a source type — SharePoint, OneDrive, file share or file list — and the filter under Destination a destination type, such as a Nextcloud team folder or a user's files; a Job Import has neither, and only a migration has a destination. When the window is too narrow for every column, the table scrolls sideways: the row menu, the tick boxes and Title, with the text filter under it, stay in place at the start, and the Pin column at the end, so you always know which job a row is. While the table scrolls sideways, the lines after Title and before Pin turn blue: the columns between them are the ones that scroll, and the scroll bar under the table spans just those columns.

Status, Group, Tags and Archived can be changed right in the table — a grey pencil beside a column's title marks them; on a row that is part of a selection, the change reaches every selected row at once, and the Actions menu beside New Job acts on every ticked row. Everything else is edited in the job dialog: double-click the row, or choose Details in its menu. See Change many jobs at once

Copy, link and delete a job

Copy makes a new job with the same settings, titled with "(copy)" after the original's title, in the same group and on Hold.
Copy link gives a link that goes straight to the job's row in the table.
Copy URL and Open SharePoint location head the row menu when you right-click the job's Source or Destination cell: the first copies the whole address — Copy UNC path for a file share, Copy UPN for a OneDrive's owner — and the second opens the library in SharePoint in a new browser tab. A file share's location cannot be opened from a web page; paste its path into File Explorer.
Delete removes the job. A job that is Running or Canceling, or Ready and not disabled, cannot be deleted, because SMART Migration has it queued or is working on it: set it to Hold or disable it first.

When the jobs have Run History rows, the delete confirmation offers to delete them too, ticked to begin with and counting them. Ticked, every run of the deleted jobs goes too, except runs SMART Migration is still reporting on, and their data is taken out of the Business Intelligence data — the Dashboard shows when that is done. Untick it to keep the runs: every run keeps its own record, including a snapshot of how the job was configured when it ran. See Run History

Pin jobs to the top

A pinned job moves to the top of the table: it is listed apart, under a Pinned band above the tree or the list, and no longer in its group below — whatever the sort, with a line in orange down its start edge. They stay in view under the column titles while the rest scrolls under them, as long as they take at most three quarters of the table's height; more than that, and they scroll with the rest. The Pin column at the far right shows a solid pin on a pinned row and an outline on the rest; click it to pin or unpin that row alone. An unpinned row leaves the band and the table stays where it is; the toast that says so takes you to the row. To pin or unpin every ticked row, use Change selected jobs … in the Actions menu.

The job dialog has Pin and Unpin too, beside Disable job on the Job heading's line; for several ticked jobs, Change selected jobs … in the Actions menu pins and unpins as well.
Pinning changes nothing else: the job keeps its place in the tree, its status and everything SMART Migration reads.
Pins are your own: each administrator pins for themselves, and no one else sees your pins.

My note on a job

My note is a few lines kept with one job: something important about it that is not part of the job's description — a decision, a warning, why it is Deferred. Write it on the pinned summary card: click the title, write in My note about this Job beside the Job section; it is saved when the card closes. The job dialog has the same field under Job Description, saved with the job. It is your own: other administrators do not see it, and each can write their own. SMART Migration never reads it. The text filter under the Title column reads notes too, and a job with a note shows a small orange triangle in the top-right corner of its title; a job with a description shows a blue one in the bottom-right corner. In the job dialog, the same small corner sits beside Job Description and My note about this Job, to say which triangle each one sets.

For how pins, My note, groups and tags work together, and how to search notes, see Organise the jobs of a project

Archive jobs

Archiving puts a job away out of everyday work without deleting anything. The Archived box at the far right of each row archives the job, or takes it out of the archive; with several rows ticked, the click applies to all of them. A confirmation says what it does first; its Do not show this again skips it for you, except to ask about the jobs' runs.

An archived job is left out of the Jobs tab — the table, its counts and its filters — and of the Dashboard's job tiles. The count in the tab bar says how many are left out — 9,051/9,051 · 7 archived. The Archived column is titled Arch.; the box under its title filters by it, in three states: empty while the archived jobs are hidden (the everyday view), a bar across it while every job shows, ticked while only the archived ones show — click it to move on to the next.
Nothing else changes: the job keeps its status and settings, and a Ready job is still claimed by SMART Migration. Set it to Hold or disable it first if it should not run.
When the jobs have Run History rows, the confirmation offers to archive them with the jobs, ticked to begin with. Their data stays in the Business Intelligence report: archiving changes nothing there.
Jobs and runs are archived independently: a job can stay in everyday work while its old runs are archived on the Run History tab — the way to keep a job that runs every day from filling the tab — and an archived job's runs can stay out of the archive.

Archive a wave or a piece of work once it is signed off, and tag the jobs that belong together so they can be found again across the waves. See Monitor the migration from one place

See also