Northern Trail outfitters in 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 Salesfoce?
A.
Create custom objects to store agent relationships.
B.
Migrate to Salesforce without a record owner.
C.
Assign record owner based on relationship.
D.
Migrate the data and assign to a non-person system user.
A.
Create custom objects to store agent relationships.
Explanation
Salesforce lacks a native "relationship table." Custom objects replicate the legacy lookup table, preserving relationships via junction objects (e.g., Agent__c ↔ Account). Assigning owners (Option C) or using system users (Option D) loses relationship context, collapsing hierarchical data into flat ownership. Migrating without owners (Option B) violates data integrity. Custom objects enable:
Relationship tracking (e.g., Agent X → Account Y).
Historical reporting on agent performance.
Scalable role-based access.
Post-migration, use Lightning Connect or data validation rules to sync relationships. This maintains the legacy structure in Salesforce, ensuring accurate reporting and access control. System users should only own records if agents aren’t Salesforce users.