The architect is planning a large data migration for Universal Containers from their legacy CRM system to Salesforce. What three things should the architect consider to optimize performance of the data migration? Choose 3 answers
A.
Review the time zones of the User loading the data.
B.
Remove custom indexes on the data being loaded.
C.
Determine if the legacy system is still in use.
D.
Defer sharing calculations of the Salesforce Org.
E.
Deactivate approval processes and workflow rules.
A.
Review the time zones of the User loading the data.
D.
Defer sharing calculations of the Salesforce Org.
E.
Deactivate approval processes and workflow rules.
Explanation
Time zones (A) impact batch scheduling; off-peak hours reduce contention with live users.
Deferring sharing (D) pauses recalculations of sharing rules during migration, freeing processing power.
Deactivating automations (E) prevents triggers, workflows, and approvals from firing, slashing transaction time.
Why not others?
B (Remove indexes): Incorrect – indexes speed up data loads by improving query performance; removing them slows migration.
C (Legacy system use): Irrelevant to Salesforce-side optimization.
Performance hinges on minimizing governor limit consumption. Automations and sharing recalculations consume CPU time and delay commits. Migrating during low-activity windows (guided by user time zones) avoids resource contention. Post-migration, reactivate automations and recalculate sharing. This trio ensures efficient resource use and avoids timeouts during large-volume operations.