Seamlessly Migrate from RANCID NCM to rConfig
Retire RANCID's CVS-era workflow and Perl glue. Move your entire router.db inventory to rConfig's professional lifecycle management platform in minutes using our automated CLI tool.
Trusted by 10,000+ Network Engineers worldwide.
[INFO] Located CVS repository at /var/rancid.
[INFO] Found 1,240 nodes across 8 groups.
[INFO] Mapping device types (cisco, juniper, foundry)...
✔ 45 Templates matched.
✔ Schedule created.
Why Move Beyond RANCID?
RANCID does one thing well, pulling configs into CVS, but full lifecycle management requires more. rConfig centralizes scheduling, templating, auditing, and reporting in one intuitive platform. With our Import Tool, migrating your entire inventory from router.db happens in minutes, completely automated.
Rapid, error-free migrations powered by a scriptable CLI, no manual steps.
Centralized Scheduling
Move beyond cron and Perl wrappers. Build visual, policy-aware backup schedules per device group, region, or change window.
Advanced Templating
Go beyond per-vendor login scripts. Use compliance templates that span device families and surface drift the moment it happens.
Comprehensive Support
Stop maintaining community clogin, jlogin, and flogin scripts. rConfig supports 100+ vendors out of the box with dedicated enterprise support available.
Rich Reporting
Replace cvs log and grep with inventory, compliance, and change reports rendered in seconds, exportable to PDF or CSV.
Automated Workflows
Trigger Slack, email, or webhook alerts when a critical router config changes. No more nightly diff emails in your inbox.
Risk Reduction
Eliminate the single points of failure baked into fragile RANCID expect and Perl scripts. Run on a maintained, documented platform.
Migration in 3 Simple Commands
Our dedicated CLI utility handles the heavy lifting. No manual CSV editing, no copy-pasting IP addresses out of router.db.
> Enter RANCID Group Name: routers_nyc > Enter rConfig Category ID [1]: 5 > Enter rConfig Tag ID [optional]: 2 > Mapping created: routers_nyc -> Category(5) -> Tag(2)
> Parsing /var/rancid/router.db... > Reading CVS metadata... OK > Found 342 nodes across 6 groups. > Validating node connectivity... 100% > Data loaded into staging table.
> Starting import process... > [1/342] Processing NYC-Core-01... Created (ID: 1042) > [2/342] Processing NYC-Dist-01... Created (ID: 1043) ... > Import Complete. 342 Devices added. > 0 Errors encountered.
Your First Hour After Migration
From raw router.db rows to actionable insights in four steps.
Verify Devices
Review the imported inventory dashboard. Ensure all 1,000+ nodes are online and reachable.
Assign Schedules
Group devices by region or function and apply granular backup schedules (hourly, daily, weekly).
Apply Policies
Attach compliance policies to detect configuration drift immediately after the first download.
Generate Reports
Export a full inventory and status report to PDF/CSV for management visibility.
Coming from a different open-source tool? See the Oxidized migration guide. Coming from a commercial tool instead? See rConfig as a SolarWinds NCM alternative or an Infoblox NetMRI alternative.
Frequently Asked Questions
Retire the CVS-era workflow. Migrate to rConfig today.
Move your RANCID router.db inventory to rConfig's professional lifecycle management platform in minutes using our automated CLI tool.