> For the complete documentation index, see [llms.txt](https://docs.vex-nx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vex-nx.com/assist/recreate-labs-from-production-configs.md).

# Recreate labs from production configs

![Assist Studio for production-to-lab](https://1807546539-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhgHCHWL3861o2DBW53aA%2Fuploads%2FeuxaIAw2pvhAX5CWNo4e%2Fve20261112v5-assist-studio.png?alt=media)

## Goal

Turn exported device running-configs into a VEX-NX lab.

## When to use this

* You have text configs from production or another lab
* You want VEX-NX to recommend templates / images and build topology intent
* You need Map / Remap / Redesign across vendors (for example Cisco to another family)

Running-config import is available on both editions (Student and Enterprise).

## High-level flow

```
Production (or lab) configs
        |
        v
Paste / import into Migrate Lab (or Assist-guided import)
        |
        v
Parse devices, interfaces, protocols
        |
        v
Map -> choose VEX-NX templates / images
        |
        v
Optional Remap / Redesign for another platform
        |
        v
Create lab topology + ScriptPad drafts
        |
        v
Import matching images -> Wipe+Start -> verify
```

## Recipe (UI)

1. Configure Assist LLM (OpenRouter) if you use Assist-assisted steps
2. Open **Migrate Lab** (or use Assist with an import-oriented prompt)
3. Paste **synthetic or redacted** configs first when learning - strip real passwords, community strings, and customer addresses
4. Review detected devices and **Map** each to a Catalog template you have images for
5. Use **Remap** / **Redesign** only when you intentionally change platform family
6. Create the lab, assign Library images, save ScriptPad profiles
7. **Wipe** then **Start** nodes that need day-0 apply; open serial to confirm hostnames

## Limits (honest)

* Parsing quality depends on config style and vendor; always review the canvas
* VEX-NX does not download proprietary images for you
* Day-0 success still depends on nested virt, RAM, and template support ([Operate and consoles](/labs/operate-and-consoles.md))
* Redesign is an assistive transform - validate routing and interfaces manually

## Related

* [Using Assist](/assist/using-assist.md)
* [Migrate Lab](/labs/migrate-lab.md)
* [Features](/getting-started/features.md)
* Terminology (Map / Remap / Redesign)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.vex-nx.com/assist/recreate-labs-from-production-configs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.