Instead of mapping parent records by searching for the source record's ID in the destination org, you can use a common external ID field that exists in both orgs. This approach requires adding an extra field in the Object Field Mapping (OFM) Custom Setting to store the API name of the external ID field from the source org. During migration, if this external ID field is configured and populated, the system will use its value to locate and map the parent record in the destination org. If the field is left blank, the system will fall back to using the source record ID, as it currently does.
Follow these steps to use this option:
1. Go to the "About Mass File Migrate" tab.
2. Click on the Mapping URL, i.e., Map parent records from Source to Destination org
3. Click the "New" button.
4. Fill in the following values:
Select Source Object: The object you want to use for file migration.
Destination Object API Name: The object in the destination org where you want to migrate the file.
Destination Object External Id Field API Name - Enter the Field API name of the field in the destination org, which holds the Id of the records that are present in the Source org, OR the common External Id between Source and Destination org.
Source Object External Id Field API Name: This field must be used when the migration is based on common External Ids between the Source and Destination orgs. Enter the Field API name of the field in the source org that holds the External Id. If the value of this field is found empty, the ID of the record will be used for searching the parent record in the destination org.
Then, click the Save button.
5. Here, check the example:
The Source org record has this field and value: MFMSource Data ---> TestField1
The Destination org record has the same field and value: MFMSource Data ----> TestField1
6. Go to the "Mass File Migrate" tab, select the object, click the Search button, and then proceed with the migration.
7. Now you will see the file migrated successfully, and the destination org's record name will appear in the last column. This confirms the migration was done using the common external ID field values that match in both orgs.
