Agentforce Financial Services Data Loader upload sequence
Key Takeaway
Load parent records before the records that point to them, so each parent's new Salesforce record ID exists when you load its children.
When you bulk load legacy client data into Agentforce Financial Services with Data Loader, Salesforce recommends loading objects in a set order. Parent records go in first, so their new Salesforce record IDs exist before you load the child records that point to them. Following the order keeps each record linked to the right client, household, or financial account.
The recommended load order
Salesforce recommends this order for individual, group, and financial account data:
- Individuals
- Identification documents
- Employment
- Education
- Relationship groups, such as households
- Individuals' relationships to groups
- Charges and Fees
- Financial accounts
- Cards
- Billing statements
- Financial account transactions
- Securities
- Financial Holdings
After those, load the remaining objects in any order.
The order follows the lookups. A child record points to its parent through a lookup field that holds the parent's Salesforce record ID, so the parent has to be loaded first.