--- schema_version: "1" id: 067fb142eeb0d98e6be4734bee5ca1bd085d1463dc03109a728ad160fee06efc title: Data Deployment with Data Packs (Managed Package) collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_data_deployment_with_datapacks.md canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_data_deployment_with_datapacks.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 8d8b712e52b03fa254acc35fe460c0f2a7b45e8cb232991754b1d936ad325009 description: For the managed package runtime, a data pack is a collection of components and related functionality that are packaged for deployment between orgs. For example, you can use data packs to deploy functionality from a sandbox environment to a production environment. products: - Omnistudio release: "264" --- # Data Deployment with Data Packs (Managed Package) For the managed package runtime, a data pack is a collection of components and related functionality that are packaged for deployment between orgs. For example, you can use data packs to deploy functionality from a sandbox environment to a production environment. ![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 save in a data pack any object listed in [Supported Data Pack Object Types (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_supported_datapack_object_types.htm&release=264.0.0&type=5 "For the managed package runtime, objects that can be exported as data packs are listed here."). ![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 When you import and export data, we recommend limiting the file size to 2 MB. If you get the error Unable to connect to server (transaction aborted: timeout), use a file that is 1.3 MB or smaller. Other factors such as your Omnistudio configuration, dependencies between Omniscripts, or data shape also contribute to the success of deployment. Manually created data packs are suitable for deploying small numbers of similar objects, for example, moving Omniscripts from a development org to a production org. However, to bulk-export complex corporate data such as products, use one of these tools: - IDX Workbench deploys objects and metadata between orgs or between orgs and Git repositories. See [IDX Workbench Desktop Application (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_idx_workbench_desktop_application.htm&release=264.0.0&type=5 "For the managed package runtime, IDX Workbench is a desktop application that you use to deploy Omnistudio data packs and Salesforce metadata. Its user interface is built on top of the Omnistudio Build Tool. The application is available for Mac and Linux."). - The Omnistudio Build Tool creates data packs that preserve object relationships. See [Data Deployment with the Omnistudio Build Tool (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_data_deployment_with_build_tool.htm&release=264.0.0&type=5 "For the managed package runtime, the Omnistudio Build Tool (formerly Vlocity Build Tool or VBT) is a Node.js command-line automation tool that packages and deploys Salesforce data packs in a source-control-friendly format. The tool creates a YAML (YAML Ain’t Markup Language) manifest that describes a deployment project. The Build Tool enables continuous integration of Omnistudio metadata to source control."). To simplify deployment of multiple related objects, combine data packs into multipacks. To maintain maximum control over groups of related data packs, incorporate version control and continuous integration tools into your development and deployment process. Deployment is best performed by Salesforce administrators with a solid understanding of how data is stored in Salesforce. Success depends on high-quality source data. ![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 You can import data packs of some older Omnistudio for Managed Packages objects into an Omnistudio standard runtime org. Omnistudio Data Mapper, Integration Procedure, and LWC-enabled Omniscript objects are automatically converted to Salesforce standard objects. Omnistudio doesn’t support the following: - Importing data packs of Omnistudio objects into an Omnistudio for Managed Packages org - Importing Cards between Omnistudio and Omnistudio for Managed Packages orgs - **[Create a DataPack or a MultiPack (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_create_a_datapack.htm&release=264.0.0&type=5)** For the managed package runtime, to deploy data between orgs, you can create and export DataPacks, which are files with a selected object’s data in JSON format. A single DataPack contains one main object and its dependent objects. A MultiPack is a DataPack that contains multiple main objects and their dependent objects. - **[Import a Data Pack (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_import_a_datapack.htm&release=264.0.0&type=5)** For the managed package runtime, after you create a data pack, you can import it into another org. - **[Supported Data Pack Object Types (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_supported_datapack_object_types.htm&release=264.0.0&type=5)** For the managed package runtime, objects that can be exported as data packs are listed here. - **[Publish Data Packs to Connected Orgs (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_publish_datapacks_to_connected_orgs.htm&release=264.0.0&type=5)** For the managed package runtime, instead of managing data pack files manually, connect two orgs and publish data packs from the source org to a target that you configure as a Salesforce connected app. To connect two orgs and publish data packs from one to the other, you must create, authenticate, and configure the connected app. - **[Fix the DataPack Import or Export Error: No Configuration Found (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_fix_the_datapack_import_export_error_no_configuration_found.htm&release=264.0.0&type=5)** For the managed package runtime, if you see the error message No Configuration Found while trying to import or export a DataPack, the issue is most likely with the configuration of the Salesforce org. This error often occurs in developer sandboxes that are missing some of the configuration files owing to a recent refresh or an install or upgrade that has missed a post-install or post-upgrade step. You can fix this error with code in Anonymous Apex.