Switching
Three CSV files, one wizard, both systems until you are ready. Still deciding? What a district gains and gives up.
Step one
Exports we have seen (as of September 2026) include only the list view's columns, so add every column first.
| Dataset | Where in Incident IQ | Columns to include |
|---|---|---|
| Users | Users list → gear → Export to CSV (or Administration → Data Export) | Email, first and last name, role (user type), location, title, phone, user ID |
| Assets | Assets list → filter All → Export to CSV | Asset tag, serial number, model category (asset type), model, manufacturer, status, owner email, location, room, purchase date, warranty expiration, purchase price, notes, asset ID |
| Tickets | Tickets list → filter All statuses and your date range → Export to CSV | Ticket number, subject, description, status, priority, issue category, requestor and requestor email, assigned to and assigned-to email, location, asset tag, created / resolved / closed dates, tags, and comments or ticket history if the view offers it |
UTF-8 CSV, up to 5 MB a file, about 20,000 rows. Split larger exports and import them oldest first.
Step two
Incident IQ columns are recognized automatically. The full guide: every column, match rule and re-run, step by step.
Pick Users, Assets or Tickets, drop the CSV.
Adjust columns, keep ticket numbers, pick a default status.
Live progress, then totals, an unmatched list and a CSV of row errors.
Step three
Incident IQ stays read-only. New tickets go to Beacon.
Forward help@yourdistrict.org to your tickets.beaconhelpdesk.com address.
Anything not yet imported is still there.
At cut-over, import tickets changed since the switch. New ones are created, the rest skipped.
The offer
Free until your Incident IQ term ends, up to 12 months. Your paid term starts the day theirs ends.
No onboarding, implementation or services fee.
Start it yourself: full District plan, every module, unlimited agents.
Then $1 per student per year with every module, locked for three years. Pricing.
A realistic afternoon
A mid-sized district on Google Workspace.
| 1:00 | Create the organization. Ten minutes on the sign-up page. Pick the slug that becomes your permanent address. |
| 1:15 | Single sign-on. Admin → Single sign-on → Google Workspace or Microsoft: add your domains and turn it on. Nothing to create in the Google or Microsoft console unless you want your own OAuth client. Test in a private window. |
| 1:45 | Sites and teams. Add each school with a short code. Put technicians on IT Support and Device Repair, building staff on Facilities. |
| 2:00 | Import users. Drop the Users export. Agents land on their teams; everyone else becomes a requester. |
| 2:20 | Import assets. Drop the Assets export. Asset types are created, statuses mapped, owners matched. Fix the unmatched list, re-run. |
| 2:45 | Import tickets. Drop the Tickets export, sorted by ticket number, lowest first, with Keep the exported ticket numbers on. It runs in the background; check the reconciliation summary when it finishes. |
| 3:15 | Categories, SLAs, automations. Rename what needs renaming, attach Classroom Down to Classroom Technology and Wi‑Fi, test the routing rules on a real ticket. |
| 3:30 | Email. Forward help@yourdistrict.org to your tickets.beaconhelpdesk.com address. Send a test. |
| 3:45 | Portal. Logo, color, welcome text, and five public articles for the top deflection categories. |
| 4:00 | Phones. Technicians sign in to the mobile web app on their phones and type ten tags into Scan on the Assets page to spot-check the import. The iOS app, in testing on TestFlight, adds the camera scanner. |
| 4:30 | Announce. One email to staff: what changed, the portal link, and that emailing help@ still works. |
Questions
No. The import wizard, SSO, and provisioning are product features. If you get stuck, email hello@beaconhelpdesk.com and a person answers within one business day.
Not if you turn on Keep the exported ticket numbers and import oldest first: sort the export by ticket number, lowest first, and import split files in that order. Incident IQ numbers are reused where they are higher than the last one Beacon assigned and unused; Beacon's counter jumps ahead so new tickets keep numbering upward. Either way the Incident IQ number and ID stay on every imported ticket.
No. Imported rows send no notifications, run no automations, start no SLA clocks, and are not triaged by AI.
The ticket is still imported with the category blank or the assignee empty, and the value appears in the unmatched list. A re-run skips tickets already imported, so it does not fill those in afterward: create your categories and import your users before the tickets, and set any stragglers on the tickets themselves.
Yes. Users and devices are updated in place; tickets that were already imported are skipped and counted. Every job is listed under Import history, and a running job can be cancelled.
The CSV exports we have seen do not include files. If you want file history, email us; with your Incident IQ API token, attachments can be brought across into the imported tickets.
Yes. Keep Incident IQ read-only for 30 days while new tickets go to Beacon, then import a final delta.
Run Beacon free until that term ends, up to 12 months. Your paid term starts the day theirs ends.
From ClassLink, yes: students sync from ClassLink Roster Server or any OneRoster export with their school, grade level and student ID. Clever is supported for sign-in, and users are created automatically on first sign-in. Staff and students also sync nightly, read-only, from PowerSchool with their school, grade level, homeroom and classes, and people from Google Workspace or Microsoft Entra with their title, phone and site. Guardians are not synchronized.
Chromebooks, yes: a Workspace administrator connects Google Admin once on Admin → Import, and Beacon reads every Chrome device each night, read-only, matching the devices you imported by serial number. How it works. Intune, yes: an Entra Global Administrator connects Microsoft Entra once, and Beacon reads every device managed in Intune each night, read-only, matched the same way. Apple devices in Mosyle Manager, yes, on the district's own API token. Jamf and SCCM, not yet; those devices are imported from CSV.
Yes, on every plan, at any time: a JSON bundle from Settings and CSV from Reports. If you leave, nothing is held.
Get started
No card, no sales call, no auto-conversion.