---
schema_version: "1"
id: 8298a46d7754ce3e61c8add9ad432d2d6083a9ae9bfce48c1a3517cc9e547fe7
title: Data Cleansing and Preparation
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_cleansing_data.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_cleansing_data.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 5c0b6e0ff5ae937f7cf5ddef13da2f9ae97b96610850b0bfdd280515e5f0f843
description: Cleaning and preparing your data is crucial for success when using the Data 360 segmentation and activation capabilities.
products:
  - Data 360
release: "264"
---
# Data Cleansing and Preparation

Cleaning and preparing your data is crucial for success when using the Data 360 segmentation and activation capabilities.

### 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: Lightning Experience</td></tr></tbody></table>

After ingesting your data into Data 360, use the library functions, operators, and raw data fields to prepare for data mapping.

- **[Streaming Data Transforms](https://help.salesforce.com/s/articleView?id=data.c360_a_streaming_transform_overview.htm&release=264.0.0&type=5)**  
    A streaming data transform reads one record in a source object, reshapes the record data, and writes one or more records to a target object. The source and target objects must be different objects. A streaming data transform runs continuously as a streaming process, picking up new or changed data.
- **[Batch Data Transforms](https://help.salesforce.com/s/articleView?id=data.c360_a_batch_transform_overview.htm&release=264.0.0&type=5)**  
    To transform your data for further usage, such as identity resolution, segmentation, or calculated insights, or to derive insights in Salesforce reports, use a batch data transform. A batch transform is a repeatable series of operations that you can run when data updates. The first time you run a batch data transform, it pulls in data and defines it according to your steps. You can then run a transform manually or set it up to run at scheduled intervals.
- **[Billing Considerations for Data Transforms](https://help.salesforce.com/s/articleView?id=data.c360_a_billing_considerations_for_data_transforms.htm&release=264.0.0&type=5)**  
    Data Transforms use Data 360 to cleanse, enrich, and reshape data from DLOs and DMOs to prepare it for insights, segmentation, and AI features. Use of Data Transforms impacts the consumption of credits in these usage types.
- **[Create a Data Transform Platform Event Flow](https://help.salesforce.com/s/articleView?id=data.c360_a_transform_platform_event_flow.htm&release=264.0.0&type=5)**  
    Create a platform-triggered flow for data transform event actions.
- **[Create a Data Transform Record Event Flow](https://help.salesforce.com/s/articleView?id=data.c360_a_transform_record_event_flow.htm&release=264.0.0&type=5)**  
    Create a record-triggered flow for data transform event actions. With a record-triggered flow, you can update another record, send a notification, or initiate a process.
- **[Normalized and Denormalized Data](https://help.salesforce.com/s/articleView?id=data.c360_a_normalized_and_denormalized_data.htm&release=264.0.0&type=5)**  
    Data originates from multiple sources and can be normalized or denormalized. The Data 360 standard data model is normalized, so incoming data must be normalized before it can be mapped to the data model. Because not all source systems provide normalized export options or normalize data, assess your field-level data to establish how to transform and map the source data to the standard data model.
- **[Normalize Denormalized Data Use Case](https://help.salesforce.com/s/articleView?id=data.c360_a_uc_normalize_denormalized_data_from_marketing_cloud.htm&release=264.0.0&type=5)**  
    In this use case, the data comes from a single Marketing Cloud Engagement data extension but must be normalized to map to the Data 360 data model objects (DMO).