When first working with CSV integration, certain questions may arise that are not immediately obvious.
Our goal is to make CSV uploads as seamless as possible, and we would like to share some key insights that can simplify your experience.
We recommend a structured approach: first, upload accounts (students, parents, and teachers), and then establish connections (relationships and enrollment). It is best to upload your files through the Integration tab.
To maintain data consistency, it is best to use the same files over time, adding new rows at the bottom for any new accounts or connections. If certain accounts need to be removed, simply delete the corresponding rows. This method ensures that existing accounts remain intact, while any accounts not included in the latest upload are automatically moved to archived records.
Local IDs play a crucial role in ensuring data accuracy. Each Local ID should be unique and free from extra symbols or spaces - one Local ID corresponds to one account.
You can always download the latest template from the Integration tab to ensure you are using the most up-to-date format. Even if you do not need all the fields, please leave them empty instead of deleting them. The username and password fields should be always filled in.
If you have previously uploaded an enrollment file, you can easily download it from either the Teacher or Parent Directory at the bottom of the page.
If you plan to use Google Sign-In for teachers, please ensure that the teacher email addresses are associated with Google accounts before uploading the files.
Local IDs are essential for connecting accounts. You can link one student account to multiple teachers and parents. For example, the student’s Local ID (e.g., 0101) can appear in different rows with different teacher Local IDs in the corresponding columns. For example:
0101 1234
0101 3496

With a District, you can assign the same Local ID to a parent account across multiple schools. This allows them to access conferences for all assigned schools from a single account, streamlining their experience and reducing duplicate entries. The same feature works for teachers!
For example, to assign Parent A to both Middle School and Primary School, you need to include Parent A in the parent file for each school separately, using the same Local ID.
In the parent file for Middle School, list Parent A under Local ID 1234, and do the same in the Primary School’s parent file.
In the Middle School relationship file, Parent A’s Local ID (1234) should be linked to Student ID 1987 and uploaded to the Middle School system.
In the Primary School relationship file, the same Parent A’s Local ID (1234) should be linked to a different student (Student ID 4567) and uploaded to the Primary School system.
By doing this, you ensure that Parent A is properly connected to both schools.