---
schema_version: "1"
id: 6587a9daa37e3d7d0cb2bb7de31a14ee1fd4d056d4459b940f1b07aa7596a134
title: Synchronize Data Extensions with Marketing Cloud Next
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mke_data_ext_sync.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mke_data_ext_sync.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 8dbc369aeb0e32c4ea2791d15a1412d23c894dd907ab7a71566bf41305069dcb
description: Synchronize your data extensions with Marketing Cloud Next on a schedule that you define. When you synchronize a data extension, your team can continue to use any integrations that rely on data extensions in Marketing Cloud Engagement. At the same time, you can start using that data to create campaigns, segments, and flows in Marketing Cloud Next.
products:
  - Marketing
  - Marketing Cloud Engagement
release: "264"
---
# Synchronize Data Extensions with Marketing Cloud Next

Synchronize your data extensions with Marketing Cloud Next on a schedule that you define. When you synchronize a data extension, your team can continue to use any integrations that rely on data extensions in Marketing Cloud Engagement. At the same time, you can start using that data to create campaigns, segments, and flows in Marketing Cloud Next.

### 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: Marketing Cloud Engagement <strong>Pro+</strong>, <strong>Corporate+</strong>, and <strong>Enterprise+</strong> Editions</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="d67541e77">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d67541e77 ">To sync data extensions, create Data 360 Objects, and map fields:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d67541e77 ">Data Cloud Architect</td>

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

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_marketing_cloud_overview-264-0-0-production-enus/2555afdb-8049-4e3c-8043-0e04803e5f16/images/icon_note.png)

Note There’s no additional cost for bringing the data from your data extensions into Marketing Cloud Next. For more information, see _Knowledge Article_: [Data 360 Zero Cost Data Ingestion from Internal Clouds](https://help.salesforce.com/s/articleView?id=005132106&type=1&language=en_US) and the [Salesforce Customer Data Cloud Rate Card](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/platform/data-cloud-platform-services-rate-sheet.pdf) (PDF).

## Create a Data Stream for Data Extension Data

In Data 360, a data stream is a connection to a data source. Each data stream has its own refresh schedule in which it pulls the latest data from the connected data source. Use data streams to synchronize Data 360 with data from your data extensions.

When you create a data stream, Data 360 stores the data from your data extension in a raw storage layer called a data lake object (DLO). However, the data isn’t available widely throughout Data 360 until you [map the fields](https://help.salesforce.com/s/articleView?id=mktg.mke_data_ext_sync.htm&release=264.0.0&type=5 "After you create a data stream that syncs data from a data extension, create a data model object (DMO) in Data 360 and map the fields from the data extension to fields in the DMO.") to a data model object (DMO). A DMO is the business layer that marketers interact with. To learn more about data objects, see _Salesforce Help_: [Data Objects in Data 360](https://help.salesforce.com/s/articleView?id=data.c360_a_data_lake_objects.htm&language=en_US).

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_marketing_cloud_overview-264-0-0-production-enus/2555afdb-8049-4e3c-8043-0e04803e5f16/images/icon_note.png)

Note You can select only one data extension at a time when you create a data stream. To connect multiple data extensions, complete these steps for each data extension.

Prioritize creating data streams for your most important data extensions, such as those used within the Contact Model.

1. Log in to Salesforce.
2. On the app launcher (![Nine dots arranged in a square shape](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_marketing_cloud_overview-264-0-0-production-enus/2555afdb-8049-4e3c-8043-0e04803e5f16/mc_marketing_cloud_overview/images/app_launcher.png)), search for data streams, and then select **Data Streams**.
3. On the Data Streams tab, click **New**.
4. Under Connected Sources, select **Marketing Cloud**.
5. Click **Next**.
6. Review the mappings of business units to data spaces.
    
    These mappings don’t automatically apply when you sync a data extension. In a later step, you specify which data space can access the data from the data extension.
7. Click **Next**.
8. On the Data Extensions tab, select the business unit that contains the data extension, as shown in this image.
    
    ![The New Data Stream window with labels indicating that you navigate to the Data Extensions tab first, and then select a business unit from the dropdown.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_marketing_cloud_overview-264-0-0-production-enus/2555afdb-8049-4e3c-8043-0e04803e5f16/mc_marketing_cloud_overview/images/mke_sync_data_extension/mke_sync_data_extension_data_stream1.png)
9. From the list of data extensions, select the data extension you want to synchronize with Data 360.
    
    The pane on the left lists the data extension folders from Engagement. After you select a folder, the pane on the right lists the data extensions it contains, as shown in this image.
    
    ![A list of data extensions, with data extension folders shown on the left side, and the data extensions that they contain on the right.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_marketing_cloud_overview-264-0-0-production-enus/2555afdb-8049-4e3c-8043-0e04803e5f16/mc_marketing_cloud_overview/images/mke_sync_data_extension/mke_sync_data_extension_data_stream2.png)
10. To apply a custom label to the data extension, change the name in the **Object Label** field. When you update the Object Label, the Object API Name field updates automatically.
    
    ![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_marketing_cloud_overview-264-0-0-production-enus/2555afdb-8049-4e3c-8043-0e04803e5f16/images/icon_tip.png)
    
    Tip It’s helpful to add a prefix such as MCE\_ to make the data extension object easier to identify.
11. Click **Next**.
12. Under Object Details, for Category, select a category that aligns with the data in the selected data extension.
    - **Profile**—Data related to an individual, account, or other type of profile. This type of data can include demographic data (such as name, age, or location), psychographic data (such as hobbies, interests, or preferences), or aggregate information (such as lifetime value or loyalty tier).
    - **Engagement**—Time-series oriented data related to events, such as previous purchases or interactions with a web page.
    - **Other**: Any other type of data, such as reference data.
13. For Primary Key, select the primary key field from the data extension.
14. Click **Next**.
15. Select a data space to sync data into.
    
    After you create the initial synchronization process, you can [sync the data with other data spaces](https://help.salesforce.com/s/articleView?id=mktg.mke_data_ext_sync.htm&release=264.0.0&type=5 "Add the data from a data extension to more than one data space. For example, if you have a primary customer data extension that’s used by multiple business units, you can synchronize it with the data space for each business unit.").
16. To specify the records that are accessible within a data space, define a filter.
    
    A filter defines the criteria for records to include in the data space. Filters don’t restrict which records are imported from the data extension into the DLO. See _Knowledge Article_: [Data 360: Impact of Data Space Filters on Data Stream Counts](https://help.salesforce.com/s/articleView?id=002721752&type=1&language=en_US).
    
    1. Next to Data Space, click **Set Filter**.
    2. Click **Add Filter**.
    3. For Select an Object, select the data extension object.
    4. For Select Column, select the column in the data extension to filter on.
    5. For Select Operator, select the type of operator to use in the filter.
    6. For Value, enter the value to filter on for the selected column.
    7. Click **Add**.
    8. To add more filters, click **Add Filter**, and then define the next filter.
17. Save your changes.
18. For Data Extension Extract Mode, select an option for extracting data from the data.
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_marketing_cloud_overview-264-0-0-production-enus/2555afdb-8049-4e3c-8043-0e04803e5f16/images/icon_note.png)
    
    Note For best performance, use a delta refresh type.
    
    - **Full Refresh**—Pull the complete set of data from the data extension.
    - **Delta Extract by Date**—Pull only the data added after the last refresh. When you select this option, also select a timestamp field from the data extension. When the extract runs, Data 360 sets the most recent value in the selected field as a high-water mark. In the next refresh, Data 360 extracts all records in which the date in the selected field is more recent than the previous high-water mark.
    - **Delta Extract by Number**—Pull only the data added after the last refresh. When you select this option, also select a number field from the data extension. When the extract runs, Data 360 finds the maximum value in the selected field and sets it as a high-water mark. In the next refresh, Data 360 extracts all records in which the number in the selected field is greater than the previous high-water mark.
19. For Refresh Mode, select an option for adding data to the data object.
    - **Upsert**—Update existing records, and create records if existing records aren’t found.
    - **Full Refresh**—Delete all existing data from the data object and insert the extracted data each time the refresh occurs.
20. Click **Deploy**.

## Map Data Extension Fields in Data 360

After you create a data stream that syncs data from a data extension, create a data model object (DMO) in Data 360 and map the fields from the data extension to fields in the DMO.

These steps show how to create a custom data object with fields that are equivalent to the fields from your existing data extension.

1. On the Data Streams page in Data 360, select the data stream that’s connected to the data extension you want to make available throughout Data 360.
2. Under Data Mapping, click **Start**, as shown in this image.
    
    ![Details of a data stream. A button on the page labeled Start is highlighted.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_marketing_cloud_overview-264-0-0-production-enus/2555afdb-8049-4e3c-8043-0e04803e5f16/mc_marketing_cloud_overview/images/mke_sync_data_extension/mke_sync_data_extension_data_mapping1.png)
3. Under Data Model Entities, click **Select Objects**.
4. Create the data model object.
    1. On the Custom Data model tab, click **New Custom Object**, as shown in this image.
        
        ![The Select Objects page, with steps indicating that the user first clicks the Custom Data Model tab, and then clicks the New Custom Object button.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_marketing_cloud_overview-264-0-0-production-enus/2555afdb-8049-4e3c-8043-0e04803e5f16/mc_marketing_cloud_overview/images/mke_sync_data_extension/mke_sync_data_extension_data_mapping2.png)
    2. For each field that marketers use in segments or flows, we recommend that you check the box in the **Enable Value Suggestion** column. This option gives users a preview of values for the selected field when they use the field to create a segment or to configure decisions in a flow.
        
        ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_marketing_cloud_overview-264-0-0-production-enus/2555afdb-8049-4e3c-8043-0e04803e5f16/images/icon_note.png)
        
        Note Up to 500 fields across your entire account can use this feature. We recommend that you only select this option for commonly used string fields that have several possible values. For example, select this option for a field called Loyalty Status that has many different but standardized status options, such as Bronze, Silver, Gold, Platinum, or Diamond.
    3. Save your changes.
        
        Data 360 creates a data object that contains the fields from the original data extension, and automatically maps the data stream to them.
5. To map data extension fields to fields in another object, [map the data extension fields to Data Model Object fields](https://help.salesforce.com/s/articleView?id=mktg.mke_data_ext_sync.htm&release=264.0.0&type=5 "After you create an object for the data in your data extension, optionally map the data to other Data 360 objects. For data extensions that contain profile data, it’s a good idea to get started by joining your data extension to the Individual object.").

## Map Data Extension Fields to Data Model Object Fields

After you create an object for the data in your data extension, optionally map the data to other Data 360 objects. For data extensions that contain profile data, it’s a good idea to get started by joining your data extension to the Individual object.

Depending on your use case and the relationships between your data extension and Data 360, you can also map fields to other objects.

1. On the mapping page for your data source, click the pencil icon next to Data Model entities, as shown in this image.
    
    ![The Data Model entities section of the mapping page. A pencil icon is highlighted, indicating that the user can edit a value.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_marketing_cloud_overview-264-0-0-production-enus/2555afdb-8049-4e3c-8043-0e04803e5f16/mc_marketing_cloud_overview/images/mke_sync_data_extension/mke_sync_data_extension_data_mapping_indv_2.png)
2. On the Select Objects page, under All Objects, search for the name of the object to associate fields with. For example, to associate fields from your data extension with fields from the Individual object, search for individual. Click the plus sign next to Individual, and then click **Done**, as shown in this image.
    
    ![The Select Objects page, with steps indicating that the user first searches for "individual," and then clicks the plus sign next to the Individual object.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_marketing_cloud_overview-264-0-0-production-enus/2555afdb-8049-4e3c-8043-0e04803e5f16/mc_marketing_cloud_overview/images/mke_sync_data_extension/mke_sync_data_extension_data_mapping_indv_1.png)
    
    The mapping view appears. The fields listed on the left side of the page are fields from your data extension, and the fields on the right side are fields from the selected data objects.
3. In the mapping view, under the selected data object, expand the Unmapped section.
4. Click the name of a field from the data extension and then click a field from the data object. For example, if your data extension contains a field called Email that contains customer email addresses, you can map it to the Email Address field in the Contact Point Email object. A line appears between the two fields, indicating that they’re mapped to each other.
    
    This image shows a connection between the ContactKey field in a data extension and the Individual Id field from the Individual object, and a connection between the First Name fields in both objects.
    
    ![The field mapping page. Several lines extend from the fields on the left side of the page and connect to the fields on the right side, indicating that the fields are mapped to each other.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_marketing_cloud_overview-264-0-0-production-enus/2555afdb-8049-4e3c-8043-0e04803e5f16/mc_marketing_cloud_overview/images/mke_sync_data_extension/mke_sync_data_extension_data_mapping_indv_3.png)
    
    ![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_marketing_cloud_overview-264-0-0-production-enus/2555afdb-8049-4e3c-8043-0e04803e5f16/images/icon_tip.png)
    
    Tip It isn’t always correct to map the primary key from the data extension to the primary key in the Standard DMO. For example, if your data extension contains information about customers’ purchase histories, each record in that data extension might have a Purchase ID (which is the primary key used to distinguish records), and a Customer ID. If you join this data extension to the Individual object, map the Customer ID (a non-primary key) in the data extension to the Individual ID (the primary key) in the Individual object.
5. Repeat the preceding step until you’ve mapped all the fields that you want to use from the data extension.
    
    It isn’t necessary to map all the fields from the data extension. However, only mapped fields are available to use in Marketing Cloud Next.
    
    ![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_marketing_cloud_overview-264-0-0-production-enus/2555afdb-8049-4e3c-8043-0e04803e5f16/images/icon_tip.png)
    
    Tip To create a field in a data object, click Add New Field, and then specify a field name and data type for it. After you create a field, you can map data extension data to it.
6. When you finish mapping fields, save your changes.

There are several foundational DMOs to link to your data extensions. For example, if your data extension contains the email addresses of your customers, we recommend that you connect that field to fields in the Contact Point Email DMO. This table lists these objects and the suggested field mappings between object fields and data extension fields.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
          <colgroup>
            <col>
            <col>
            <col>
          </colgroup>
          <thead class="slds-text-title_caps ">
            <tr class="">
              <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d67541e748">Data Extension Field Contents</th>
              <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d67541e751">Data Model Object</th>
              <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d67541e754">Field in DMO to map to</th>
            </tr>
          </thead>
          <tbody>
            <tr class="">
              <td data-label="Data Extension Field Contents" class="slds-cell-wrap" style="vertical-align:top;" headers="d67541e748 ">A primary key for the data extension, such as SubscriberKey or ContactKey</td>

              <td data-label="Data Model Object" class="slds-cell-wrap" style="vertical-align:top;" headers="d67541e751 ">Individual</td>

              <td data-label="Field in DMO to map to" class="slds-cell-wrap" style="vertical-align:top;" headers="d67541e754 ">Individual Id</td>

            </tr>
            <tr class="">
              <td data-label="Data Extension Field Contents" class="slds-cell-wrap" style="vertical-align:top;" headers="d67541e748 ">A primary key for the data extension, such as SubscriberKey or ContactKey</td>

              <td data-label="Data Model Object" class="slds-cell-wrap" rowspan="2" style="vertical-align:top;" headers="d67541e751 ">Contact Point Email</td>

              <td data-label="Field in DMO to map to" class="slds-cell-wrap" style="vertical-align:top;" headers="d67541e754 ">Contact Point Email Id</td>

            </tr>
            <tr class="">
              <td data-label="Data Extension Field Contents" class="slds-cell-wrap" style="vertical-align:top;" headers="d67541e748 ">A field that contains a subscriber’s email address</td>

              <td data-label="Field in DMO to map to" class="slds-cell-wrap" style="vertical-align:top;" headers="d67541e754 ">Email Address</td>

            </tr>
            <tr class="">
              <td data-label="Data Extension Field Contents" class="slds-cell-wrap" style="vertical-align:top;" headers="d67541e748 ">A primary key for the data extension, such as SubscriberKey or ContactKey</td>

              <td data-label="Data Model Object" class="slds-cell-wrap" rowspan="3" style="vertical-align:top;" headers="d67541e751 ">Contact Point SMS</td>

              <td data-label="Field in DMO to map to" class="slds-cell-wrap" style="vertical-align:top;" headers="d67541e754 ">Contact Point Email Id</td>

            </tr>
            <tr class="">
              <td data-label="Data Extension Field Contents" class="slds-cell-wrap" style="vertical-align:top;" headers="d67541e748 ">A field that contains a subscriber’s phone number</td>

              <td data-label="Field in DMO to map to" class="slds-cell-wrap" style="vertical-align:top;" headers="d67541e754 ">Telephone Number</td>

            </tr>
            <tr class="">
              <td data-label="Data Extension Field Contents" class="slds-cell-wrap" style="vertical-align:top;" headers="d67541e748 ">A field that contains a subscriber’s E.164-formatted phone number</td>

              <td data-label="Field in DMO to map to" class="slds-cell-wrap" style="vertical-align:top;" headers="d67541e754 ">Formatted E164 Phone Number</td>

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

As your account grows and you add more data to it, consider creating more mappings between data extensions and standard data objects. For more information about the standard data objects in Data 360, see _Salesforce Help_: [Customer 360 Data Model](https://help.salesforce.com/s/articleView?id=data.c360_a_c360datamodel.htm&language=en_US) and _Salesforce Developers_: [Standard Data Model Objects (DMOs)](https://developer.salesforce.com/docs/data/data-cloud-dmo-mapping/guide/c360dm-datamodelobjects.html).

## Create Data Relationships with DMOs

Establish data relationships between your data extension and standard data model objects. While DMO mapping defines how to structure raw data in data model objects during ingestion, a DMO relationship defines how records connect to each other after ingestion.

Defining data relationships is a foundational step for working with segments and journeys. The process of defining a DMO relationship in Marketing Cloud Next is similar to defining the Contact Model in Engagement. In the Contact Model, you define one-to-one, one-to-many, and many-to-many relationships between data extensions, which define paths for filters and decision splits in Journey Builder. For example, you can associate a customer ID with previous orders in a one-to-many relationship–that is, one customer ID is associated with many orders. A journey can then use this relationship to send customers down a certain path if they’ve placed more than one order.

1. On the app launcher (![Nine dots arranged in a square shape](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_marketing_cloud_overview-264-0-0-production-enus/2555afdb-8049-4e3c-8043-0e04803e5f16/mc_marketing_cloud_overview/images/app_launcher.png)), search for data model, and then select **Data Model**.
2. From the list of data model objects DMOs, select the DMO that contains the data from your data extension.
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_marketing_cloud_overview-264-0-0-production-enus/2555afdb-8049-4e3c-8043-0e04803e5f16/images/icon_note.png)
    
    Note If you don’t see the DMO listed, click the arrow next to Mapped, and then select **All**.
3. On the Relationships tab, click **New**, as shown in this image.
    
    ![The data model object detail page, with steps indicating that the user first clicks the Relationships tab, and then clicks the Add button.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_marketing_cloud_overview-264-0-0-production-enus/2555afdb-8049-4e3c-8043-0e04803e5f16/mc_marketing_cloud_overview/images/mke_sync_data_extension/mke_sync_data_extension_data_relationship1.png)
4. On the Edit Relationships window, click **New Relationship**.
5. Configure the relationship.
    1. For Field, select the primary key field from the data extension. For profile-related data extensions, this value is usually **SubscriberKey** or **ContactKey**.
    2. For Cardinality, select the type of relationship to create. If the data extension contains a field that’s unique for each corresponding record in the related object, select **1:1**. If the data extension contains multiple records that correspond to a single record in the related object, select **Many:1**.
    3. or Related Object, select the object that contains the fields you want to relate to the data extension object.
    4. For Related Field, select the field to relate.
6. Save your changes.

## Synchronize Data to an Additional Data Space

Add the data from a data extension to more than one data space. For example, if you have a primary customer data extension that’s used by multiple business units, you can synchronize it with the data space for each business unit.

1. In Data 360, click the Data Spaces tab.
2. Select the data space that you want to make the data from the data extension available in.
3. Click **Add Data Lake Objects**.
4. Select the data lake object that’s associated with your data extension, and then click **Next**.
5. To specify which records to make available in the data space, define a filter.
    1. Click **Set Filters**.
    2. Click **Add Filter**.
    3. For Select an Object, select the data extension object.
    4. For Select Column, select the column in the data extension to filter on.
    5. For Select Operator, select the type of operator to use in the filter.
    6. For Value, enter the value to filter on for the selected column.
    7. Click **Add**.
    8. To add more filters, click **Add Filter**, and then define the next filter.
    9. Save your changes.
6. On the Data Streams tab, select the stream for your data extension.
7. The Data Mapping section includes the new data space. Next to the name of the new data space, click **Start**.
8. [Map the fields from the data space to fields in the data model entities for the data space](https://help.salesforce.com/s/articleView?id=mktg.mke_data_ext_sync.htm&release=264.0.0&type=5 "After you create an object for the data in your data extension, optionally map the data to other Data 360 objects. For data extensions that contain profile data, it’s a good idea to get started by joining your data extension to the Individual object.").
9. [Configure relationships between the data extension and standard DMOs](https://help.salesforce.com/s/articleView?id=mktg.mke_data_ext_sync.htm&release=264.0.0&type=5 "Establish data relationships between your data extension and standard data model objects. While DMO mapping defines how to structure raw data in data model objects during ingestion, a DMO relationship defines how records connect to each other after ingestion.").