Skip to main content

RouterShift

Multi-vendor network device configuration converter. It reads a switch or router configuration, turns it into a vendor-neutral model, and writes it out for another platform, together with a report that says, item by item, what was converted exactly, what was approximated and what a person has to look at.

Platforms: Cisco IOS / IOS XE and NX-OS, Arista EOS, Juniper Junos, HPE Aruba AOS-CX, AOS-S (ProCurve) and Comware 7. The manual explains how to use it, docs/SCOPE.md lists what converts per area and platform, CONTRIBUTING.md explains how to help and CHANGELOG.md lists the releases.

It is a quick reference for how a configuration looks on another platform, not a migration tool: read the output and the report before anything goes near a live device.

RouterShift is the sibling of FWShift, which does the same for firewall policies.

Status

Alpha (0.1.0). Cisco IOS / IOS XE, Arista EOS, HPE Aruba AOS-CX, AOS-S (ProCurve) and HPE Comware 7 convert in every direction for the system settings (hostname, domain, DNS, NTP with authentication keys, syslog, banner, spanning tree (mode, priorities, MST region, port guards), SNMP communities, v3 users and notification hosts), VLANs, interfaces (switchport access and trunk, voice VLAN, LAGs and LACP, SVIs, loopbacks, the management port, subinterfaces), IPv4 and IPv6 addressing, DHCP relay and server, VRFs, static routes, IPv4/IPv6 access lists with their interface bindings, gateway redundancy (HSRP, VRRP, anycast gateways), OSPF, BGP, NAT and site-to-site IPsec VPNs (on IOS, EOS and Comware; the AOS switches have neither), local users and privilege levels, and AAA (RADIUS and TACACS+ servers and groups, login, enable, command and accounting method lists), 802.1X and MAC authentication on ports, the TFTP/FTP source interface, QoS (classes, policies with DSCP marking and policing, port trust), MPLS with LDP (on IOS, EOS and Comware), and wireless networks (SSID, VLAN, security) between IOS XE and Comware controllers, flagged on the switches that have none. Management access converts too: SSH, Telnet and HTTP(S) servers, the remote login ACL and idle timeout, the syslog level and source, and LLDP and CDP (globally and per port). Layer 2 security converts as well: DHCP snooping, ARP inspection, IP source guard, port security and storm control. VRF route leaking (route distinguisher, import and export route targets) and multi-chassis LAG pairs (EOS MLAG and AOS-CX VSX, flagged on IOS, AOS-S and Comware) convert too. Prefix lists and route maps (Comware route policies) convert with the BGP neighbors and redistribution that apply them, and so do policy-based routing and BFD (timers, BGP neighbors, OSPF). RIP and IS-IS convert between IOS, EOS and Comware (flagged on the Aruba switches). Multicast converts too: IGMP snooping per VLAN with its querier, and multicast routing (PIM mode, IGMP version, static RPs). Port mirroring (SPAN) and sFlow convert on every platform; NetFlow between IOS (Flexible NetFlow) and Comware (NetStream), and is flagged elsewhere, as is sFlow on IOS. IP SLA probes (Comware NQA) and tracked objects convert between IOS and Comware with the static routes and gateway groups that use them; EOS takes the interface tracks, and the rest is flagged. The DNS client (lookup switch, search domains, source interface, static hosts) and PoE per port (on/off, priority, power limit) convert as far as each platform has the setting. VXLAN (VTEP source, VLAN and VRF VNIs, static flood lists) and BGP EVPN (neighbors, advertised VLANs) convert between IOS, EOS and AOS-CX, and are flagged on AOS-S and Comware. Juniper Junos reads and writes the core of a switch or router configuration, in either the curly-brace form or display set lines: system settings (hostname, DNS, NTP with keys, syslog, time zone, banner, SSH, local users), SNMP communities, VLANs, ports and aggregates with LACP, access and trunk ports, irb, loopback and management interfaces, subinterfaces, IPv4/IPv6 addresses, VRFs (routing instances with RD and route targets), static routes, OSPF, BGP (groups, EVPN family), LLDP and spanning tree (RSTP, MSTP, VSTP). Every other feature read from another platform is listed in the report as "not written for Junos yet". Cisco NX-OS reads through the IOS reader (with its own blocks: features, vrf context, neighbor blocks, hsrp and vrrp blocks, use-vrf) and writes the system settings, users, SNMP communities, VLANs, ports, port-channels, SVIs, the management port in VRF management, VRFs and their static routes, ACLs, prefix lists and route maps, HSRP and VRRP, DHCP relay, storm control, OSPF (interface-based, VRFs in the process), BGP (neighbor blocks, EVPN family), spanning tree (rapid PVST+, MST), LLDP and the vty settings. Everything else is reported as "not written for NX-OS yet". BGP covers IOS XE peer templates (written into each neighbor), BGP inside VRFs (IOS address-family ipv4 vrf, EOS, NX-OS and AOS-CX vrf, Comware ip vpn-instance), session passwords, timers, route-reflector clients, prefix limits, allowas-in, remove-private-as and maximum-paths. What RouterShift recognises but does not convert (EEM, telemetry, certificates, the zone-based firewall, EIGRP, DMVPN, NBAR, queuing, ...) is reported once per feature under "Recognised, not converted", with the reason and the line numbers. Everything else is listed under "Not understood", grouped by the block it is in, with secrets masked.

Usage

pip install routershift      # or, from a checkout: pip install .
routershift convert --from ios --to aoscx running-config.txt -o aoscx.cfg --report report.txt
routershift parse --from eos running-config.txt      # the vendor-neutral model as JSON
routershift platforms

The report says, for each item, whether it was converted exactly, approximated (with what changed), needs review, or was skipped.

Port maps

Ports are renumbered for the target (for example GigabitEthernet1/0/1 becomes Ethernet1 on EOS) and every renumbered port is flagged in the report. For a real migration, give a port map with --port-map ports.txt:

# source port = target port
GigabitEthernet1/0/1 = Ethernet7
TenGigabitEthernet1/1/1 = Ethernet49/1

Requirements

Python 3.9 or later, no other dependencies.

Licence

GPL-3.0-or-later. See LICENSE.

Metadata

Release files for routershift 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for routershift 0.1.0
File Size Uploaded Provenance Actions
routershift-0.1.0.tar.gz 367.3 kB With provenance Details for routershift-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for routershift 0.1.0
File Interpreter ABI Platform Actions
routershift-0.1.0-py3-none-any.whl Python 3 none any Details for routershift-0.1.0-py3-none-any.whl

Total release size: 702.3 kB

Release files / routershift-0.1.0.tar.gz

Download URL routershift-0.1.0.tar.gz
Size 367.3 kB
Tags Source
SHA-256 checksum
How to use checksums
7965c944bf0cb49a4fe09dab00075ab2621be29ec494f0308545c89689bdb437
BLAKE2b-256 checksum
How to use checksums
d9ac185f46b8902db043c1d255e437f02baba3898cd917325c3a4455b4d247b8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.

Transparency log

Release files / routershift-0.1.0-py3-none-any.whl

Download URL routershift-0.1.0-py3-none-any.whl
Size 335.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
63998e64c6781fdc1d2e1ca487198f66e7db7475f6c0f9238863105a8782a13b
BLAKE2b-256 checksum
How to use checksums
c2f93642e4c1c2d6601d139d697b1fd3f53ca050026d7553fa38ebe1813a23bf
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.

Transparency log

Security for routershift 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for routershift-0.1.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page