--- cuppy_hub: salesforce cuppy_path: reference/official/data360/data-cloud-dev/guide/packages-data-kits.md cuppy_section: docs cuppy_doc: 58SW-7DR3 cuppy_doc_uuid: 216c94ad-28f3-4ee4-8b35-d1e11987b69b cuppy_permalink: https://cuppy.io/salesforce/d/58SW-7DR3 cuppy_version: 1 cuppy_updated: 2026-10-23T16:16:52.575Z cuppy_canonical: https://cuppy.io/salesforce/docs/reference/official/data360/data-cloud-dev/guide/packages-data-kits cuppy_mcp: https://cuppy.io/mcp cuppy_body_sha256: e11de7829dd3a94eed4e5bcc67e719cd12d3786ede7491ef6f3d4cbb7e8434e1 # cuppy_body_sha256 is over the document body ALONE, excluding both generated blocks. --- > Mirror of (Salesforce, Data 360 Developer Guide), read 2026-10-23. Salesforce's own page is the authority; this copy exists because that site refuses non-browser readers. ## Packages and Data Kits A package is a container to which you can add metadata components. It holds the set of related features, customizations, and schema that comprise your app. When packaging Data 360 metadata, you must add the metadata to a data kit, and then add the data kit to the package. Data kits streamline the package creation and installation process. For Data 360, the metadata represents the definition of Data 360 components in the Data 360 org and not the data. For example, the metadata can represent the definitions of calculated insights, profiles, and data streams. If you’re packaging both Data 360 metadata and Salesforce Platform metadata, create two separate packages: one for Data 360 metadata and one for all other metadata. Starting in Winter ‘25, including both Data 360 metadata, and non-Data 360 metadata in a single package isn’t allowed. To package Data 360 metadata components, first add the components to a data kit. Then add the data kit to a package. The package is then used to install the Data 360 components in a different org. A package can contain one or more data kits. You can’t add Data 360 metadata in an unlocked package. Customer developers, that is, developers doing in-house development for their own Data 360 instance, use data kits with unmanaged packages to deploy metadata from a test org to a production org. Salesforce partners who build apps and distribute them on AppExchange use managed packages to do both. Salesforce partners can develop apps for Data 360 customers. For managed packages, make sure that the namespace is enabled for your organization. For more information, see [Create and Register Your Namespace](https://developer.salesforce.com/docs/atlas.en-us.252.0.sfdx_dev.meta/sfdx_dev/sfdx_dev_unlocked_pkg_create_namespace.htm) All Data 360 feature metadata in a managed package is locked. As a package owner, you can control and protect the data kit metadata from unauthorized changes. After you install a package and deploy the data kit components, the components are locked. Subscribers can add components but can’t modify or delete any deployed mappings or components. If modifications are made to the deployed components, they’re overwritten when the data kit is redeployed. To find out which Data 360 components are packageable, see [Data 360 Extensibility Readiness Matrix](https://developer.salesforce.com/docs/atlas.en-us.c360a_api.meta/c360a_api/c360a_api_isv_readiness_data.htm). For Data 360 components that aren’t available in data kits, you can add them to a package. To find out which components are available in packages, see [Metadata Components for Data 360 Cheat Sheet](https://developer.salesforce.com/docs/data/data-cloud-dev/guide/component-cheatsheet.html). Also, check the [Metadata Coverage Report](https://developer.salesforce.com/docs/metadata-coverage). **See Also** * _Trailhead_: [Packaging and Data Kits in Data Cloud](https://trailhead.salesforce.com/content/learn/modules/packaging-and-data-kits-in-salesforce-cdp) * _Help_: [Build and Share Data 360 Functionality](https://help.salesforce.com/s/articleView?id=data.c360_a_build_and_share_functionality.htm&type=5) * _Help_: [Packaging in Data Cloud](https://help.salesforce.com/s/articleView?id=data.c360_a_packaging_in_customer_360_audiences.htm&type=5) --- You are reading one file. The same content is free over MCP at https://cuppy.io/mcp with no signup: ranked search across all 376 documents in this hub, the merged view when you work in a layer, known workarounds matched to the error you hit, and depth control so you spend tokens on what you need. Start with the `_hello` tool. How to connect: https://cuppy.io/salesforce/ Something wrong in this document? Report it with the `session feedback` tool on the same endpoint.