Salesforce Education Cloud: "InvalidBatch field name not found IndividualApplicationId" when loading Person Education during EDA to Education Cloud migration

Follow these steps to correct the field mapping and prepare your org so the Person Education load succeeds.

Cause 1: The field API name in your mapping does not match the target object.
1. In your target Education Cloud org, go to Setup > Object Manager > Person Education [PersonEducation] > Fields & Relationships.
2. Use the Quick Find box to search for the field your migration references (for example, IndividualApplicationId).
3. Confirm the exact API name of the lookup or field that relates Person Education to the Individual Application [IndividualApplication] object. Standard field API names commonly end in [__c] for custom fields or use the relationship name without an "Id" suffix in the Data Loader mapping.
4. Open your Data Loader field mapping (.sdl) file or the mapping dialog, and change the target column from IndividualApplicationId to the exact API name shown in step 3.
5. Save the mapping and re-run the load.

Cause 2: The required custom fields were not created on Education Cloud objects before the load.
1. Go to Setup > Object Manager > Person Education [PersonEducation] > Fields & Relationships and verify every field your migration writes to exists. If any target field is missing, create it manually with the same API name and data type as your mapping expects.
2. Follow the documented prerequisite: add the required custom fields on the case participant, care plan, service appointment, and related Education Cloud objects before you migrate data. See the Salesforce Help article "Prerequisites for Data Migration Within Your Org".
3. If you migrate custom fields, review your Data Processing Engine definitions: go to Setup > Data Processing Engine, open each relevant definition, and edit the data transformation operations to include the custom fields you are migrating.
4. Confirm the required picklist values exist on the target fields before loading. See the Salesforce Help article "Add Picklist Values to Education Cloud Fields".

Cause 3: The lookup target record does not yet exist, so the reference cannot resolve.
1. Load the parent Individual Application [IndividualApplication] records into the target org first.
2. Retain the source-to-target ID cross-reference from the Individual Application load results.
3. In your Person Education transform, replace source IDs with the new target Individual Application record IDs, then load Person Education last.

Confirm the issue is resolved by re-running the Data Loader insert for a small batch of Person Education records and verifying the batch completes with zero errors and that each loaded Person Education record shows the correct related Individual Application in Setup > Object Manager > Person Education record view.