How to migrate an EVE-NG lab to netplex
Coming from EVE-NG? Your labs move across without a rebuild. EVE-NG exports a lab as a .unl file (its "Unified Network Lab" format); netplex. reads that file directly and converts it to its own .npx model - every node, interface and link. This guide walks the full migration.
What you gain: labs run on a shared server and open in any browser (no client, no local hypervisor per machine), and every topology is isolated by design - nodes have only the links you draw, with no hidden management LAN.
In EVE-NG, export the lab you want to move - that produces a .unl file. If your nodes use custom images, zip the lab folder instead; netplex. accepts the .zip too.
On the Labs page in netplex., click Import (top-right). The picker auto-detects the format - you do not pick "EVE-NG" from a list, you just hand it the .unl file.
netplex. reads the .unl, rebuilds the topology, and converts each EVE-NG bridge network into real links between the right interfaces. Here a three-node campus (two routers and a PC across two segments) lands as a new lab with its wiring intact.
Open it and the canvas is your EVE-NG lab, converted - same nodes, same interfaces, same links. EVE-NG templates map to the closest netplex. runtime; where a licensed vendor image was referenced, assign it from your Library (netplex. never ships vendor images) and power on.
Structure is preserved exactly - topology, interfaces and links always come across; the only manual step is assigning images where an EVE-NG template has no netplex. equivalent. A .zip of several exports imports them all at once. See the related guides for migrating from GNS3 and ContainerLab, and for importing the Cisco IOL / Juniper vSRX images your labs rely on.