NTO has outgrown its current salesforce org and will be migrating to new org shortly. As part of this process NTO will be migrating all of its metadata and data. NTO’s data model in the source org has a complex relationship hierarchy with several master detail and lookup relationships across objects, which should be maintained in target org. What 3 things should a data architect do to maintain the relationship hierarchy during migration? Choose 3 answers:
A.
Use data loader to export the data from source org and then import or Upsert into the target org in sequential order.
B.
Create a external id field for each object in the target org and map source record ID’s to this field.
C.
Redefine the master detail relationship fields to lookup relationship fields in the target org.
D.
Replace source record ID’s with new record ID’s from the target org in the import file.
E.
Keep the relationship fields populated with the source record ID’s in the import file.
A.
Use data loader to export the data from source org and then import or Upsert into the target org in sequential order.
B.
Create a external id field for each object in the target org and map source record ID’s to this field.
D.
Replace source record ID’s with new record ID’s from the target org in the import file.
Explanation:
A: Data Loader sequential imports preserve hierarchical relationships.
B: External IDs maintain referential integrity through unique identifiers, facilitating accurate relationship mapping.
D: Replacing IDs in import files ensures relational integrity in target org.
Option C (changing relationship types) unnecessarily alters the data model structure.
Option E (keeping source IDs) will break relationships since Salesforce assigns new IDs during migration.