Sync is a beta release feature. If you don’t see it in your subscription, contact your Entegrata Customer Experience Manager to ask about having it enabled.
Overview
Sync lets you take the data mapping work you’ve built on one pipeline and move it into another — for example, from a test pipeline into your production pipeline — without rebuilding any of it by hand. A pipeline is a working copy of your data mapping configuration: the entities, the fields on them, where each field comes from, and how they relate to each other. Most firms keep more than one:- A production pipeline (usually called main) that feeds real reporting.
- One or more test pipelines where new mapping work gets built and validated safely.
Sync moves mapping configuration only — the definitions of your entities and fields. It never moves your data, and it never changes the pipeline you’re syncing from.
Key Terms
What Sync Changes
Every sync overwrites the target; there is nothing to choose. A whole-pipeline sync makes the target match the source. Each difference it finds is handled the same way:
A single-entity sync is narrower: it replaces that entity’s mappings in the target with the source’s. It doesn’t copy metrics, and it never deletes the entity. See Two Scopes.
The Two Directions
Both directions are supported, and both are common:- Test → main. You built something new on a test pipeline and you want it live.
- Main → test (Sync from main). Your test pipeline has drifted from production and you want to reset it before starting fresh work.
Two Scopes
Sync works at two scopes. They are not the same feature at different sizes — they differ in what they can add, what they can remove, and what they check.
Start with single-entity sync when you want a surgical change and you know the entity isn’t entangled with others. Use whole-pipeline sync when entities are interrelated, or as your default when you’re syncing a body of work rather than one change.
Syncing a Single Entity
Move just one entity
Syncing Pipelines
Sync an entire pipeline into another
Where to Find Sync
Required permissions
- Entity Sync: Update on the entity’s layer (Manage Silver Entities or Manage Gold Entities) and Update on the target pipeline
- Pipeline Sync: Update on the source pipeline (Manage Production Pipelines or Manage Dev Pipelines) and Manage Silver Entities Update
- Sync from main: Manage Production Pipelines Read and Manage Silver Entities Update. The target must be a pipeline you can update.
On an entity
Open a pipeline, then open a layer — for example Silver — and click the three-dot menu (⋮) on any entity row:- Sync — copy just this entity into another pipeline.
On a pipeline
Find the pipeline you want to sync from, click the three-dot menu (⋮) at the right of its row, and hover Manage:- Duplicate — make an independent copy of this pipeline (not part of Sync).
- Diff — compare this pipeline against another and change nothing.
- Sync — push this pipeline’s mappings and metrics into another pipeline.
- Sync from main — the reverse: pull production’s mappings and metrics into this pipeline.
The main pipeline’s own actions menu has no Manage submenu. To sync into main, start from the pipeline you’re syncing from.
Publishing After a Sync
Two consequences are worth planning around:- If a scheduled run fires between your sync and your publish, it runs the old configuration.
- A target that was never published won’t run at all, and may report that it has no pipeline nodes.
- Tick the publish checkbox in the Sync dialog — Publish the target pipeline after syncing. It’s off by default, and publishes immediately after the sync is saved.
- Publish manually afterward, using the Publish action on the target pipeline. This is the right choice when you want to sync several changes, verify them together, and publish once.
“The sync was saved, but publishing failed.”
“{target} still runs the mappings it had before the sync. Publish it again to pick up these changes.”
Publishing again is the fix. You do not need to re-sync. Resolve whatever the failing entities report — usually a validation problem in the mapping itself — and publish the target again.
Publishing Mappings
What publishing does and what it requires
Managing Pipeline Status
Activate a pipeline for scheduled runs
Limits and What Sync Does Not Do
Being explicit so nothing is a surprise:- Source and target must be in the same firm and environment. You cannot sync across firms.
- The source is never modified. Sync is strictly one-directional per run.
- Data is never moved — only mapping configuration.
- Sync does not publish unless you ask it to.
- Access control entities are never synced. They’re deliberately excluded so a target can’t be left in an inconsistent access state.
- Renaming can look like a delete plus an add. Sync matches items by their stable key, so if something was renamed on one side, the comparison sees one item removed and a different one added rather than a rename.
Best Practices
Related Topics
Comparing Pipelines
Review differences without changing anything
Duplicating Pipelines
Create an independent copy instead of syncing
