When migrating data to Salesforce, how can an Architect retain the original created date from the legacy system?

The correct choice is to enable "Set Audit Fields" permission for the user during migration. This option allows the Salesforce user performing the data migration to directly set certain audit fields, such as the Created Date and Last Modified Date, to specific values instead of relying on the default system timestamp. In Salesforce, audit fields are automatically managed by the system; however, by granting this permission, you can retain critical historical information from your legacy system.

Enabling "Set Audit Fields" is particularly useful in scenarios involving data migration, as it not only ensures that the historical context surrounding records is preserved but also helps maintain data integrity and relevance within the Salesforce environment. This method is efficient and straightforward, as it does not require complex workarounds or custom development.

The other options, while they may seem viable, introduce additional steps or complications. For example, updating records post-migration can lead to additional processing and potential for data inconsistencies. Creating a new field can capture the original created date, but it would result in a loss of the native functionality tied to the standard Created Date field. Writing an Apex trigger may be an advanced solution but could complicate the migration process and introduce potential errors or performance issues.

In summary, enabling "Set Audit Fields" permission