Network Device Import Methods
Network Device Import Methods - CSV, API, Manual & Integration Guide
Section titled “Network Device Import Methods - CSV, API, Manual & Integration Guide”After reading this page, you can compare the five ways to add devices to rConfig V8 (manual entry, cloning, REST API, CSV import, and Device Sync) and choose the right one for your deployment size and source systems.
The five import methods
Section titled “The five import methods”Manual entry
Section titled “Manual entry”Best for: adding 1-5 devices, testing, or when you need full control over every field.
Click Add Device from the Devices table and fill in the name, IP address, credentials, vendor/model, command group, and connection settings. See Devices Management for the full field reference.
Manual entry suits initial testing and proof-of-concept setups, one-off additions such as a new router or replacement switch, devices with unique or complex configuration, and learning the rConfig device model before running a bulk import.
Device cloning
Section titled “Device cloning”Best for: adding devices that are similar to ones you already have, such as routers at the same site or switches sharing a configuration.
Find an existing device close to what you need and click clone. rConfig copies the vendor, model, credentials, connection protocol settings, command group, tags, and templates. Only the device name and IP address (both required) need to change, along with anything else that differs. See Devices Management for where the clone action lives in the device table.
Cloning works well for deploying standardized equipment across sites, adding multiple devices of the same type, and rapid expansion where consistency matters more than per-device customization.
REST API
Section titled “REST API”Best for: automation, scripting, external integrations, or when device data already lives in another system.
The Device API Reference lets you create, read, update, and delete device records programmatically. If device data lives in spreadsheets, databases, monitoring tools, or other management platforms, a script can push that data into rConfig using the same fields available in the UI.
Typical uses include automated provisioning workflows, syncing with CMDBs or ticketing systems, custom provisioning portals, CI/CD pipeline integration, and bulk operations via Python, Bash, or PowerShell.
CSV import
Section titled “CSV import”Best for: importing 10-1000+ devices at once, migrating from another system, or working from spreadsheet data.
Export your device list as CSV and upload it through Settings → Import/Export. rConfig maps columns to device fields and creates all the records in one pass. The Device Import Workbook covers the full column reference, ID lookups, and upload steps.
A CSV import can include core device fields (name, IP, vendor, model, command group), credentials, connection settings (protocol, port, timeout), comma-separated tags, and custom fields. Before a large run, download the CSV template from rConfig, test with 5-10 devices, keep the source CSV as a backup, and check for duplicate IPs or names.
Device Sync integrations
Section titled “Device Sync integrations”Best for: organizations already using NetBox, Nautobot, or Zabbix as their source of truth.
If an IPAM/DCIM system or monitoring platform already tracks your devices, configure a Device Sync integration instead of duplicating that data. The source system stays the system of record, and rConfig consumes it:
- NetBox Device Sync: full device sync with site, role, and platform mapping
- Nautobot Device Sync: the same rich mapping as NetBox
- Zabbix Device Sync: pulls monitored hosts directly into rConfig
After the integration is configured with API credentials and field mappings, a sync (manual or scheduled) creates and updates devices automatically, so future syncs keep rConfig current with the source system.
Choosing the right method
Section titled “Choosing the right method”- 1-5 devices with unique configuration: manual entry
- Devices similar to ones you already manage: cloning
- Device data already in another system, no existing integration: REST API or CSV
- 10-1000 devices from a spreadsheet: CSV import
- Using NetBox, Nautobot, or Zabbix: Device Sync integration
- Ongoing automation: REST API or Device Sync
These methods can be combined. Many teams use Device Sync for the bulk of their infrastructure, manual entry for test devices, and cloning for rapid site deployments.
What happens after import
Section titled “What happens after import”Regardless of the method used, every device follows the same path:
- The device record is created in the database.
- Credentials are validated, if testing is enabled.
- The command group and tags are applied.
- A connection template is assigned based on vendor and model. For multi-vendor environments, see Universal Device Support.
- The device becomes available for backup tasks, policy compliance, and reporting, and appears in the Device Inventory.
From here, you can run manual or scheduled backups, apply compliance policies, send configuration snippets, generate inventory reports, and compare configurations over time.