Monitor the migration from one place

Watch everything from the Dashboard

The Dashboard follows SMART Migration on its own, with nothing to refresh. From top to bottom it answers five questions:

Section	The question it answers
Job and file figures	How many jobs are where, and what the runs have found and moved.
Running jobs	What SMART Migration is working on right now, and how far each run has come.
Notifications sent	Who was told what, and when, about which run.
Log	What happened to the jobs and runs, who did it, and what changed.
Business Intelligence	Whether the Power BI report is up to date with the runs.

The Notifications sent table

Notifications sent lists each job once, by the latest notification the app sent to the users and groups in its Notify to — the latest event of its latest run — the latest first: when it was sent, the job's title, the event — started, finished, finished with warnings or errors, canceled, or a run's first error or warning — the message it carried, led by the run's figures as the run stands now (that the job has started, for a start; the result and how long the run took, then files, versions and volume, once it has ended; then its errors, warnings and file issues), and the users it went to. A notification sent before the app recorded its users names its users and groups and how many users that was instead.

Filter the table by Job title, Event, Message and Sent to: each box sits under the title of its column. Sent to takes several users and shows the notifications sent to any of them.
Sort it by clicking a column's title — Sent, Job title, Event, Message or Dismissed — and again to reverse it; Ctrl-click adds a column to the sort, as on the Jobs tab. Event sorts in the order a run's events happen. Pinned notifications stay on top whatever the sort, and the table keeps your sort for the next visit.
Rest the pointer on a title to see the run at a glance, or click it to pin its summary card, with its buttons.
Rest the pointer on an event for the job's card: every notification of its Latest run, the latest first — a small count beside the event says how many there are — and under it each earlier run that sent notifications, by when it started. Click the row — anywhere but its title, its tick box and its marks — or the card itself to pin the card under the event: it offers the buttons of the run's card on its title — Details, Open run on Run History tab, Goto Job, Copy link, and Cancel job while the run is under way. Every notification stays recorded; the table only shows each job's latest.
Double-click a row, or click Job details in its row menu, to read the run's details here on the Dashboard.
The row menu opens the run on the Run History tab or the job on the Jobs tab.
The pin at the right of a row keeps that job's row at the top of the table, under a Pinned band, in view while the rest scrolls, whatever arrives after it — the pin moves with the job to its next notification. Click it again to unpin it; a message then takes you to where it went. Pins are your own: no other administrator sees them.
Dismiss a job's row once you have read it — every notification of its run goes with it, and a new notification for the job brings the row back: its Dismissed box, Dismiss selected notifications for the ticked ones, or the row menu. The filter box under Dismissed shows them again, and Delete dismissed notifications, on the line of the heading, deletes them — only the record of what was sent; their runs stay in Run History.
The count beside the heading shows how many jobs' rows the filters let through of all of them, and how many are dismissed.
The next notifications load by themselves as you scroll to the end of the table, the last row saying so while they come.

A notification whose run is deleted leaves the table, as it leaves the bell.

The Log: who did what, and what changed

The Log under Notifications sent lists what happened, the latest first: when, the event, the job's or run's title, what it says, and who did it — the administrator signed in, the account SMART Migration signs in with for what it reports, or Server for the server's own background jobs.

Event	What the row says
Jobs imported	How many jobs an import wrote, into which group, and how many did not validate — one row for each import, counted up as SMART Migration sends its rows. Its card's Show imported jobs opens the Jobs tab on that group.
Job created	A job made in the job dialog, or a copy of another.
Job changed	Each field a save changed, from what to what — `Status: Finished → Hold`, `Mode: Discovery → Migration`. A change of mode comes first and is flagged, see below.
Jobs changed	A change made to many jobs at once, from the Actions menu or Change selected jobs …: what was set, how many jobs, and the first of their titles.
Jobs deleted, Runs deleted	How many went and the first of their titles; runs a job's retention schedule deleted say so.
Run started, Run finished, Cancel asked for	A run's mode, how it ended — Finished or Canceled — its result and its files; an import's run, how many jobs it imported and into which group. A run has one row: Run started while it runs, replaced by Run finished when it is over.
Group changed, Tag changed, Setting changed	A group created, renamed, merged or deleted; a tag renamed or deleted; who can use the app, or the Log retention, changed.

A change of mode stands out. A job moved from Discovery to Migration — or from any mode to another — does other work from then on, so its row is drawn in amber with a thick amber edge, and its details open with Mode changed and the two modes as pills, the old before the new. A change of many jobs' mode shows the new one. Its card leads with the same note.
Rest the pointer on a row's event, title or details for its card: what happened, in full, laid out for its kind of row — each field a save changed, before and after; what a change of many jobs set, what it did besides (jobs put on Hold, or Finished again) and every job it reached; every job or run a delete took; what an import wrote and where; how a run ended; a group, tag or setting before and after. A long list scrolls inside the card. Click the row to pin the card, with its buttons below the list: Goto Job, Open run on Run History tab, Copy details and Delete …, as fit the row.
Beside each event, the icons of the job it is about: the run's icon for a run, the job's mode — Discovery, Test Migration, Migration, Import — and its source in its own colour, as the Jobs table draws it: SharePoint, OneDrive, a file share or a file list; an import, the source of the jobs it writes.
Filter it by Event, by text in the Title, by text in the Details — the words the column shows, in your language, and every job or run a row names, not only the first ones the column has room for — and by By, which takes several people. Sort it by clicking When, Event, Title or By; the table keeps your sort for the next visit.
Tick rows and choose Delete … in the Actions menu above the tick boxes, or Delete … in a row's menu, to take rows out of the Log. What they describe stays as it is, and the Log records the delete itself, with who did it.
Export to CSV saves every row the filters let through, in the table's order, to a CSV file — the time, the event, the title, the details, who did it, and the job's and run's ids.
The row menu opens the row's job on the Jobs tab, or its run on the Run History tab.
Rows are kept for a month unless an administrator chooses otherwise under Log retention on the Settings tab: a week, a month, three or six months, a year, or for ever. Every hour, the server deletes the rows older than that.

Look at the runs that have finished

The Run History tab lists every run that has finished, with its result and the message it ended with. Set its Result filter to Error, then to Warning: those are the runs to read first. A run with issues shows the issues mark and their number beside its Result; click it to list each file on the File Issues tab.

Action	Where the run goes	Its data in the BI report
Archive	Out of the Run History tab until its Archived filter shows it	Kept
Delete	Gone, after SMART Migration has purged its data	Purged

Organise the work with groups, tags and Archived

Groups, tags and the Archived box together keep thousands of jobs and runs readable: each answers a different question.

Group: which wave

One per job — Pilot, Wave 1, Finance. The trees on the Jobs, Run History and File Issues tabs are organised by it, and it goes into the Power BI report.

Tags: which piece of work

Any number per job, across the groups — an owner, a department, a site, or the state of the work, such as Needs review, Waiting for owner or Signed off.

Archived: done with

Puts finished work away out of everyday views without deleting anything. Archived jobs are still claimed when Ready, and archived runs stay in the report.

Used together they follow a logical piece of work from start to finish:

Group the jobs by wave
File each job in the wave it migrates in, with Manage groups or the Group column.
Tag the pieces of work that cut across the waves
Give the jobs of one department, one owner or one cut-over weekend the same tag, so Tags (all) finds them on every tab.
Follow the work by tag
Filter the Jobs and Run History tables by the tag to see the jobs, their runs and how they ended, whichever wave they are in. Tag a job Needs review while its results are being checked, and remove the tag once they are signed off.
Archive what is finished
When a wave or a piece of work is signed off, archive its jobs and their runs: the everyday views keep to the work still under way, and Show archived brings them back whenever the history is needed.

A daily check

A few minutes on the Dashboard each day keep a migration under control:

Is the server in touch? Live at the top right means SMART Migration is calling in; the Dashboard says so when it is not.
What is running? Running jobs, with their progress.
Who was told what? Notifications sent: every start, finish, first error and first warning sent, and to whom.
What has finished since yesterday? Run History, filtered to Error and Warning first. Read each one, fix what needs fixing, then archive it.
Is the report current? The mark on the Power BI heading turns red while deleted runs are still to be purged; refresh SMART BI.pbix once it has cleared.

See also