Cloud Kicks (CK) is migrating Account and Contact information from a legacy CRM system into Salesforce using Data Loader. Accounts in the legacy system have a unique ID held that is used to relate Contacts to Accounts in the legacy system. CK wants to automatically match these Contacts to the relevant Accounts when loading the Contacts into Salesforce.
What should a consultant recommend to meet the requirement?
Click on the arrows to vote for the correct answer
A. B. C. D.D
To automatically match Contacts to the relevant Accounts during the data migration process from a legacy CRM system to Salesforce, the recommended approach is to create an External ID on the Contact object. Therefore, the correct answer is option A: Create External ID on Contact.
Here's a detailed explanation of why this is the recommended solution:
External IDs: An External ID is a field in Salesforce that holds a unique identifier from an external system. It allows you to match records in Salesforce with corresponding records in an external system using a common identifier. In this case, the unique ID held in the legacy CRM system can serve as the External ID.
Contact-Account Relationship: In Salesforce, the relationship between Contacts and Accounts is typically established through a lookup or master-detail relationship. However, creating a Master-Detail relationship between Contact and Account (option B) or Account and Contact (option C) is not suitable for this scenario because it implies a hierarchical relationship, where the child record (Contact) depends on the parent record (Account). The legacy CRM system's unique ID is used to relate Contacts to Accounts, which suggests a one-to-one or one-to-many relationship rather than a hierarchical one.
Account External ID: Creating an External ID on the Account object (option D) is not the recommended solution because it does not address the specific requirement of matching Contacts to Accounts using the unique ID from the legacy system. While an External ID on Account can be helpful for various integration scenarios, it does not directly facilitate the automatic matching of Contacts during the data loading process.
Contact External ID: By creating an External ID on the Contact object (option A), you can map the legacy system's unique ID to the External ID field on the Contact records being loaded into Salesforce. During the data loading process using Data Loader or any other integration tool, you can leverage this External ID to perform an upsert operation, which will automatically match Contacts with their respective Accounts based on the unique ID. The External ID acts as a cross-reference between the legacy system's ID and the corresponding Contact record in Salesforce.
In summary, creating an External ID on the Contact object enables you to automatically match Contacts to their relevant Accounts during the data migration process, ensuring accurate and efficient data import from the legacy CRM system into Salesforce.