Skip to main content

​
Overview

A whole-pipeline sync moves every entity’s mapping configuration from a source pipeline into a target pipeline in a single operation. Because related entities move together, relationships stay consistent — which is why this is the recommended default over syncing entities one at a time.
Nothing in the source pipeline changes. A sync only writes to the target.

​
Syncing a Pipeline

1

Open the Sync Dialog

From the pipelines list, click the three-dot menu (⋮) on the pipeline you’re syncing from, hover Manage, and click Sync.A dialog opens, titled Sync {source} to {target}.
2

Check the Direction

A blue panel labeled Syncing shows From (the pipeline you clicked) and To (the target).Read this before anything else — it’s the fastest way to catch a backwards sync.
3

Pick the Target

The Target pipeline dropdown defaults to your main pipeline, shown as {name} (main). Change it if you’re syncing somewhere else.The source pipeline is never offered as its own target.
4

Pick a Strategy

Three cards are available: Overwrite, Merge (review changes), and Overlay. Selecting one shows a banner describing exactly what it will do.
Overwrite deletes anything in the target that doesn’t exist in the source. If you’re unsure what the target contains, choose Overlay or Merge.
5

Write a Reason

The Reason for Sync box is required for Overwrite and Overlay — the Sync button stays disabled until you fill it in.Your reason is saved to the target’s change history, so write something a colleague would understand in three months:
“Syncing new billing-attorney fields validated on test.”
If you chose Merge, you’ll enter the reason later, at commit time.
6

Decide About Publishing

The Publish the target pipeline after syncing checkbox is off by default. Until the target is published, it keeps running the mappings it had before the sync.This is the step people miss — see Publishing After a Sync.
7

Click Sync

Click Sync to apply.If you chose Merge, the button reads Review changes instead, and takes you into the review wizard rather than applying anything.A full-screen overlay reads Syncing "{source}" to "{target}"... while it runs.
8

Read the Result

When it finishes you’ll get a notification summarizing the outcome, for example:
If anything needs your attention — a skipped entity, a failed publish, or nothing having changed — a Sync Result window also opens.

​
Sync from Main

⋮ → Manage → Sync from main opens the same dialog with the direction already reversed: main is the source, and the pipeline whose menu you opened is already selected as the target. Everything else works identically. This is the “reset my test pipeline to match production” shortcut. Overwrite is usually what you want here.
Sync from Main Before Starting New WorkStarting a change on a test pipeline that has drifted from production means you’re building on a configuration that no longer reflects reality. Resetting first keeps your eventual sync clean.

​
Reading the Results

Every sync reports a per-entity outcome. A notification always appears; the Sync Result window opens on top of it when something is worth a closer look. The result table has three columns — Entity, Outcome, and Reason: If you asked to publish, a banner reports how that went separately from the sync itself — green (“Published {target} — it now runs the synced mappings.”) or red, with the failing entities listed.

​
Where to Look Later

Every entity a sync changed gets an entry in the target’s change history, stamped with your reason, your user, and the time. That history is a full snapshot of the entity, so a sync is reviewable — and revertible — after the fact. This is why the reason field is required.

​
Best Practices

Diff First, Sync SecondRun Manage → Diff against the same target before syncing. It’s read-only, it takes a minute, and it turns “I think this is right” into “I know what’s about to change.”
Verify the Target After SyncingOpen the target pipeline and spot-check the entities you expected to change. Confirm the publish banner was green before assuming the new configuration is live.

​
Troubleshooting

​
The Sync Button Is Disabled

Problem: You’ve selected a target and strategy but Sync stays greyed out. Solution:
  • Fill in the Reason for Sync field — it’s required for Overwrite and Overlay.
  • Confirm a target pipeline is selected in the dropdown.

​
Nothing Changed

Problem: The result reports 0 changed and every entity as Unchanged. Solution:
  • The two pipelines already match for the strategy you chose. Run a Diff to confirm.
  • If you expected deletions to be applied, check whether you used Overlay — Overlay never deletes. Use Merge or Overwrite instead.
  • Confirm you saved your work on the source pipeline before syncing.

​
Entities Reported as Skipped

Problem: One or more entities show Skipped in the Sync Result window. Solution:
  • This is Overlay behaving as designed: it found entities that only exist in the target, and Overlay never deletes. Read the Reason column to confirm.
  • If you intended to remove those entities, re-run with Merge and explicitly turn on the removals.

​
The Target Still Runs the Old Mappings

Problem: The sync succeeded but reports and scheduled runs still reflect the old configuration. Solution: The target hasn’t been published. See Publishing After a Sync.

​
No Manage Submenu

Problem: The pipeline’s three-dot menu doesn’t show Manage. Solution: The main pipeline has no Manage submenu by design. To sync into main, start from the pipeline you’re syncing from.

Syncing a Single Entity

Move just one entity instead

Sync Strategies

Choose between Overwrite, Overlay, and Merge

Reviewing Changes with Merge

Approve differences one at a time

Sync Overview

Scopes, limits, and publishing