Conduit lets you export your saved routes as a JSON backup and import routes from a previous backup. This is useful when moving to another device, sharing route setups, or keeping a safety copy before making changes.
Exporting routes
- Open Conduit.
- Go to the Outbound Routes section.
- Open the Routes menu.
- Choose Export Backup.
- Save the JSON file when prompted.
The exported file contains your route definitions, including route names, short names, base URLs, follow-up route settings, and parameter mappings.
Importing routes
- Open Conduit.
- Go to the Outbound Routes section.
- Open the Routes menu.
- Choose Import Routes.
- Select a Conduit route backup JSON file.
- Choose how Conduit should handle matching routes.
Import options
Replace matching
Use this when the imported routes should update your existing routes. Matching routes are replaced, and new routes are added.
Add new only
Use this when you only want routes that do not already exist. Matching routes are skipped.
Keep both
Use this when you want to preserve your current routes and import copies of matching routes. Conduit gives copied routes unique names and short names where needed.
How Conduit detects matches
Conduit treats an imported route as matching an existing route when it has the same internal route ID, the same short name, or the same route signature. A route signature is based on the route's base URL and parameter mappings.
What gets backed up
- Route display names
- Short names used for auto-triggering
- Base URLs
- Parameter mappings
- Follow-up route short names
What is not backed up
- Payload history
- Callback history
- Launch failure history
Best practice
Export a backup before making major route changes. If you are importing shared routes, use Keep Both first if you want to compare the imported setup with your existing routes before replacing anything.
