NERIS Resource Center
NFIRS to NERIS: a migration guide, not a scare piece.
Moving from NFIRS to NERIS is a workflow change, not just a form change: incident structure, submission path, and entity registration all differ from what your department has done since the paper-form era. This guide covers what actually changes, what happens to your years of NFIRS records, and the questions that protect your history.
Key takeaways
- NERIS restructures incident data. It is not a recoding of NFIRS, so "mapping the old codes" is the wrong mental model for training officers.
- Your NFIRS history does not flow into NERIS automatically. Where it lives, and whether it stays usable, is decided by your software vendor.
- The transition is the moment of maximum vendor honesty: certified-and-live is provable; "on the roadmap" is a bet your compliance rides on.
- Departments switching software during the transition should migrate NFIRS history into the new system, not leave it hostage in the old one.
What actually changes for your department
Incident structure. NFIRS asked "which code is this incident?" NERIS captures what happened in a richer structure: incident types, actions, and context designed for modern analysis. For officers, the practical change is how reports are organized and validated, which is why an hour of hands-on training beats a code-mapping cheat sheet.
Submission path. Instead of NFIRS flat-file submissions through state channels, NERIS is a cloud platform your records system integrates with directly. Your department's entities (the department itself, stations, FDIDs) are registered in NERIS, and your software submits against them. Multi-FDID departments: this is where the complexity concentrates. Without software that manages it, each identity can mean its own login and its own submission workflow.
Validation. NERIS enforces data quality at submission. Software that validates before submitting turns errors into red flags at write-time; software that doesn't turns them into rejected federal records at month-end.
What happens to your NFIRS data
Here is the part that matters most and gets said least: NERIS does not import your NFIRS history. Those records (for some departments, decades of them) back your ISO audits, grant applications, legal defenses, and institutional memory. What happens to them depends entirely on your software situation:
If you stay with your current vendor: ask exactly where NFIRS records will live after the transition, whether they remain searchable and reportable next to NERIS records, and whether keeping them accessible costs extra. Get it in writing.
If you're switching software: your NFIRS history should migrate into the new system as part of implementation, not stay behind in a legacy vendor's archive that you lose access to when the contract ends. This is Alpine's standard practice: RedAlert implementations include migration of historical incident data (we've converted hundreds of departments from every RMS under the sun, plus Access databases and homegrown systems), and NFIRS history stays searchable alongside new NERIS records. How our migration works →
Using the transition well
A forced reporting change is disruptive no matter what, so extract value from it. Departments are using NERIS as the trigger to consolidate the point solutions they've accumulated (separate alerting apps, spreadsheet LOSAP, paper truck checks) into one system, on the logic that one migration beats four. If your vendor's NERIS answer was shaky anyway, the math gets easy.
Common questions
Does RedAlert still handle NFIRS?
Your NFIRS history remains in RedAlert and stays queryable. Alpine migrates historical NFIRS incident data as part of every implementation, so you can report across the NFIRS and NERIS periods because both live in the same database. New incidents are written and submitted as NERIS, which is the federal path now that NFIRS is retired. If you are shopping for what you still think of as NFIRS software, the capability you want is incident reporting and NERIS.
Can we map our old NFIRS codes to NERIS?
Not one-to-one, and it's the wrong goal. NERIS restructures incident capture rather than renaming NFIRS codes. Good software presents the new structure cleanly and validates it; good training teaches officers the new shape once instead of maintaining a translation table forever.
Will our ISO audit still work if our history is split across NFIRS and NERIS?
It works if both live in one reportable system. The risk case is history stranded in a legacy vendor's archive while new records accumulate somewhere else. In RedAlert, migrated NFIRS history and new NERIS records are reported together, the auditor gets one package.
Our current vendor says NERIS support is "coming." Should we wait?
Ask for a date in writing and a customer already submitting. If they can't provide either, remember what's at stake isn't their roadmap. It's your federal reporting, your grant data, and your audit trail. "Coming" from a vendor is a promise; certified-and-live is a fact you can verify in a demo.
Twenty years of NFIRS records? They come with you.
See how RedAlert migrates history and submits to NERIS, live, with a real person.