Syncing Salesforce with Legacy Database: A Consultant's Recommendation

C

To meet the requirement of searching and cross-referencing records with the original source database in Salesforce, the Consultant should recommend using a custom External ID field and mapping it to the original record ID value. Therefore, the correct answer is option C: Use a custom External ID field and map this to the original record ID value.

Here's a detailed explanation for this recommendation:

1. External ID field: An External ID field in Salesforce is a custom field that allows you to store an identifier from an external system. It is typically used for integration purposes, enabling you to link records in Salesforce with corresponding records in an external system.

2. Custom field: Since Cloud Kicks wants to cross-reference records with the original source database, a custom field should be created specifically for this purpose. A custom field gives you the flexibility to define and configure the field according to your organization's requirements.

3. Mapping to the original record ID value: When migrating 70 million records from a legacy database to the data warehouse, each record will have its own unique identifier in the original source database. To enable cross-referencing, the Consultant should recommend mapping the custom External ID field in Salesforce to the original record ID value from the legacy database. This mapping will establish a relationship between the records in Salesforce and their counterparts in the original source database.

By using a custom External ID field mapped to the original record ID value, Cloud Kicks will have the ability to search and cross-reference records with the legacy database. This ensures that the sales team can access and compare information between Salesforce and the original source database, facilitating their sales automation processes effectively.