The one-way Finalsite Enrollment to Veracross integration sends admissions data from Finalsite Enrollment to Veracross automatically. It's useful for schools that use Finalsite Enrollment for Admissions and Veracross for Enrollment. There's an additional charge; contact Support to get started.
💡Quick Answers
- Which direction does data flow? One-way: from Finalsite Enrollment to Veracross. Admissions runs in Finalsite Enrollment; data is then pushed to Veracross.
- How is relationship data handled? Each student is linked to their parents and siblings, but parents are not linked to each other (no spouse relationships) and siblings are not linked to one another.
- What's required for clean syncing? Student IDs must match exactly between Finalsite Enrollment and Veracross. Inconsistent IDs cause sync errors.
- Where do I see what data points are sent? A reference list of data points is linked in the article. Need additional data? Support can create a custom export.
- Who handles which setup steps? The school adds Finalsite Enrollment as an Integration Partner in Veracross, then notifies Finalsite Enrollment Support so they can complete the Finalsite Enrollment side using the Veracross credentials.
- Who manages enrolled students? Up to you. Either side can manage enrollment, depending on which is easier for your admins and parents. If using Finalsite Enrollment, manually update statuses of NEW students to enrolled in Veracross after the push.
Admissions & Enrollment Process
Admissions
The Admissions Process is managed within Finalsite Enrollment, however, Veracross has the school build out their admissions process within Veracross so that the integration will work.
Enrollment: Which System Do I Use?
The Enrollment Process can be managed within Finalsite Enrollment with the integration, or it can be managed solely within Veracross. It depends what makes more sense to the Admin, and which product is easier for parents and Admins to use for Enrollment.
If your school would like to use Finalsite Enrollment for Enrollment, you can work with the Support Team to build a custom export of enrolled student data. Once the data has been pushed to Veracross, the school will need to update the statuses of NEW students to enrolled within the Veracross system.Â
Â
Important Integration Notes
-
Relationship data: The integration process establishes the relationship for the student, linking them as a child to their parents and as a sibling to their brothers and sisters. In other words, it only connects the student you import to their parents and siblings. The siblings and parents themselves are not connected to one another.
For example, You import the following family:
Agatha Miller (student)
Margaret Miller (sister)
Louis Miller (brother)
Clarisa Boehmer (mother)
Fredrick Miller (father)
Upon Import, Agatha is connected as the child of Clarisa and Fredrick and the sibling of Louis and Margaret, but Louis and Margaret themselves are not connected as siblings, and, on the same thread, Clarisa and Fredrick are not connected to one another as spouses.
For more information on relationship management, you can check out this Veracross article.
 -
Ids: To ensure seamless integration across systems and avoid potential issues, it is crucial that IDs match consistently. Students must maintain the same ID in both Finalsite Enrollment and Veracross. This alignment of IDs between the two systems is essential for smooth data synchronization and to prevent any discrepancies or complications that might arise.
 -
Data Points: Click here to review the specific list of data that can be sent from Finalsite Enrollment to Veracross. If you require the ability to send additional data beyond what is listed, our dedicated support team can create a custom export tailored to your needs.
- For more information about creating a custom export, we encourage you to explore our comprehensive article: Custom Data Services: Data Export to SIS & 3rd Party Systems. There, you can find details about the expected timeline and requirements for this service, enabling you to make informed decisions based on your unique requirements.Â
Finalsite Enrollment to Veracross Integration: Setup & Responsibilities
Once your school has purchased the integration, you can begin the setup process. This integration uses the new Veracross API, so users with the OAuth_App_Admin role can begin the setup themselves from the Identity & Access Management homepage in Axiom.
Customer Responsibilities
- Add Finalsite Enrollment as an Integration Partner in Veracross and start the integration
- Inform the Finalsite Enrollment Support Team via email once complete so that we have access to the Client ID and Client Secret in the Veracross Partner Portal
- Collaborate with Finalsite Enrollment Configuration Team to get the export configuration set up to meet your data needs
- (ongoing) Run exports in Finalsite Enrollment to push to Veracross as needed
Finalsite Enrollment Responsibilities
- Complete set up of integration in Finalsite Enrollment using customer-specific credentials from Veracross
- Create export configuration used to export data out of Finalsite Enrollment into Veracross
- Provide support throughout the setup process and handle troubleshooting of any issues related to the export
Comments
0 comments
Article is closed for comments.