Every time you deploy a pipeline, the platform saves a snapshot of its configuration as a new version. You can review what any version contained, restore an earlier one if a recent change causes problems, and move a pipeline's configuration between environments by exporting it to a file and importing it into a different pipeline instead of rebuilding it by hand.
Overview
Each pipeline keeps a running history of its deployments in the Versions tab. You can also move a pipeline's configuration elsewhere, such as into another environment, by exporting it to a file and importing it into a different pipeline instead of rebuilding it by hand.
Viewing Deploy History
Open a pipeline and go to the Versions tab to see its deploy history. Every deployment appears here, listed newest first, with a version number such as V1 or V2. The version that is currently live carries a Current pill so you can tell at a glance which one is active. Each row also shows who deployed the version and when. Before the pipeline's first deployment, the tab lets you know versions will appear here once you deploy.
Open any version from this list to browse its object selection, schema mappings and transformations, and settings in a read-only view — useful for comparing deployments before deciding whether to restore one.
Restoring a Previous Version
If a recent deployment introduced a problem, revert to an earlier version. Open the version you want to bring back and choose Restore this version. A confirmation screen explains that restoring will revert the pipeline's object selection, schema mapping, transformations, and settings to match that version. Once you confirm, the pipeline's draft is updated, and you'll see a message confirming the restore was successful. Restoring does not deploy the pipeline automatically, so review the draft and deploy it when you're ready.
Exporting a Pipeline Configuration
To move a pipeline's configuration elsewhere, open the pipeline's menu and choose Export Pipeline. This downloads the current configuration as a JSON file, which you can save, share, or use later to bring the same setup into another pipeline.
Importing a Pipeline Configuration
To bring a saved configuration into a pipeline, open the pipeline's menu and choose Import Pipeline. Drop the JSON file onto the upload area or select Upload JSON file to browse for it. The platform analyzes the file and validates it against the pipeline's source and destination connections before applying the object selection, schema mapping, and transformations it contains.
An import can be blocked or partially applied if the file doesn't line up with the pipeline you're importing into:
Validation failed. The file doesn't match any objects from either the source or the destination — usually because it was exported from a pipeline connected to different systems. Review the file and upload it again.
Missing fields. Some mappings in the file reference fields that don't exist on this pipeline's connections. The affected objects are skipped, while the rest of the selection and mapping is still imported. Review the skipped combinations, then continue or fix the file and try again.
When the import completes without issues, you'll see a message confirming the pipeline was imported successfully.
Notes
Restoring a version updates the draft only — deploy the pipeline afterward to make the restored configuration live.
Exported files contain object selection, schema mapping, and transformations, not connection credentials.
Import a configuration into a pipeline whose source and destination connections match what the file expects, to avoid validation errors.