--- schema_version: "1" id: b0d2dc6a7777c197995f3d8a35b2eefc85020038346b1b93ad6b6c0edaf74c99 title: Configure for Deployment Between Orgs (Managed Package) collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_configure_for_deployment_between_orgs.md canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_configure_for_deployment_between_orgs.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 8dc619610c500361062f4298efe8e9f41fc57163574475b4920243d4f3a0a809 description: For the managed package runtime, you must configure a source org and a target org. Both orgs should have the same Omnistudio runtime. products: - Omnistudio release: "264" --- # Configure for Deployment Between Orgs (Managed Package) For the managed package runtime, you must configure a source org and a target org. Both orgs should have the same Omnistudio runtime. ![Managed Package app icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/resources-global/_corporate/images/managedpackageicon.png) This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see [Omnistudio Help](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_standard.htm&language=en_US). You can import data packs of some older Omnistudio for Managed Packages objects into an Omnistudio org. Omnistudio Data Mapper, Integration Procedure, and LWC-enabled Omniscript objects are automatically converted to Omnistudio objects. Importing data packs of Omnistudio objects into an Omnistudio for Managed Packages org isn't supported. Importing Cards between Omnistudio and Omnistudio for Managed Packages orgs isn't supported. 1. In the org you plan to use as your source, make sure the correct versions of Salesforce objects you want to deploy are active. Some objects, such as Omniscripts and Integration Procedures, have versions that can be activated and deactivated. Only active versions of such objects are deployed. 2. Open IDX Workbench. If no projects exist, the Configure Workspace dialog appears. If other projects exist and you want to create a new project, click the Edit icon on the main IDX Workbench screen to open the Configure Workspace dialog. 3. From the Repository dropdown list, select **New Repository**. You must create a repository for the project even if both your source and target are orgs. 4. In the New Repository dialog, specify a name and a repository folder. If the folder doesn't exist, it's created. Click **Save**. 5. From the Source dropdown list, select **New Environment**. (An environment is an org.) To configure limited access to an org, see [Configure an Org Using a Community User Login (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_configure_an_org_using_a_community_user_login.htm&release=264.0.0&type=5 "For the managed package runtime, when you configure an org for running Test Procedures, you can specify a Salesforce Community and authenticate as a Community user. This is especially useful for running Test Procedures in which user access affects the results."). 6. In the New Salesforce Org dialog, specify a name. 7. If your source is a sandbox org, change the Organization Type to https://test.salesforce.com. 8. Click **Log in using OAuth**. The Salesforce login window appears. Log in to the org. If the Allow Access window appears, click **Allow**. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/images/icon_note.png) Note If you use the Google Chrome browser and you're redirected to a `localhost` URL when you attempt to log in, open a new browser tab and paste this URL into the address field: `chrome://net-internals/#hsts`. Look under the Delete domain security policies heading. If localhost is in the Domain field, click **Delete**. 9. From the Target dropdown list, select **New Environment**. Repeat the same steps. To configure limited access to an org, see [Configure an Org Using a Community User Login (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_configure_an_org_using_a_community_user_login.htm&release=264.0.0&type=5 "For the managed package runtime, when you configure an org for running Test Procedures, you can specify a Salesforce Community and authenticate as a Community user. This is especially useful for running Test Procedures in which user access affects the results."). 10. From the Project dropdown list, select **New Project**. To use a Project object instead of configuring a project, see the next section. 11. In the New Project dialog, specify a name for your project. 12. Select the types of Vlocity and/or Salesforce objects to deploy. You can use the Search field to filter the list. Select all the types you need. ![In the New Project dialog, select Vlocity Types, type int in the Search field, and check the Integration Procedures box.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/omnistudio_for_managed_packages/images/selectips.png) 13. Click **Fetch DataPacks**. 14. Under Pick datapacks for project, you can optionally enter text to filter the names of the fetched objects. ![Under Pick datapacks for project, if you type Documentation in the Search field, the Documentation\_CacheTopLevel Integration Procedure is listed.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/omnistudio_for_managed_packages/images/fetchdatapacks.png) 15. Move the objects you want to deploy from the All datapacks list to the Selected datapacks list. You can use the Shift key to select multiple items in either list. ![The Documentation\_CacheTopLevel Integration Procedure is selected.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/omnistudio_for_managed_packages/images/selectdatapacks.png) You can click **Ignore Dependencies** to exclude dependent objects from deployment. 16. Click **Save**. The Configure Workspace dialog reappears. 17. To refresh comparison data whenever you save the workspace, make sure **Force refresh of data from orgs** is selected. ![image](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/omnistudio_for_managed_packages/images/forcerefresh.png) 18. Click **Save** to save the workspace. Messages appear as objects are fetched. To cancel, press Command-R on the Mac or Control-R on other operating systems. 19. When the listing is complete, IDX Workbench displays green + icons to indicate the new objects in the source org. 20. To edit the repository: 1. Click the Edit icon on the main IDX Workbench screen to reopen the Configure Workspace dialog. 2. Click the Edit icon next to the Repository dropdown list to open the Repository Settings. 3. Edit the Expansion Path if you want to change the subfolder of the repository folder in which data packs are stored. 4. Specify **Additional DataPack Query Filters** if you want to filter objects of the specified type in all projects that use the repository. Click **Add New Filter** to add as many filters as you need. For example, setting DataPack Type to Product2 and Additional Query Filter to `RecordTypeId != null` excludes non-Vlocity products. 5. Click **Save**. 21. To add objects to the project: 1. Click the Edit icon on the main IDX Workbench screen to reopen the Configure Workspace dialog. 2. Click the Edit icon next to the Project dropdown list to reopen the Project dialog. 3. Repeat steps 12 through 18 above.