Trial loads, validation and reconciliation of migrated data
Key Takeaway
Before each full load, load one record and check it. After loading, confirm the results with custom reports of record counts, spot checks, and exception reports. If the org has fewer records than the source, use exception reports to find what did not migrate, then re-migrate or update those records.
Moving client, household, and financial account data into Agentforce Financial Services works best as a series of small, checked loads rather than one big push. You prepare clean data and load objects in an order that respects their relationships. You test each file with a single record first. After the loads, you validate the migration and reconcile any gaps, so the right records arrive and stay linked to each other.
How to prepare the data before loading
Validation starts before anything is loaded, because problems are cheaper to fix in a file than in the org.
- Choose which data to migrate. You may not need the whole set.
- Build one template per object.
- Mark the required fields in each template, including fields that business rules need and legacy ID fields.
- Clean the data before it goes into the templates.
- Review the templates after you fill them in.
Store each record's legacy ID in a custom field. You can give that field the "External ID" attribute so the field is indexed. Stored legacy IDs help keep relationships intact. They also let you build custom reports that validate the migration.