You must run batch jobs or use a data loader to import Salesforce records into
Customer 360 for Salesforce
.
Customer 360 for Salesforce
creates a bean when you first synchronize and import a record into
Customer 360 for Salesforce
.
When you import records,
Customer 360 for Salesforce
performs the following tasks:
Creates beans, if you flag objects for synchronization.
If you do not flag objects for synchronization, the migrate batch job creates beans for those objects.
Normalizes the data for certain fields to ensure that the data adheres to the standard formats.
Normalized data ensures that the data is consistent among the beans for certain fields to reduce the chance for the duplication of data and to improve the quality of matching results.
Customer 360 for Salesforce
standardizes fields, such as country code, legal form, and domain name.
Creates the fuzzy segment and the external ID.
The fuzzy segment is a key that
Customer 360 for Salesforce
uses as a first step to identify matches. The external ID associates a bean with a source record.
Searches for potential duplicates.
If you decide that the record is a duplicate,
Customer 360 for Salesforce
does not create a bean and the process ends. If
Customer 360 for Salesforce
does not identify any potential duplicates or the user indicates that the potential duplicates are not duplicates,
Customer 360 for Salesforce
creates the bean.
Sends the normalized data from the bean back to the
Customer 360 for Salesforce
Salesforce record.
Creates a master bean.
For an account bean,
Customer 360 for Salesforce
makes a clone of the account bean to create the master bean and adds the bean to the related list of the master bean to link the bean to the master bean. For a contact or a lead bean, the matching batch job matches the bean to a master bean.
Customer 360 for Salesforce
adds the bean to the related list of the master bean to link the bean to the master bean and the associated account bean.