# ERP machine mapping (https://docs.pulsarml.com/guides/settings/erp-machine-mapping)

Give each Pulsar machine the name your ERP system uses for it, one by one or from a CSV file.



Your ERP system may call a machine something different from its name in Pulsar. **ERP Machine Mapping** stores, for each machine with production, the name it has in your ERP, so that integrations between the two systems can match the same machine. It only links names; it doesn't send data to your ERP. To open it, go to **Settings** → **Production** and click the **ERP Machine Mapping** tab.

<Screenshot id="erp-machine-mapping" alt="Production settings on the ERP Machine Mapping tab, with the Import, Download and Add ERP Machine Mapping buttons at the top right and, below, the empty state No Machine Mappings Yet, Map a Pulsar machine to an ERP name to see it here." width="1440" height="380" />

## The mapping list [#the-mapping-list]

The tab lists the machines that already have an ERP name, with the **Machine** and its **ERP name**. Until you add one, it shows **No Machine Mappings Yet**. Each machine can have one ERP name. To change it, use the menu on the machine's row.

## Add a mapping [#add-a-mapping]

<Steps>
  <Step>
    Click **Add ERP Machine Mapping**. The **Create ERP Machine Mapping** dialog opens.

    <Screenshot id="erp-machine-mapping-add-dialog" alt="The Create ERP Machine Mapping dialog, with the required Machine field showing Select Machine, the required ERP name field showing Enter ERP name, and the Cancel and Add ERP Machine Mapping buttons; Add ERP Machine Mapping is greyed out." width="562" height="354" />
  </Step>

  <Step>
    In **Machine**, choose the Pulsar machine. The list has a search box and only offers machines with production that don't have an ERP name yet.
  </Step>

  <Step>
    In **ERP name**, type the machine's name exactly as it appears in your ERP.
  </Step>

  <Step>
    Click **Add ERP Machine Mapping**, or **Cancel** to close the dialog without saving.
  </Step>
</Steps>

## Import mappings from a file [#import-mappings-from-a-file]

<Steps>
  <Step>
    Click **Import**. The **Import ERP Machine Mapping** dialog opens.

    <Screenshot id="erp-machine-mapping-import-dialog" alt="The Import ERP Machine Mapping dialog, with an upload area that reads Browse and upload your files and First time uploading this file? Feel free to download the sample file, with sample file as a link, and the Cancel and Confirm buttons; Confirm is greyed out." width="696" height="368" />
  </Step>

  <Step>
    Click **sample file** to download the template, `import-erp-machine-mapping.csv`. It has two columns, `Pulsar name` and `ERP name`, and two example rows. Write one machine per row: its name in Pulsar, then its name in your ERP.
  </Step>

  <Step>
    Click the upload area and choose your file. Only `.csv` files are accepted.
  </Step>

  <Step>
    Click **Confirm** to import the mappings, or **Cancel** to close the dialog.
  </Step>
</Steps>

## Download the mappings [#download-the-mappings]

Click **Download** to save the current mappings as `ERP Machine Mapping.csv`, with the columns `Machine` and `ERP name`.

For integrations that read Pulsar data from your own systems, see the [API reference](/).