Northern Trail Outfitters is migrating to Salesforce from a legacy CRM system that identifies the agent relationships in a look-up table.
What should the data architect do in order to migrate the data to Salesforce?
Northern Trail Outfitters is migrating to Salesforce from a legacy CRM system that identifies the agent relationships in a look-up table.
What should the data architect do in order to migrate the data to Salesforce?
When migrating data to Salesforce, each record must have an owner. The record owner can be a user or a queue, and this is crucial for maintaining data integrity and adhering to Salesforce's data model. Assigning record owners based on existing relationships in the legacy CRM system helps preserve the integrity and usage of data within the new Salesforce environment, ensuring that the relationships and responsibilities are accurately reflected.
Standard Salesforce behaviour is based on record owner. So the migrated data should used that feature. => D.
It's either C or D - the question leaves room for abiguity. If the relationships are one to many, then a custom object would be appropriate and C would be the right answer. If the relationships are 1-1, then D is the right answer.
The most accurate answer is D. Assign record owners based on relationship. In Salesforce, every record must have an owner. The owner can be a user or a queue. When migrating data from a legacy CRM to Salesforce, it’s important to maintain the relationships between records. Therefore, assigning record owners based on the relationships identified in the look-up table from the legacy CRM system would be the most appropriate approach. C. Create custom object to store agent relationships: While creating a custom object to store agent relationships is possible, it’s not necessary. Salesforce has standard objects that can handle relationships, and it’s generally best to use these whenever possible. Furthermore, this option does not address the issue of record ownership.
one custom object (junction table), that should represent relationship between the agents -> C