You can use the predefined egress jobs to export master data from the Organization and Person business entities of Customer 360 SaaS to Data 360.
Each egress job uses a taskflow to run mapping tasks. Each mapping task includes a mapping that maps the Customer 360 SaaS business entity fields to the Data 360 data lake object (DLO) fields. The job uses Business 360 FEP Connector to read data from Customer 360 SaaS and Salesforce Data 360 Connector to write data to Data 360. The egress jobs use predefined Data Integration assets, such as mappings, mapping tasks, and taskflows, to publish the master records and their relationships to data streams in Data 360.
After you deploy the preconfigured data kit, run predefined egress jobs. The Salesforce Ingestion API ingests the master data from data streams into Data 360 DLOs. The preconfigured field mappings automatically populate the master data into Data 360 data model objects (DMOs). When you run the identity resolution rulesets, the unified profiles in Data 360 are enriched with master data from Customer 360 SaaS.
The following image shows how master data is published from Customer 360 SaaS to Data 360 using MDM Extension for Data 360:
