You are here:
Update Your Data Configuration
To help you unify your data, we provide a CSV file that lists the processes in your org that need to be updated. Generate the CSV file, update your data mapping, then use the file to make the necessary changes.
Required Editions
| Available in: Marketing Cloud Engagement Pro+, Corporate+, and Enterprise+ Editions |
| User Permissions Needed | |
|---|---|
| To generate the CSV file: | A Salesforce account with the Marketing Admin permission set. |
| To update the data mapping: | A Salesforce account with the Marketing Admin permission set. |
| To manually update the data configuration: | A Salesforce account with the Marketing Admin and Data Cloud Architect permission set. |
- Log in to Salesforce.
- In Salesforce Setup, go to Marketing Cloud | Marketing Features | Marketing Cloud Engagement | Unify Data. If you don’t see the Unify Data page, your Engagement data is compatible with Marketing Cloud Next and you don’t need to complete these steps.
-
Click Generate Download Link and then click
Generate to confirm.
The amount of time the process takes to complete depends on the amount of data in your org. When the download link is ready, it appears on the page. We also send a copy of the CSV file to the email address associated with your user profile. If you have an existing download link, this action replaces it.
-
Update your field mapping.
This one-time process maps new Data Lake Object (DLO) fields to the Data Model Object (DMO) to support the unified data model.
- In the Update Field Mapping section, click Update Mapping.
- In the confirmation modal, click Update to confirm.
-
Use the generated CSV file to manually update your data processes.
The file includes a list of processes with conflicting values. To resolve conflicts, go to the process definitions listed in the CSV file and update the data configuration so that both the legacy and unified values are valid. For example, in the legacy data model, the unsubscribe DMO value is named Opt Out. In the unified data model, the unsubscribe DMO value is named UNSUBSCRIBE. To fix this, change the value to “Opt Out OR UNSUBSCRIBE.” For a complete list of naming differences, see Event Detection in the Marketing Cloud Engagement Data Model: Key Differences with Marketing on Cloud.
Now you’re ready to configure your incoming and existing data so that it’s compatible with Marketing Cloud Next features.
Did this article solve your issue?
Let us know so we can improve!

