How to switch from SedonaOffice without missing a single monthly monitoring bill
Short answer: check your SedonaOffice agreement and notice period first(Bold Group doesn't publish terms or pricing), then decide where the ledger will live, because SedonaOffice is your accounting system as well as your operations system. Export customers, sites, systems and every recurring line with its next bill date from the Customer Query Builder as CSV, and ask Bold for anything the query builder doesn't reach. Rebuild your install, inspection and service workflows, move one crew or one kind of work at a time, cut billing over at the start of a billing period, and keep SedonaOffice readable until a fixed date, ideally after year-end close.
With Fieldproxy, migration is free and assisted and you're live within a day: your first crew runs real installs, inspections or service calls the day after the call, on your own statuses and data. Everyone else moves on a schedule you set. Your books move to QuickBooks, Xero or Sage with two-way sync, because Fieldproxy is not a general ledger. One price per company, unlimited users.
Leaving SedonaOffice? See your setup first
Send us a SedonaOffice export. We build your stages, forms and data in Fieldproxy, free, before you decide.
Why teams leave
Why teams leave SedonaOffice, with the facts checked
SedonaOffice is a serious system. Bold Group calls it the only enterprise-level business software designed for security companies, and its accounting is the reason many dealers chose it. Companies rarely leave because the ledger is weak. They leave because the work around the ledger, in the field and on the fire side, needs more than the back office gives them. Each reason below is checked against Bold's own pages or a public code source, and where Bold doesn't say, we say so.
The install-to-monitoring handoff lives in notes
SedonaOffice's datasheet covers service, inspections, job management with full job costing and inventory down to the warehouse. What many dealers still keep in a tech's notes or a PDF is the handoff itself: the zone list in plain words, the call list with two numbers per contact, and proof that every zone reached the central station on test. In Fieldproxy, Site, System and Zone are records, the handoff is a checklist on the job, and an install can be blocked from Live until every zone shows received.
source: Bold Group, SedonaOffice datasheet (2019)source: SIAC, Law enforcement best practices
Fire inspections are recorded device by device
NFPA 72 testing is per device, deficiencies need photos, repairs need a quote the customer approves, and many AHJs want results filed through The Compliance Engine. In Fieldproxy the annual test runs on the technician's phone from the system record, offline in a basement if it has to, and each deficiency becomes a good, better, best repair quote the customer approves from a link. See how it's set up for fire safety companies.
source: City of Bellevue, F-50 Inspection, testing and maintenancesource: Seattle Fire Department, Fire alarm installation/acceptance report
Permits, Records of Completion and cure-by dates run on clocks
Florida low-voltage jobs need a Uniform Notice within 14 days after completion. A fire install needs an NFPA 72 Record of Completion before acceptance, and McAllen, Texas won't schedule a final inspection until it's uploaded. Fieldproxy gives each clock an owner and an alert, builds the Record of Completion from the system record as the job progresses, and keeps a UL certificate register linked to each system.
source: Florida Statutes s. 553.793, Low-voltage alarm permittingsource: City of McAllen, Fire alarm system Record of Completionsource: UL Solutions, Fire alarm service certification
Monthly billing starts when someone remembers
When the install closes in one place and the recurring charge is keyed in another, RMR can start a month late. In Fieldproxy the monitoring contract is created at signing and activated the day the install goes Live, with the monthly charge, cycle, term, renewal date and cancel reason as fields, not notes. Invoices then sync to your accounting system, where AR lives.
Weight, hosting and an owner with other products
SedonaOffice came from Perennial Software, which EverCommerce bought in 2018 and merged with Bold Technologies; the company became Bold Group in 2019. Bold now also sells Managely, a fully hosted cloud platform, and AlarmBiller for smaller dealers. SedonaOffice comes with a guided implementation and no published price. Some dealers want screens and statuses built around how they already work instead, with unlimited users. See Fieldproxy pricing.
source: Security Sales & Integration, Bold Technologies and Perennial Software merge after being acquiredsource: Security Systems News, Bold Perennial now Bold Groupsource: Bold Group, Managelysource: Bold Group, AlarmBillersource: Bold Group, SedonaOffice
AI agents and Claude or ChatGPT on your own data
Bold's SedonaOffice pages don't describe AI agents or a connector for Claude or ChatGPT. Fieldproxy's AI agentscan be set up to read a previous dealer's zone list into a draft, read a panel label from a photo, and warn you when an account sits on test too long. Its MCP server lets Claude, ChatGPT or Copilot do anything the app can do, with a person confirming each change.
Stay on SedonaOffice if
- You want recurring invoicing, AR, AP and the general ledger inside one dealer system. SedonaOffice does that natively. Fieldproxy is not a ledger: with us, the books live in QuickBooks, Xero or Sage.
- You run your own central station on Manitou and rely on SedonaOffice's link to it, where a monitored event can open a service ticket.
- Full job costing and warehouse-level inventory inside the ledger are central to how you close the month, and they work for you.
- You like Bold but want the cloud. Ask Bold about Managely or AlarmBiller before you look elsewhere.
- You're mid-term, or your SedonaOffice setup works and your team knows it. Don't switch to fix a problem you don't have.
Watch it
See the setup end to end
A fire alarm and security company set up in Fieldproxy with demo data, covering inspections, violations, installs and billing.
Fire Alarm & Security Company Software: Inspections, Violations, Installs & Billing (Walkthrough). Watch on YouTube
Before you go
What to export from SedonaOffice, and how
SedonaOffice's own help article documents one export route clearly: the Customer Query Builder (CQB) has an Export button that saves query results as a .csv file with every selected field, and an SQL button that shows the query behind it. Bold doesn't publish a full list of what the CQB reaches, so for anything it doesn't, ask Bold for a CSV in writing. Bold's datasheet also lists a report manager with hundreds of reports and custom queries. The rule for RMR: every recurring line must arrive with its next bill date, or a customer gets billed twice or not at all.
| Data | How to get it out of SedonaOffice | What happens to it in Fieldproxy |
|---|---|---|
| Customers, sites and contacts | Customer Query Builder, Export to .csv. Keep the SedonaOffice customer number as a column. | Customers and sites, checked for duplicates, with the SedonaOffice number kept as a reference field. Each site can get a QR code. |
| Systems, panels, communicators and zones | CQB, if your fields are reachable; otherwise ask Bold for a CSV. Fill gaps from your central station's account reports. | Site, System and Zone records: plain-language zone descriptions, zone type, area, wired or wireless, panel make, model and firmware. |
| Call lists, passcodes and central station account numbers | CQB or a CSV from Bold, checked against your central station's account report for each site. | Call list with two numbers per contact, account number and receiver format on the site, ready for the handoff checklist. |
| Recurring lines (RMR) | CQB or a CSV from Bold: amount, billing cycle, next bill date, term, renewal date, tax setting, cancel reason. | Monitoring and service contracts on each account, next bill dates kept exactly, checked against one full billing cycle run in both systems. |
| Open AR, deposits, credits and the general ledger | SedonaOffice's own reports (AR aging, GL), run at your cutover date with your accountant. | Not moved into Fieldproxy. Opening balances go into QuickBooks, Xero or Sage; Fieldproxy then syncs invoices and payments two-way. |
| Open jobs, tickets and inspection schedules | CQB or Bold's reports; list the schedule per system (annual, semi-annual). | Open jobs at the right stage; inspection due dates rebuilt as recurring schedules on each system. |
| Service and inspection history | Bold's reports or a CSV from Bold. | History on each site and system, so the next technician sees the last visit and the open deficiencies. |
| Inventory by warehouse, with serials | Bold's inventory reports. | Warehouse and van stock, with serials on installed equipment. |
| Technicians, licenses and certifications | A plain list: name, role, license type, number and expiry. | Unlimited users with roles; dispatch only offers fire alarm work to technicians whose licenses cover it. |
source: SedonaOffice help: Customer Query Builder function buttons (Export to .csv)source: Bold Group, SedonaOffice datasheet (2019)
What doesn't come with it
What doesn't export, and what we rebuild
An export carries records, not the way your account is set up. Here is what to expect, and who does the work.
Your ledger setup and posting rules
SedonaOffice posts transactions to its own general ledger in real time. The chart of accounts, posting rules and GL history stay with SedonaOffice. Your accountant sets them up in QuickBooks, Xero or Sage, and Fieldproxy's sync is mapped to them during setup.
source: Bold Group, Financial management solutionssource: Bold Group, SedonaOffice datasheet (2019)
Report designs, saved queries and mail merge templates
CQB query designs are saved as files and mail merge letters use templates on your Template Server. They are SedonaOffice formats. Save the files and screenshot the reports you use every month; we rebuild the ones that matter as Fieldproxy reports and documents.
source: SedonaOffice help: Customer Query Builder function buttons (Export to .csv)
The Manitou link
If you run your own central station on Manitou, the link that opens a SedonaOffice ticket from a monitored event doesn't move with an export. Talk to us before you plan the switch, and list how signals reach your service team today.
source: Bold Group, Manitou product sheet (2024)source: Bold Group, Alarm monitoring software
Sedona-X Mobile settings and card payments
Technician app settings and card payment setup in Sedona-X Mobile are rebuilt, not exported. In Fieldproxy, technicians take payment with Tap to Pay or a payment link, and forms and checklists are set per system or device.
Do these before you cancel SedonaOffice
- Read your SedonaOffice agreement for the term, notice period and renewal date, and get anything unclear in writing from Bold.
- Agree with your accountant where the ledger lives from cutover, and the date the opening balances are taken.
- Run every CQB export you need, with SedonaOffice customer numbers kept, and save the files and query designs.
- Ask Bold in writing for a CSV of anything the CQB doesn't reach: zones, call lists, recurring lines, history, attachments.
- Run the AR aging, deposits and credits reports at cutover, and keep a full GL export for audits.
- Screenshot your recurring billing settings, tax setup, reports and mail merge templates.
- Keep read-only access to SedonaOffice until year-end close, so history and audits never depend on a file.
Send us your SedonaOffice export and see it running in your setup.
Get DemoLive within a day
The move from SedonaOffice, day by day
Migration to Fieldproxy is free and assisted: our team builds your setup and moves your data. You're live within a day, meaning your first team runs real jobs in Fieldproxy the day after the call. How fast everyone else follows is your call.
Live within a day is when the first crew runs real jobs, not when billing moves. RMR billing moves only after a full billing cycle has matched in both systems. A large account base, messy zone data or a Manitou link adds time, and we say so on the first call.
What happens on go-live day- 1
Before the call: the agreement, the ledger decision and the exports
You and your accountant, about two hours
Find your SedonaOffice term and notice date. Decide with your accountant whether the books move to QuickBooks, Xero or Sage. Run the CQB exports for customers, sites and recurring lines. Pick a first crew to move, for example new installs or fire inspections. - 2
The call: one install and one inspection, start to finish
You and Fieldproxy, 30 minutes
Walk us through a burglar or fire install from survey to the first armed night, and an annual inspection from due date to repair quote. Tell us who approves what, what the central station needs, and how monthly billing starts. Send the exports, a few proposals, an inspection report and a Record of Completion. - 3
We build your setup
Fieldproxy's team
Install stages from Proposed to Live, the handoff and on-test checklists, NFPA 72 inspection forms per device type, deficiency to quote, permit and violation clocks, contract fields for RMR, roles, and the screens each person sees on the web and the phone app. Status names mirror SedonaOffice's where they work. - 4
We move your data, free
Fieldproxy's team and Fieldproxy AI
Customers, sites, systems, zones, call lists, recurring contracts with next bill dates, open jobs, inspection schedules and history, mapped and checked for duplicates. Ten accounts are checked end to end with you: site, zones, contacts, permit, contract and central station account all match. - 5
We connect the books
Fieldproxy's team, with your accountant
Two-way sync with QuickBooks Online, Desktop or Enterprise, or Xero, or deep sync with Sage, mapped to your chart of accounts and tested on real invoices. Exactly what syncs is agreed and tested in setup. - 6
Live: the first crew on Fieldproxy
Day one
One crew runs today's new installs or inspections in Fieldproxy, offline if needed, with GPS check-in. Billing, and everyone else, stays on SedonaOffice for now. - 7
Weeks or months: billing cuts over, then SedonaOffice goes read-only
Your schedule
Run one full billing cycle in both systems and compare every invoice line, tax and total. Cut billing over at the start of a billing period. Move service and inspections next, then the whole RMR base, and keep SedonaOffice readable until year-end close.
Cutover
Running SedonaOffice and Fieldproxy side by side
For a short, dated window, both tools are open. Fieldproxy is there to replace SedonaOffice, not to sit on top of it, so the rules below are about ending the overlap cleanly. Our view from moves we have run, not a sourced fact.
SedonaOffice bills until the cycle matches
While crews move, SedonaOffice keeps raising every recurring invoice. Fieldproxy runs the same cycle in parallel and sends nothing until every line, tax and total matches. Then billing cuts over on the first day of a billing period, so no account is billed twice or skipped.
One system of record per job
A crew on Fieldproxy creates every new install, inspection and ticket there; a crew still on SedonaOffice stays there. Open jobs finish where they started. Only one system posts each invoice to the books, and the numbering rule is agreed before day one.
A fixed switch-off date
Set the date SedonaOffice becomes read-only, ideally after year-end close and before your renewal date. The Watcher agent flags accounts on test too long, permits about to lapse and inspections coming due while crews are new to Fieldproxy.
The fear
What if a monitoring bill goes out wrong, or not at all, during the move?
Recurring revenue under contract is what an alarm company is worth, so the billing base is the part you can't afford to get wrong. This is how to move it so nothing is lost and nothing is billed twice.
- 1
Field work moves first, billing moves last
Crews can be on Fieldproxy for weeks while SedonaOffice keeps billing exactly as it does today. Nothing about RMR changes until you say so. - 2
Every recurring line keeps its next bill date
Contracts are loaded with amount, cycle, next bill date, term and renewal date, and checked line by line against the SedonaOffice export before they count. - 3
One full cycle in parallel before cutover
Both systems produce the same month's invoices. You compare them, we fix any difference, and only a matching cycle unlocks the cutover. A large account base can run more than one cycle. - 4
Contract rules come with the contracts
State rules can be kept on each contract record, for example California's separate signed disclosure for auto-renewals longer than a month, so a renewal is flagged before it rolls on a contract that doesn't carry it.
Where things live
SedonaOffice terms and where they go in Fieldproxy
So your office and crews know where things went on the first morning. How job costing, warehouses and multi-company setups map is agreed on the call.
| In SedonaOffice | In Fieldproxy |
|---|---|
| Customer and site records | Customers and sites, with the SedonaOffice number kept as a reference field |
| Systems and zone lists | System and Zone records on each site, with plain-language descriptions and panel photos |
| Recurring invoicing (RMR) | Monitoring and service contracts on the account; invoices sync to QuickBooks, Xero or Sage |
| General ledger, AR and AP | Stay in your accounting system: QuickBooks Online, Desktop or Enterprise, Xero (two-way) or Sage |
| Service tickets | Service jobs with your own stages, dispatched by license, skills and drive time |
| Inspections | NFPA 72 device-by-device inspections, deficiencies with photos, repair quotes approved from a link |
| Job management and job costing | Install projects from Proposed to Live, with labor, parts and the handoff checklist |
| Inventory by warehouse | Warehouse and van stock, with serials on installed equipment |
| Sedona-X Mobile | Fieldproxy app on Android and iOS: offline, photos, signatures, QR per site and asset, Tap to Pay |
| Customer Query Builder and Report Manager | Reports and dashboards, or ask your data in plain English through Claude or ChatGPT |
| Mail merge letters | Document templates and automated emails and texts from the record |
| Manitou link | Agreed case by case on the call; central station handoff sent from the job record |
Straight answers
Switching from SedonaOffice: FAQ
How long does it take to switch from SedonaOffice to Fieldproxy?
Is migration from SedonaOffice free?
SedonaOffice is our accounting system. Is Fieldproxy a general ledger?
How do I get my data out of SedonaOffice?
Can I keep SedonaOffice for accounting and use Fieldproxy in the field?
Does the Fieldproxy app work offline?
Can AI agents help an alarm company?
Can I use ChatGPT or Claude with my alarm company data?
Will monitoring billing start on the right date after an install?
Sources
Where the facts on this page come from
Every SedonaOffice fact links to SedonaOffice's own pages, opened on 19 November 2026. Features and terms change, so check the current page before you decide. More detail, with every source, is in How Fieldproxy is set up for fire alarm and security companies.
- source: Bold Group, SedonaOffice
- source: Bold Group, SedonaOffice datasheet (2019)
- source: Bold Group, Financial management solutions
- source: Bold Group, Sedona-X Mobile
- source: Bold Group, Managely
- source: Bold Group, AlarmBiller
- source: Bold Group, Alarm monitoring software
- source: Bold Group, Manitou product sheet (2024)
- source: SedonaOffice help: Customer Query Builder function buttons (Export to .csv)
- source: Security Sales & Integration, Bold Technologies and Perennial Software merge after being acquired
- source: Security Systems News, Bold Perennial now Bold Group
- source: California Business and Professions Code s. 7599.54, Alarm agreements
- source: Florida Statutes s. 553.793, Low-voltage alarm permitting
- source: City of Bellevue, F-50 Inspection, testing and maintenance
- source: Seattle Fire Department, Fire alarm installation/acceptance report
- source: City of McAllen, Fire alarm system Record of Completion
- source: UL Solutions, Fire alarm service certification
- source: SIAC, Law enforcement best practices
Leave SedonaOffice without the leap. Live within a day.
A 30-minute call about how a job runs in your business, and a SedonaOffice export. We show you your own setup and data running in Fieldproxy before you commit.
Plan my switchFree, assisted migration. One price per company, unlimited users. Changes are a conversation.