Config Promotion

Your Pinion setup lives as records — products, bundles, pricing and product rules, attributes, dimensions, discount schedules, block pricing, quote templates, and more. Config Promotion moves that configuration from one org to another — sandbox → production, or a template org → a customer org — idempotently: re-running a promotion never duplicates a record it already moved and never clobbers a record the target already has. It’s a Pinion+ feature, in the Pinion admin app under Config Promotion.

It works because every promotable record carries a SyncKey — a durable, cross-org identity (a UUID), immutable once stamped. A Salesforce Id is org-local (the same product has a different Id in each org), so promotion keys everything on the SyncKey instead: the idempotent upsert, the lookup remapping (a child points at the right parent in the target), and the source ↔ target diff.

Two paths, for two jobs:

  • Map & promote workbench — the granular path. Pick a connected target and a parent object; records list side by side (yours and the target’s), joined by SyncKey. You map each parent by hand, inspect a field-by-field diff, opt specific children out, then promote just what you checked. Use it to move a handful of records with review, or to reconcile two orgs whose keys have drifted.
  • Deploy to Sandbox — the bulk path. One click pushes your whole promotable catalog into a connected sandbox (update existing, create missing, leave unchanged alone), auto-matched by SyncKey. Use it to seed a sandbox after a refresh.

A promotion is self-contained: promote a record and Pinion carries its owned children (a rule with its conditions / actions; a product with its options, attributes, dimensions, schedules, block prices) and the records it references (pulled in so the import has no dangling lookup) — you don’t stage dependencies by hand.

See the user guide’s Config Promotion section for the click-by-click walkthrough.