Load sequencing for provider, facility, and clinical record relationships
Key Takeaway
Load records that others reference, such as providers and facilities, before the records that point to them. The target org assigns new record IDs, so store source record IDs in a custom External ID field and relate child records through it.
Moving data into Agentforce Health means loading records in an order that lets each record point to the records it depends on. Provider and facility records form the base. Clinical encounter records build on both patient and provider records, so a migration strategy has to sequence provider, facility, and clinical data together.
Why load order matters
Salesforce keeps record relationships through unique record IDs, not record names. The target org gives every imported record a new ID, so the source record IDs in your import files must be replaced with the new IDs.
A parent record is a record that others reference, and a child record is a record that points to it. The parent loads first because its new ID does not exist until the target org creates it. The new ID then goes into the child file before that file loads. For example, after Accounts are imported, the new Account IDs replace the source Account IDs in the Contact, Opportunity, and Case files before those files load.