Salesforce’s OmniStudio platform enables rapid development of guided processes, data retrieval components, and user interfaces like OmniScripts, FlexCards, Integration Procedures, and more. However, after Salesforce introduced the new standard OmniStudio following the Industries Cloud migration, many admins and developers discovered that the familiar Import/Export buttons were missing from the OmniStudio Designer.
Migrating components between environments — such as from sandbox to production — or sharing reusable assets across projects is a common requirement for Salesforce teams. Without clear guidance, this change in the UI can lead to confusion and slowdowns. This blog explains both your options for importing and exporting components in the new design: using Command Line Interface (CLI) and enabling the classic UI experience.
Two Methods to Import/Export
When Salesforce introduced the new standard OmniStudio after the Industries Cloud migration, many admins and developers noticed that the familiar Import/Export buttons were missing from the OmniStudio Designer. If you’ve been wondering how to migrate your OmniScripts, Integration Procedures, and FlexCards across orgs, here are the two methods you can use.
Method 1: Use Salesforce CLI (Recommended)
Salesforce has shifted the official support for Import/Export to the Salesforce CLI (SFDX). This is the preferred approach for automation, CI/CD pipelines, and bulk migration.
Example: Export a specific OmniScript:
SFDX omnistudio: export -p OmniScript -n “MyTestScript” -o ./export
Using the Salesforce CLI is the recommended method for importing and exporting OmniStudio components. The CLI brings automation support, makes it ideal for team workflows, and fits naturally into a DevOps pipeline with version control and continuous deployment.
Why Use CLI?
- Automation‑ready: Easily integrate export and import commands into scripts for repeatable deployment.
- Bulk Operations: Export multiple components or entire folders without navigating UI screens.
- Consistency: Removes manual error by codifying exports and imports via commands.
- Version Control: Integrate with Git to track changes over time.
Example: Exporting with CLI
To export an OmniScript called MyTestScript to your local machine:
SFDX omnistudio: export -p OmniScript -n “MyTestScript” -o ./export
This command creates a local file (in JSON format) representing the OmniScript’s configuration and metadata. You can use similar commands for FlexCards and Integration Procedures by changing the -p parameter accordingly.
Using CLI for Import
Once you have the exported JSON files, you can import them into another org using a corresponding CLI command, maintaining structure and relationships. This is particularly useful in CI/CD environments where automated deployments are key.
Method 2: Enable UI Import/Export via OmniStudio Settings
If you prefer the classic UI experience of clicking buttons, Salesforce still provides a way to bring back the Import/Export feature inside Designer.
Steps
1. Navigate to Setup → OmniStudio Settings.
2.Enable Managed Package Designer.
3.Refresh the OmniStudio Designer page.
4.You will now see the familiar Import and Export buttons in the UI.
Some users prefer a visual approach rather than command lines. If you are more comfortable with Salesforce’s point‑and‑click environment, you can re‑enable the classic Import/Export buttons by adjusting settings.
When to Use UI Import/Export
- You are working in an org that doesn’t use automation or CICD.
- You prefer visual confirmation before performing migrations.
- You are training new admins or team members unfamiliar with CLI.
This method restores a familiar experience inside OmniStudio Designer, making it easier to select components, run exports, and track migrations — all through clicks instead of commands.
Best Practices for Import/Export Workflows
Regardless of the method you choose, the following practices help ensure success:
1. Backup Before You Export or Import
Create backups in your source org before migrating components. This prevents accidental loss and lets you restore to a known good state.
2. Test in a Sandbox First
Always perform import/export tasks in a sandbox before executing in production. This reduces risk and lets you debug any issues.
3. Maintain Clear Naming Conventions
Use consistent naming for components, folders, and exported files. This simplifies searching and tracking when working with many assets.
4. Document Your Workflow
Maintain a record of components exported, imported, and any changes applied during the migration process. Documentation supports auditing and future troubleshooting.
5. Use Version Control with CLI
If you’re using Salesforce CLI, pair it with a version control system like Git to track configuration changes and enable rollback if needed.
Troubleshooting Tips
- CLI Not Recognized: Ensure Salesforce CLI (SFDX) is installed locally and authenticated against your org.
- Dependencies Missing: Verify objects and fields referenced by OmniStudio components exist in the target org.
- UI Buttons Still Not Visible: Double‑check OmniStudio Settings, refresh the designer, or clear browser cache.
Conclusion
Salesforce’s new standard OmniStudio has shifted migration workflows, removing familiar UI import/export buttons from the designer. Fortunately, you have two solid options: use Salesforce CLI for automation and scalability, or re‑enable the classic UI experience through settings when visual control is preferred. Both methods are valid and can be chosen based on your team’s workflow and preferences.
By integrating the original blog text verbatim and expanding around it with detailed explanations, examples, and best practices, this version ensures your content stays intact while improving readability, SEO value, and practical usefulness.