# Load (Transform Input) Pipeline Step The _Transform Input_ step is used during the _Load_ section to perform the transformations defined in the data source configuration process. This page describes how the _Transform Input_ step works and how to configure it. ## Overview Originally, the logic contained within the _Transform Input_ step was part of the Data Loader itself. At that time, the Squirro data processing pipeline began with the _Enrich_ steps rather than the _Load_ step. In Squirro release 3.3.1, this logic was separated from the data loader itself and moved into a separate step, allowing for better troubleshooting. The _Transform Input_ step takes the extracted data in row format and transforms them to Squirro Item format by using the mapping configuration defined for the data source. [](https://s3.amazonaws.com/download.squirro.net/docs/technical/data-loading/transform-input.png) > **Note** > > If you wish to keep the functionality of the _Transform_ step in the data loading process, you can edit the `common.ini` file and change `item_transformation_in_pipeline =` from `true` to `false`. ### How It Works When you create a data source using a data connector from within the UI, you define the mapping configurations. Here, you define how a source field maps to a Squirro item field. Reference: Learn more about the Squirro [Item Format](../../api/item-format.md#data-loading-item). If the source document has a field such as `article`, we may choose to map that source field to the Squirro item field `title`. In the data loading process, this represents steps 2 and 3, _Map to item fields_ and _Map to labels_, as shown in the example screenshot below: [](https://s3.amazonaws.com/download.squirro.net/docs/technical/data-loading/title-body.png) > **Warning** > > Every document must include a mapped Title or Body field. ### Configuring the Transform Input Step The _Transform Input_ step includes a configuration option in your Squirro installation’s `common.ini` file named `item_transformation_in_pipeline`. This option controls whether the _Transform Input_ step is enabled (`true`) or not (`false`). When it is set to `false`, if the _Transform Input_ step is in a pipeline, it is skipped. There are no other step-specific configuration options within `common.ini` like you would find in some other steps (e.g. MIME detection). Reference: To learn more about configuring the _Transform Input_ step within `common.ini`, see [common.ini](../../admin/configuration/config-files/common-ini.md#admin-common-ini). ### Benefits of Transform Input Step The primary reason for moving the file mapping configurations from the Data Loader and creating a standalone step is to assist in troubleshooting. As part of the [Data Processing Pipeline](../index.md#data-processing), you can view data loading error logs within the Squirro Monitoring space. Reference: To learn more, see [Squirro Monitoring](../../ui/squirro-monitoring.md#ui-squirro-monitoring). Additionally, as part of the _Transform Input_ step, you can freely change the mappings of a data source without needing to extract the data again from the third-party system. > **Note** > > If you run into any errors you are unable to troubleshoot yourself, visit the [Squirro Support website](https://go.squirro.com/support) and submit a technical support request.