> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/verifone-central-device-management/verifone-central/devices/add-devices/bulk-import-devices.md).
# Bulk import devices
Use bulk import to add many device records from one file.
### When to use this flow
Use bulk import when:
* you need to add many devices at once
* the device records must exist before first contact
* your device data is already prepared in a supported file
If you only need to add one device, use [Add a single device](/verifone-central-device-management/verifone-central/devices/add-devices/add-a-single-device.md).
### Use bulk import for the right cases
Bulk import works best when:
* the same creation workflow applies to many devices
* the device data already exists in a reviewed source file
* you can validate the file before upload
### Before you start
Confirm that:
* your role allows bulk device creation
* your file is in **CSV** or **XML** format
* the file contains the device details required by your import flow
* the target placement data is ready for all devices in the file
* you are ready to review the import results after submission
### File readiness checks
Before you upload, confirm that the file:
* uses **CSV** or **XML**
* includes only the devices for this import
* contains consistent values across all records
* does not include known duplicates
* is the final reviewed version
### What to prepare
Before you upload the file, confirm that:
* the device identifiers are complete
* the device data matches the import flow you plan to use
* the file only includes devices you want to create in this import
* the file does not include devices that already exist
* the hierarchy and reference set values are ready for the imported records
Prepare a sample validation plan before you import:
* choose a few devices to review after import
* know the expected record count
* know where the imported devices should appear
### Validate the import file
Review the file before upload:
* confirm the file type is **CSV** or **XML**
* confirm each record has the required device details
* confirm device identifiers are unique within the file
* confirm the data is formatted consistently across all rows or records
* confirm the device count matches what you expect to import
{% hint style="warning" %}
Import only the devices you want to create now. Incorrect or duplicate records can slow cleanup after the import finishes.
{% endhint %}
### Understand what success looks like
A successful import means:
* the expected number of records are created
* rejected rows are understood and limited
* sample devices appear with the correct identifiers and placement
### Import the file
{% stepper %}
{% step %}
### 1. Open the bulk import flow
Go to **Verifone Central** → **Device Management** → **Devices** → **Add Devices**.
Open the bulk import option.
Select **Bulk Import Devices**.
{% endstep %}
{% step %}
### 2. Upload the import file
Upload the **CSV** or **XML** file.
Use the final reviewed file version. Avoid editing it again after validation.
{% endstep %}
{% step %}
### 3. Review the import details
Review the import details before you continue.
Check that the file and device count match what you expect.
If anything looks wrong, stop here and correct the source file before submission.
{% endstep %}
{% step %}
### 4. Submit the import
Continue to submit the import.
{% endstep %}
{% step %}
### 5. Confirm the outcome
After submission, review the import completion status and confirm that:
* the expected number of records were created
* failed or rejected records are understood
* the new devices appear in the expected hierarchy or context
{% endstep %}
{% endstepper %}
### If the import does not complete
Check these first:
* the file format is **CSV** or **XML**
* the file contains the required device details
* the file does not include invalid or duplicate device identifiers
* the import result in **Notifications** shows which action is needed
Review the notification result before you retry the import. Fix the source file first, then submit again.
#### Common outcomes
Use these checks to narrow the issue:
* **Only some devices were created** — compare the import result with the source file and isolate rejected records
* **No devices were created** — review the file format, required values, and submission details
* **Imported devices appear in the wrong place** — review the placement values included in the file
* **The records exist but devices do not connect later** — continue to [Registering the device](/verifone-central-device-management/verifone-central/devices/registering-the-device.md) and [Device heartbeats](/verifone-central-device-management/verifone-central/devices/registering-the-device/device-heartbeats.md)
### Verify the result
After the import completes, confirm that:
* the expected number of device records now exist
* key identifiers are correct on sample records
* placement values are correct on sample records
* the import notifications do not show unresolved failures
### Result
The file is processed and valid device records are added in bulk with their intended device data.
### Next steps
* [Notifications](/verifone-central-device-management/verifone-central/devices/alerts-and-notifications/notifications.md) — confirm import completion
* [View devices](/verifone-central-device-management/verifone-central/devices/view-devices.md) — review imported records
* [Device details](/verifone-central-device-management/verifone-central/devices/view-devices/device-details.md) — inspect a sample imported record
* [Registering the device](/verifone-central-device-management/verifone-central/devices/registering-the-device.md) — review first-time registration
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.verifone.com/verifone-central-device-management/verifone-central/devices/add-devices/bulk-import-devices.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.