If the import flags a possible duplicate
Select "Existing Users" at the first import step. Admissions+ then checks each row in your file against your existing student records.
When a row's name is close to an existing student's name, but another field does not agree, Admissions+ shows a "Potential mismatched students!" banner on the Import Summary step.
This can flag two different children, for example two siblings with a similar first name. The import matches each row to an existing student by the identifier you mapped, such as email or Unique Pupil Number, not by name. A blank, wrong, or duplicated identifier in your file makes the import match the row to the wrong student, and it then flags the mismatch because the name, gender, or date of birth does not agree.
Click "Resolve" next to a flagged row. This opens the "Resolve Potential Mismatch" window, which shows the Admissions+ record next to your file's row, with each field that does not agree marked in red.
- Select "This is the same person" only when the two records are the same child. Admissions+ overwrites the existing record with the data from your file.
- Select "These are different individuals" when the row belongs to a different child. Admissions+ does not import that row, so the existing student's record stays as it is.
Do not use "These are different individuals" to fix two siblings flagged as one person: this skips the second child's row completely. Instead, correct that child's identifier in your CSV file so it is unique to them, then import the file again.
Keep school history out of the Arbor export
The "School History" step on the application form collects this data from the parent. Collecting it here does not by itself send it to Arbor.
Admissions+ sends data to Arbor through a separate export. Go to Data, then Export, and start an export with "My School MIS" as the source.
On the Data Mapping step, find the "SCHOOL MAPPING" card. Its "Details" section lists the school-history fields: La Code, Establishment Number, Educational Institution Name, Start Date, End Date, and Leaving Reason.
Untick the fields you do not want to send to Arbor. Admissions+ still collects that data on the application form; unticking a field only stops it going into this export.
