How do you move OmniStudio components between orgs, and what commonly goes wrong?

Migration is where OmniStudio implementations most often lose a day, and almost all of it is predictable.

1. Use IDX Workbench to move OmniScripts, FlexCards, Data Mappers and Integration Procedures between orgs or between an org and source control, and the companion build tool to automate it in a pipeline.
2. Activation is the classic omission. Components deploy in an inactive state; the runtime only serves activated versions. A deployment that 'worked' but errors on first use is nearly always this.
3. Dependencies travel separately. An OmniScript that calls an Integration Procedure that calls a Data Mapper needs all three, plus any custom LWC, custom labels, custom objects and fields the definitions reference. Missing metadata fails at runtime, not at deploy time.
4. Environment-specific values — named credentials, endpoints, record Ids embedded in Set Values — must be parameterised or reconfigured per org rather than carried across.
5. Permissions differ. Deploying the component does not deploy the profile or permission set access the running users need on the underlying objects and fields.
6. Treat OmniStudio metadata as source-controlled artefacts and deploy through a pipeline. Manual designer changes in a higher environment are the other reliable source of surprises.