Etlworks makes it easy to copy, export, and import Flows — including all related Connections, Formats, Macros, and Listeners. This is useful for:
- Duplicating an existing Flow.
- Migrating Flows between environments.
- Backing up or sharing Flows with others.
New in release 10.1.0: flows can be exported and imported as readable JSON (.etlworks.json), and the import collision policy can be fine-tuned per object type with Also replace / Also keep. Details below.
Duplicate a Flow
To quickly clone an existing Flow:
Step 1. Go to the Flows page.
Step 2. Click Duplicate Flow.
Step 3. Enter a new name for the Flow.
The duplicate will retain all original settings.
Export Flow(s)
To export one or more Flows:
Step 1. Navigate to the Flows page.
Step 2. Click Export/Import Flow and choose Export.
Step 3. Select one or more Flows to export.
Step 4. Click Export Selected or Export All.
You’ll download a.etld file containing the selected Flows and all related Connections, Formats, Macros, and Listeners.
Note: If the Flow is nested, all subflows and dependencies will be included in the export.
Export as JSON
Since 10.1.0, the Export dialog has two new options:
- File format: Encrypted (.etld) — the default, unchanged — or Readable JSON (.etlworks.json): a single readable file that every Import accepts. Readable exports contain no IDs, timestamps or owners, and an unchanged export is byte-identical — reviewable, diffable, and ideal for keeping flows in Git.
- Connections: how connection credentials are written — Without secrets (the default: password fields are never written, and on import the target keeps its own secrets), Reference only (only connection names and types; the target must already have them), or With encrypted credentials (password fields as encrypted envelopes; the choice appears only when an export key is configured).
For the readable format in depth — the file layout, projects, deploying with plan and apply, and keeping flows in Git — see Data Integration as Code.
Import Flow(s)
Step 1. Go to the Flows page → Export/Import Flow → Import.
Step 2. Click Choose the flow file to import, then select a .etld or a readable .etlworks.json file.
Step 3. Select which Flows to import.
Step 4. Choose a collision policy (see below).
Step 5. Optionally expand the flow to import and replace connections and formats with connections and formats that already exist in your system.
Step 6. Optionally, add tags.
Step 7. Optionally, if you don't want to import credentials enable Do not import connection credentials. This is useful when importing flows from different environments.
Step 8. Optionally, enable Import schedules. This will import schedules (if exist) from flows included in the import file.
Step 9. Click Import Selected or Import All.
Note: If importing a nested Flow, all related resources (Connections, Formats, Macros, Listeners) will be imported automatically.
Collision Policies
When importing, choose how Etlworks should handle naming conflicts:
-
Add: Create entirely new objects with a timestamp suffix.
Example: My Flow [05-17-2024_14-52-41].
- You can rename these later (ensure uniqueness).
- If the Flow uses an HTTP Listener, update the URL Pattern (must be globally unique).
- Replace: Replace existing Flows, Connections, Formats, Macros, and Listeners that match by name and type.
- Keep: Keep existing artifacts and skip importing duplicates.
-
Keep all, replace Flows and Macros: Replace only Flows and Macros. Keep existing Connections, Formats, and Listeners.
Ideal for migrating between environments.
Fine-tune the policy per type (10.1.0+): after choosing a policy, the Also replace and Also keep multi-selects adjust it per object type (Flows, Macros, Formats, Schedules, Connections), and the dialog shows the effective result in one line, for example: "Replace: flows, macros, formats, schedules. Keep: connections." The same control is available in the CLI as the replace=, keep=, copy= and fail= modifiers.
Add Tags on Import
If selected, Etlworks will add the chosen tags to all Flows, Connections, Formats, and Listeners created or updated during import.
Cannot import a Flow
If the Connection or Listener used in the Flow contains the IP address 127.0.0.1 or localhost, it cannot be imported to the tenant or the account on the shared instance.
Workaround
The solution is to replace 127.0.0.1 or localhost with something else.
Export File Encryption
All exported.etld files are encrypted by default.
Readable JSON exports (10.1.0+): credentials included in a readable .etlworks.json file (the With encrypted credentials option) are encrypted with the same Private Key — or with the Readable JSON Key, a passphrase of at least 32 characters, when no private key is set. Both are under Settings → Security → Export/Import Encryption. On servers with multiple tenants, including Etlworks Cloud, the export key is shared by every tenant, so tenant users can't export or import encrypted credentials: export without secrets and set credentials in each environment instead. See Credentials and secrets.
To use your own encryption key:
Step 1. Go to Settings → Security → Export/Import Encryption.
Step 2. Upload a private key in PEM format (-----BEGIN RSA PRIVATE KEY-----).
Step 3. Optionally, add a passphrase.
How To Generate Key
You can generate a key using:
ssh-keygen -t rsa -m PEM- On Linux/Mac: Use directly in terminal.
- On Windows: Use PowerShell (if OpenSSH is installed) or PuTTY.