Partners who stayed on Orna.
Work mutual aid and shared coverage with an Orna agency as if you shared a CAD: their calls show on your board, yours on theirs, without phone-call relays.
Integration · Orna
Run Orna alongside EchoCAD. Or leave it, and keep everything.
Echo911 built two tools for agencies on Orna: a live sync that shares CAD calls one-way or two-way between the platforms, and a full Orna-to-EchoCAD importer for agencies ready to convert completely, with their history intact.
Sync and importer available now. Direction and scope configured per agency by Echo911.
Live sync
CAD calls, shared in real time.
For agencies running Orna next to EchoCAD, or working with partner agencies that do, calls flow between the platforms automatically. One-way or two-way, your choice.
THEIR SIDE
Orna
Calls created or updated in Orna appear in EchoCAD as live incidents.
◀━ ONE-WAY ━
◀━ TWO-WAY ━▶
◀━ TWO-WAY ━▶
YOUR SIDE
EchoCAD
Calls created or updated in EchoCAD flow back to Orna when two-way sync is on.
Both platforms, one truth.
During a migration, sync keeps Orna and EchoCAD consistent, so no call is missed while dispatchers move to the new console at their own pace.
Your rules, your direction.
Echo911 configures which direction data flows and what syncs. One-way inbound, one-way outbound, or full two-way.
Full conversion
The Orna-to-EchoCAD importer.
Ready to leave? The importer moves your agency onto EchoCAD completely, and your data comes with you.
We take your Orna data.
Echo911 pulls your data from Orna and maps every field to its EchoCAD equivalent: calls, units, and history.
We import and check it with you.
The importer loads your history into EchoCAD, and your agency verifies the result against the source before anything goes live.
Day one starts with your history.
Dispatchers open EchoCAD to years of their own call data, searchable and mapped, and Orna can be retired on your schedule.
What you gain by converting.
- The full EchoCAD platform: console, EchoMDT, EchoCAD Mobile, EchoPhone, and built-in EchoRMS
- NENA-standard GIS with validated address intake and Esri-compatible mapping
- Officer safety built in: SOS/man-down, status-check timers, and premise-hazard alerts
- One vendor, 24/7 support for CAD, records, and every integration on this page
What you don't give up.
- Your call history: imported, not abandoned
- Your partners: agencies still on Orna keep sharing calls with you over the live sync
- Your timeline: sync first, convert when ready; there is no forced cutover date
FAQ
Orna integration questions.
What is the difference between the sync and the importer?
The sync is for coexistence: calls flow between Orna and EchoCAD in real time, one-way or two-way, while both systems stay in use. The importer is for conversion: it moves your Orna data into EchoCAD in a guided migration so your agency can leave Orna entirely without losing history.
Can we sync one-way only?
Yes. The direction is configured per agency. Some agencies push Orna calls into EchoCAD only, some push EchoCAD calls out to Orna only, and some run full two-way sync.
If we convert, do we lose our old calls?
No. The Orna-to-EchoCAD importer is built specifically so agencies keep their data: your call history comes across into EchoCAD, and day one on the new platform starts with your records, not an empty database.
Can we run the sync first and convert later?
Yes, and many agencies should. Run both platforms in sync during a transition period, let dispatchers and responders get comfortable, then run the importer and cut over when you are ready.
Orna is a trademark of its respective owner. The name is used to identify interoperability and data-migration capability only and does not imply affiliation with or endorsement by that vendor.
Get started
Sync with Orna today. Convert when you're ready.
Tell us how your agency uses Orna and we'll map out the sync, the import, or both.