Migrating Data from ERP System to Salesforce: Best Practices

How to Organize Data Using Unique ID in Salesforce

Question

Cloud Kicks (CK) wants to migrate data from its existing enterprise resource planning (ERP) system to Salesforce. CK wants to organize its data using the unique ID that is a number type in the ERP.

What should the consultant recommend to meet the requirement?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

C

To meet the requirement of organizing data using the unique ID from the existing ERP system in Salesforce, the consultant should recommend the following option:

C. Map the ERP unique ID to a custom external ID unique number field.

Here's a detailed explanation of why this option is the most suitable:

  1. Use the ERP unique ID as the Salesforce ID (Option A): This option suggests using the ERP unique ID as the Salesforce ID. However, Salesforce IDs are alphanumeric and auto-generated by the system, typically in the form of a 15- or 18-character ID. It is not possible to directly use a number type field from the ERP system as a Salesforce ID.

  2. Create an external ID unique number field in the ERP labeled 'ERP unique ID' (Option B): This option recommends creating an external ID unique number field in the ERP system. While this can be useful for maintaining a link between the ERP system and Salesforce, it does not directly address the requirement of organizing data using the ERP unique ID within Salesforce.

  3. Map the ERP unique ID to a custom external ID unique number field (Option C): This is the most appropriate option to meet the requirement. By mapping the ERP unique ID to a custom external ID unique number field in Salesforce, you can ensure that the unique ID from the ERP system is preserved and can be used as a reference for data organization. Custom external ID fields in Salesforce are designed to hold unique identifiers from external systems and can be indexed for efficient data retrieval.

  4. Create a text field and insert the ERP unique ID (Option D): Creating a text field and inserting the ERP unique ID is not the best approach in this scenario. While it allows storing the unique ID, it doesn't provide the advantages of using a custom external ID field. Using a number type field to store the unique ID as text might also lead to data inconsistencies and potential issues when performing numeric operations or sorting.

Therefore, the recommended option is C. Map the ERP unique ID to a custom external ID unique number field. This approach ensures the preservation of the unique ID from the ERP system and provides a suitable field type for data organization and efficient retrieval within Salesforce.