The dashboard page is used to monitor and control migration processes.

Processes

All content sets are listed here in order of weight. For each content set listed, you will see the following items:

Clear/Import
These toggles enable processes to run - see the glossary for details.
Content Set
The name of the content set. This name can be used to specify a particular content set in a drush command. It is linked to the edit page for the content set.
Total rows
A count of the total rows in the source view.
Imported
A count of the Drupal objects successfully created for this content set. If any of these objects generated informational messages (conditions interesting enough to report, but not severe enough to prevent successful import) there will be a link to the messages here.
Unimported
A count of source rows which have not yet been migrated, or which failed to migrate successfully. If there were any failures, there will be links to the messages here.
Last imported
The date and time that the last import or scan completed.

Any content set currently being processed is highlighted.

Execute

Drush is the preferred means of running migration processes. However, particularly while developing your migration processes, you may want to run processes directly in the browser. To do so, open the Execute fieldset and submit the form. You may set the following parameters for an interactive run:

Update previously-imported content
Equivalent to the --update option in drush, this causes previously-imported content to be remigrated from the current source data, in addition to new content being imported.
Sample size
If set, this number of rows of each checked content set will be processed before completion.
Source IDs
If set to a comma-separated list of primary keys from the source view, those specific IDs will be run through each checked process. This is useful when determining a problem processing a specific row of source data.

When executing interactively, first any Clear actions are run in reverse order, then any Import actions are run in forward order.

Stop all running tasks can be used to cleanly exit any processes running elsewhere (i.e., any processes that are highlighted).

In the lower area of the page, you may create a new content set, providing these parameters:

Description
A user-friendly name for the content set, used for display in various places. It also may be used to specify which content set to process on a drush command.
Destination
The Drupal object which this content set will populate. The migrate module has builtin support for the following Drupal objects, and you can also use hooks to define customer destinations:
Source view
A view containing the source data for this content set. This view must contain a single row for each destination object to be created (e.g., a single row per user, or per Page node). It also must have at least one unique data column.
View arguments
It may be that you want to use a single view as the source for multiple content sets - for example, you might have an incoming "content" table which contains both articles and blog entries. In this case, you would add an argument to the view definition to distinguish the cases, and create separate content sets for the different cases. Here you specify the distinct argument used to select rows from the view for this content set.
Weight
A numerical value used to order content sets in listings, and when processing multiple content sets in a single operation. For example, if you are migrating roles, then assigned migrated roles to users, you should give your role content set a lower weight than the user content set so it is processed first.

When you click the Add button, the content set is created, with its primary key defaulted to the primary key of its base table (if there is one), and the content set's edit page is displayed to allow you to add mappings.