Switching
From Raptor.
District-wide systems come with district-wide habits. The move works best building by building, with the screening policy and the SIS connection settled before the first desk changes.
- Settle the policy before the tool.
Write down the current screening and alert rules as the desks actually apply them, not as the manual says. That document becomes the configuration. - Export visitors and volunteers.
Ask for CSV exports of visitors, volunteers and any ban or watch list. Phone numbers and dates of birth matter for de-duplication; visit history mostly does not. - Decide on SIS sync.
If you are a district, the PowerSchool connection is what keeps student and staff lists current without anyone typing. It is a paid feature; a single school on the free plan can run without it. - Start with one school on the free plan.
It costs nothing and it settles the badge design, the alert routing and the desk routine before anyone has signed anything. - Run the parallel week at that school.
Both systems on one desk, five days, EduQueue as the record. Check the evacuation PDF during a drill if one falls in the week. - Roll out in the order the buildings are ready, not alphabetically.
A building with a settled receptionist and a working printer goes before the one that is mid-renovation.
For a side-by-side of the two products, see raptortech-alternatives.com, which we also publish and which cites its sources. This page is only about the move.
Talk to us about the move
Say where you are coming from and how many desks. We have done this move before and will tell you where it snags.