# General Information

## Scanners and Importers

**Scanner** is the term used in  migration-center for an input adapter. It is used to read the data that needs processing into migration-center and is the first step in a migration project. 

**Importer** is the term used for an output adapter used as the last step of the migration process. It takes care of importing the objects processed in migration-center into the target system.

Scanners or importers have a unique name, a set of configuration parameters and an optional description. They work as a job that can be run at any time and can be executed repeatedly.

Scanners and importers are created, configured, started and monitored through **migration-center Client** but the corresponding processes are executed by **migration-center Job Server**.

For every run a detailed **history** and **log** file are created.

## History, Reports, Logs

A complete history is available for any Scanner or Importer job from the **History** window. It is accessible through the button/menu entry on the toolbar/context menu. 

The **History** window displays a list of all runs for the selected job together with additional information, such as the number of processed objects, the start and ending time and the status.

![](https://122685853-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fhelp%2F-M7Jio5MZ2wrMD1oKT6x%2F-M7JjLQczqKBYKbLLBlS%2F3.png?generation=1589485857571983\&alt=media)

Double clicking an entry or clicking the Open button on the toolbar opens the **log file** created by that run. The log file contains more information about the run of the selected job:

* Version information of the migration-center Server Components the job was run with
* The parameters the job was run with
* Execution Summary that contains the total number of objects processed, the number of documents and folders scanned or imported, the count of warnings and errors that occurred during runtime.

{% hint style="info" %}
The amount of information written to the log files depends on the setting specified in the ‘loggingLevel’ start parameter for the respective job.
{% endhint %}