---
schema_version: "1"
id: 8ba35695a34146469b071090e6dde91b244c92abf0bbb86712873d8213829add
title: Replicate Metadata Across Data Spaces Using Local Data Kit Deployment
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_data_space_replicate_metadata.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_data_space_replicate_metadata.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: a71e7aa0cbceac2261711f240e222b3e28e290f6f43e0675270a90d6b40948f7
description: Use a local data kit deployment to replicate Data Cloud metadata and process definitions across multiple data spaces within the same sandbox org. Packaging configurations into a local data kit reduces manual effort, ensures consistency, and accelerates time to value when your data space strategy requires standardized definitions across different spaces. Standardization is especially important for deployments across geographies or brands where processes are defined centrally.
products:
  - Data 360
release: "264"
---
# Replicate Metadata Across Data Spaces Using Local Data Kit Deployment

Use a local data kit deployment to replicate Data Cloud metadata and process definitions across multiple data spaces within the same sandbox org. Packaging configurations into a local data kit reduces manual effort, ensures consistency, and accelerates time to value when your data space strategy requires standardized definitions across different spaces. Standardization is especially important for deployments across geographies or brands where processes are defined centrally.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>All Editions</strong> supported by Data 360. See <a href="https://help.salesforce.com/s/articleView?id=data.c360_a_dc_editions.htm&amp;language=en_US" target="_blank">Data 360 edition availability</a>.</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available with add-on license: <strong>Data Spaces</strong></td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:left;vertical-align:top;" id="d96713e71">Permission Sets Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Permission Sets Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d96713e71 ">To access Data Cloud Setup</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d96713e71 ">
              <p>System admin profile OR </p>
              <p style="margin-bottom:0;">Data Cloud Architect permission set</p>
            </td>

          </tr>
        </tbody>
      </table>

Previously, replicating configurations such as calculated insights and segments required manual re-creation in each data space, which was time-consuming and prone to error. With local data kit deployment, Data 360 performs a pure upsert, automatically updating existing components or creating new ones with the appropriate data space prefix.

- Verify that you're working in a Data 360 sandbox environment.
- Log in to the default data space.
- Make sure that your metadata and process definitions are finalized in the default data space.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_note.png)

Note Local data kit deployment supports standard data kits only. To move changes from sandbox to production, use a DevOps data kit.

These high-level steps replicate metadata and promote it to production:

1. Create your data model objects (DMO) mappings, calculated insights, and segments in the default data space of your sandbox.
2. Package your finalized configurations into a standard local data kit.
3. Use the one-click deployment for each target data space within the sandbox.
4. Add the necessary filters to the data lake objects (DLO) mapped into each of the target data spaces.
5. Create a DevOps data kit for each data space to deploy the configurations to your production environment.

#### See Also

- [_Salesforce Help_: Replicate Data 360 Configurations Using Local Data Kits](https://help.salesforce.com/s/articleView?id=data.c360_a_replicate_data360_configurations_using_local_data_kits.htm&language=en_US)