FieldproxySwitching guide ยท sources checked 19 November 2026

How to switch from Q360 without skipping a single service plan or monitoring bill

Short answer: read your Solutions360 agreement for the term and notice date first, then decide with your accountant whether the books stay in an ERP or move to QuickBooks, Xero or Sage. Solutions360 doesn't publish an export guide, so ask them in writing for CSVs of customers, sites, installed equipment, contracts and recurring lines, open calls, projects and PM schedules. Rebuild your install and service process, move one crew at a time with field work first, move recurring billing last at a month end, and keep Q360 readable until a fixed date.

With Fieldproxy, migration is free and assisted and you're live within a day: your first install crew or service tech runs real jobs in Fieldproxy the day after the setup call, with your own statuses, checklists and handoff rules. Everyone else moves on a schedule you set. One price per company, unlimited users, so adding a project manager or a subcontractor never changes the bill.

Leaving Q360? See your setup first

Send us a Q360 export. We build your stages, forms and data in Fieldproxy, free, before you decide.

Book your demo

A video call with our team

Number of employees

Why teams leave

Why teams leave Q360, with the facts checked

Q360 is a serious product. It runs sales, projects, service contracts, inventory, field service and full accounting for integrators in one system, and Solutions360 says it serves 500+ integrators across AV, security, fire and life safety. Integrators who leave it are rarely missing a feature. More often they want something lighter than an ERP, or something that reaches the customer and the phone. Each point below is checked against Solutions360's own pages and published news on 19 November 2026.

You want field software, not a new ledger

Q360's finance module runs project accounting, invoicing and revenue recognition, and its QuickBooks comparison page calls its accounting native and full-featured. That is a strength if you want one ERP. If your controller is settled in QuickBooks, Xero or Sage, it means the ledger moves too. We work the other way round: Fieldproxy runs installs, service and contracts and syncs two-way with QuickBooks Online, Desktop and Enterprise, Xero and Sage, and exactly what syncs is agreed and tested during setup. The books stay where your accountant wants them.

source: Solutions360: Finance & Accounting (project accounting, revenue recognition)source: Solutions360: Q360 compared with QuickBooks

A new owner, a new CEO and the consulting arm sold

In October 2025 Northrim Horizon made a strategic growth investment in Solutions360 and Nate Gardner became CEO, with founder Brad Dempsey moving to CTO. In March 2026 NSCA bought Navigate, the consulting business Solutions360 had owned since 2021. The stated plan is more investment in AI and modules, which may suit you well. It is still a sensible moment to compare before you renew, and to get roadmap and support commitments in writing whichever way you go.

source: NSCA: Solutions360 receives strategic growth investment from Northrim Horizon, appoints Nate Gardner CEO (14 Oct 2025)source: AV Network: NSCA acquires Navigate Management Consulting (March 2026)source: Solutions360: About us (leadership, customers)

The customer can't approve anything from a link

Q360 tracks inspections, deficiencies and SLAs well inside the system. We found no customer portal or no-login approval links on its service, field service or payments pages. In Fieldproxy a property manager approves a deficiency repair or a monitoring agreement from a link, signs off a PM visit, views the inspection report and pays, and multi-site customers get a portal scoped to their own sites.

source: Solutions360: Service & Contracts (SLAs, recurring inspections, renewals, block time)source: Solutions360: Field Service Management (offline-first mobile app, AskQ)source: Solutions360: Q360 Payments (cards, ACH, autopay)

The install-to-monitoring handoff is a custom job

Q360's security page lists RMR billing and a site-level installed base for access control, video and intrusion. It doesn't name zone lists, central station handoff, alarm permits or CP-01 programming records. In Fieldproxy those are standard records on the site: the zone list with plain-language descriptions, the call list, the city permit number and the on-test results, and an install can't move to Live until every zone shows received. Fire installs build the NFPA 72 Record of Completion as the job progresses, and Florida jobs carry the 14-day Uniform Notice clock.

source: Solutions360: Security integrators (RMR billing, installed base)source: City of McAllen: NFPA 72 fire alarm Record of Completion formsource: Florida Statutes s. 553.793: low-voltage alarm permit labels and Uniform Notice

AI that helps in the screen, not on the phone

AskQ reads the record you're on, runs 25 built-in tasks and answers how-to questions. It's useful, and it works inside Q360. We found no phone, text or email agent and no ChatGPT, Claude or MCP connection on Solutions360's pages. Fieldproxy's AI agents answer after-hours trouble calls, log them on the right site and system, check the service plan, and chase unsigned agreements and unapproved deficiency quotes. Our MCP server lets ChatGPT, Claude and Copilot work on your data, with a person confirming each change.

source: Solutions360: AI Agents (AskQ, 25 built-in agent tasks)

A price you only see in a sales cycle

Q360 publishes no pricing for the software or the implementation. Fieldproxy doesn't publish a dollar figure either, but the model is simple: one price per company by monthly job volume, unlimited users on every plan, AI credits included, and migration free. See how plans work.

source: Solutions360: Q360 homepage (segments, modules)

Stay on Q360 if

  • You want one ERP with the general ledger, revenue recognition and project accounting in the same product. Q360 does that and Fieldproxy is not a ledger.
  • Your Q360 setup already holds your install, contract and handoff rules and your team trusts it. Don't move to fix a problem you don't have.
  • You rely on Q360 Payments autopay across many monitoring customers and don't want to ask them to re-authorize a card or bank account.
  • Your design team lives in D-Tools or XTEN-AV and the two-way quote flow into Q360 is working. Q360 has those integrations named on its own site.
  • You're mid-term on your agreement. Build and test now, and set the cutover for the term end.
How Fieldproxy is set up for AV and security integrators

Before you go

What to export from Q360, and how

Solutions360 doesn't publish an export guide, and we found no documented bulk export on its API and integration page. So treat every row below as a written request to your Solutions360 account manager: ask for a CSV or Excel file of each, with Q360's own customer and site numbers kept so records can be matched. Make the request well before your notice date, open every file, and keep copies.

DataHow to get it out of Q360What happens to it in Fieldproxy
Customers, sites and contactsAsk Solutions360 for a CSV of customers, bill-to and site addresses, and contacts, with Q360 IDs.Customers and sites with the bill-to kept separate from the site, so landlords and multi-site accounts bill correctly.
Installed base (systems and equipment)Ask for a CSV of equipment per site: system type, make, model, serial, install date, warranty end.Systems and devices on each site, each with a QR code. AV rooms get their device schedule; security systems their panel and communicator.
Service contracts and RMR linesAsk for each contract: plan, amount, frequency, start, end, next bill date, SLA tier and block time balance.Contract records that keep their next bill date, response targets and included visits. Nothing is billed until you switch billing over.
PM and inspection schedulesAsk for each recurring schedule with its last completed and next due date.Recurring visits and inspections generated from the contract on their existing due dates, so the cycle carries on unbroken.
Inspection history and deficienciesAsk for a CSV of deficiencies and the inspection reports as files; keep the reports customers and AHJs may ask for.Open deficiencies become quotes the customer can approve from a link; past reports attach to each system's history.
Open service calls and projectsAsk for open calls with status, and open projects with job cost to date and billed to date.Open calls land at the right stage. Projects carry cost and billing to date as a starting point, and AV rooms keep their punch items.
Zone lists, call lists and permitsAsk where these are held in your Q360 setup (often custom fields or attachments) and request them as a CSV.Structured zone lists, call lists and permit numbers per site, with renewal reminders on the permits.
Open AR and paymentsRun an AR aging at cutover and ask Solutions360 what can and can't be exported from Q360 Payments.Open invoices stay in your accounting system. Saved card and ACH authorizations usually can't move, so customers re-authorize.
Inventory and open purchase ordersAsk for stock on hand by location and open POs.Stock per warehouse and van, with parts used on jobs pulled from it.

source: Solutions360: API & Integration (D-Tools, XTEN-AV, HubSpot, Inspect Point and others)source: Solutions360: Service & Contracts (SLAs, recurring inspections, renewals, block time)source: Solutions360: Security integrators (RMR billing, installed base)source: Solutions360: Q360 Payments (cards, ACH, autopay)

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 and its posting rules

If Q360 has been your books, the chart of accounts, revenue recognition setup and posting rules don't come with the data. Your accountant sets up the books in QuickBooks, Xero or Sage from trial balances and open AR and AP at a month end. We then agree and test what syncs, for example invoices, payments, customers and items.

source: Solutions360: Finance & Accounting (project accounting, revenue recognition)

AskQ tasks, dashboards and reports

AskQ's built-in tasks and your OneDashboard views are part of Q360, not data. List the reports your owners and service managers read each week, and we rebuild them as Fieldproxy dashboards and scheduled reports.

source: Solutions360: AI Agents (AskQ, 25 built-in agent tasks)source: Solutions360: Finance & Accounting (project accounting, revenue recognition)

Integrations and saved payment methods

The D-Tools, XTEN-AV, HubSpot, Ramp, Avalara, PSA and Inspect Point links stop with Q360. Note which ones you use and what each one moves. Card and ACH authorizations held in Q360 Payments stay with that processor, so plan a re-authorization request to autopay customers before billing moves.

source: Solutions360: API & Integration (D-Tools, XTEN-AV, HubSpot, Inspect Point and others)source: Solutions360: Q360 Payments (cards, ACH, autopay)

Workflows and SLA rules

Skills-based dispatch rules, SLA escalation timings, contract renewal automation and email-to-service-call rules are settings. Write each one down, with who gets which alert and when, and we set the same rules up as Fieldproxy automations.

source: Solutions360: Service & Contracts (SLAs, recurring inspections, renewals, block time)

Do these before you cancel Q360

  • Read your Solutions360 agreement for the term, notice period and renewal date, and get anything unclear confirmed in writing.
  • Decide with your accountant where the books live after cutover, and the month end where opening balances are taken.
  • Send Solutions360 a written export request listing every row in the table above, and open each file when it arrives.
  • Run the AR aging and a full set of financial reports at cutover, and keep them for audits.
  • Download the inspection reports, Records of Completion and AV closeout packs customers or AHJs may ask for.
  • Ask autopay customers to re-authorize their card or bank account before the first bill from the new system.
  • Keep read-only access to Q360 until after year-end close if the ledger was in Q360.

Send us your Q360 export and see it running in your setup.

Get Demo

Live within a day

The move from Q360, 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 means your first team runs real jobs, not that the whole company has moved. A ledger migration, hundreds of recurring lines or a large open project book add time, and we say how much on the first call.

What happens on go-live day
  1. 1

    Before the call: agreement, ledger decision and export request

    You and your accountant, about two hours

    Find the Q360 term and notice date. Decide where the books will live. Send the export request. Pick a first team to move, for example one security install crew or the fire inspection techs, and pick a month end for billing.
  2. 2

    The call: one install and one service contract, end to end

    You and Fieldproxy, 30 minutes

    Walk us through one recent job: survey, proposal, the monthly charge, permits, programming, central station handoff or AV acceptance, and then the service plan with its visits and response targets. Send a sample zone list, Record of Completion or closeout pack, and the exports you already have.
  3. 3

    We build your setup

    Fieldproxy's team

    Sites, systems and devices; zone lists and handoff records for security; device counts and the Record of Completion for fire; rooms, submittals, punch lists and closeout for AV. Your statuses, required photos, inspection forms, contract tiers and the screens each role sees on the web and the iOS and Android app.
  4. 4

    We move your data, free

    Fieldproxy's team and Fieldproxy AI

    Customers, sites, installed equipment, open calls, projects, contracts and PM schedules, mapped and checked for duplicates, with Q360 IDs kept. Contracts keep their next bill and next visit dates. Inspection reports attach to each system's history.
  5. 5

    We connect the books

    Fieldproxy's team, with your accountant

    Two-way sync with QuickBooks Online, Desktop or Enterprise, Xero or Sage, tested with real invoices and payments before anyone depends on it. Recurring billing stays in Q360 for now.
  6. 6

    Live: the first crew runs real jobs

    The day after the call

    The pilot team works in the Fieldproxy app: site notes and history, checklists, required photos, signatures and on-test results. Everyone else stays on Q360, and the office sees both until the next team moves.
  7. 7

    Weeks or months: team by team, billing last

    Your schedule

    Move the remaining install crews and service techs, one team at a time. After one full billing cycle matches line by line, switch recurring billing at a month end. Then take final exports and let the Q360 term end.

Cutover

Running Q360 and Fieldproxy side by side

For an integrator the overlap has two speeds: field work moves quickly, team by team, and recurring billing moves once, at a month end, after a full cycle has been checked.

Every job lives in one system

A service call, install or inspection is worked in Fieldproxy or in Q360, never both. Teams that have moved take new work only in Fieldproxy; anything opened in Q360 before their move is finished there.

Q360 bills until one cycle matches

Contracts are loaded in Fieldproxy with their next bill dates, but Q360 keeps billing for one cycle. Compare the two invoice runs line by line, then switch at a month end, so no monitoring or service plan month is skipped or doubled.

A fixed switch-off date

Agree the date Q360 becomes read-only, ideally at the end of its term. While the team is new to Fieldproxy, the Watcher agent flags accounts left on test, permits about to expire and SLA targets close to a miss.

The fear

What if a service plan or monitoring month is billed twice, or not at all?

Recurring revenue is what an integration business is valued on, and a billing mistake lands on your best customers first. This is how we keep the switch from touching it.

  1. 1

    Billing moves last, on its own date

    Field work moves first. Recurring billing stays in Q360 until you choose a month end to switch, so the risk sits in one planned step, not spread across the move.
  2. 2

    One cycle compared line by line

    Before the switch, the contract lines loaded in Fieldproxy produce a draft invoice run for the same period Q360 bills. Every difference in amount, date or customer is fixed before anything is sent.
  3. 3

    Every contract keeps its next bill date

    Each contract arrives with its next bill date, frequency and amount from the Q360 export, so billing carries on from where Q360 stopped, not from the day you moved.
  4. 4

    Autopay re-authorized before it is needed

    Customers paying by saved card or ACH get a request to re-authorize weeks ahead, with a payment link. Those who haven't done it by cutover are listed for a call, not discovered when a payment fails.

Where things live

Q360 terms and where they go in Fieldproxy

So your office and technicians know where things went on the first day. How contract tiers and project billing are set up is agreed on the call.

In Q360In Fieldproxy
Sales & CRM, quotesProposals with one-time lines and monthly lines, approved and signed from a link
Projects & Job Costing (site, building, room)Install jobs by phase; AV rooms with submittals, punch lists and closeout gating the final invoice
Customer equipment list / installed baseSites, systems and devices with serial, firmware, warranty and a QR code
Service & Contracts, SLAsContracts with tiers, response targets, included visits and SLA clocks with escalation
Recurring inspections and PM schedulesRecurring visits and inspections generated from the contract on their due dates
DeficienciesDeficiencies with photos that become quotes the customer approves from a link
RMR billingMonthly charges that start on Live or acceptance and sync to QuickBooks, Xero or Sage
Field Service Management mobile appTechnician app in 27 languages: checklists, required photos, signatures, QR codes, GPS check-in
Skills-based dispatchScheduling by skill, license (installer registration, fire alarm technician, CTS) and drive time
Finance & AccountingNo ledger in Fieldproxy: books stay in QuickBooks Online, Desktop or Enterprise, Xero or Sage
Q360 PaymentsPayment links on invoices and Tap to Pay in the field
AskQAI agents on phone, text and email, and an MCP server for ChatGPT, Claude and Copilot

Straight answers

Switching from Q360: FAQ

How long does it take to switch from Q360 to Fieldproxy?
You're live within a day: your first install crew or service tech runs real jobs in Fieldproxy the day after the setup call, with free, assisted migration. Moving every team is on your schedule. Recurring billing moves last, at a month end, after one full billing cycle has been compared in parallel.
Is migration from Q360 free?
Yes. We import and map your Q360 exports, check them for duplicates, keep Q360 IDs, and build your sites, systems, contracts and schedules with you. You pay for Fieldproxy, not for the move. Plans are priced by monthly job volume with unlimited users; see the pricing page.
What can I export from Q360?
Solutions360 doesn't publish an export guide, so ask your account manager in writing for CSV or Excel files of customers and sites, installed equipment, contracts and recurring lines, PM schedules, open calls and projects, deficiencies and inventory, plus your inspection reports as files. Do it well before your notice date.
Does Fieldproxy replace Q360's accounting?
No. Fieldproxy is not a general ledger. Your books live in QuickBooks Online, QuickBooks Desktop or Enterprise, Xero or Sage, and Fieldproxy syncs two-way with them; exactly what syncs is agreed and tested during setup. If you want the ledger inside the same product, staying on Q360 may be the better choice.
Can I keep Q360 for accounting and use Fieldproxy for field work?
We don't recommend it as a long-term setup unless the two are connected, because customers, sites and invoices would be kept in two places. The common pattern is a short overlap: field work moves team by team, and billing and accounting move together at a month end.
Does the technician app work offline?
Q360's app is offline-first, so check this carefully. Tell us which sites have poor signal, such as basements, plant rooms and new builds, and we test the checklists, photos and signatures your technicians use there during the pilot before any other team moves.
Do AI agents answer service calls and chase approvals?
Yes. Fieldproxy's AI agents answer calls, texts and emails, log trouble calls against the right site and system, check whether the service plan covers the work, and chase unsigned agreements and unapproved deficiency quotes. They run on AI credits included in each plan, and every change an agent proposes can require a person to confirm.
Can ChatGPT or Claude work with my data?
Yes. Fieldproxy's official MCP server lets ChatGPT, Claude, Copilot and other assistants read your data and do anything the app can do, such as creating jobs, schedules, quotes and invoices, with a person confirming each change. We found no ChatGPT, Claude or MCP connection on Solutions360's pages; its AskQ assistant works inside Q360.
Can Fieldproxy block an alarm install from going live until the handoff is complete?
Yes. The site holds the zone list, call list with two numbers per contact, city permit number and central station account, and the install can't move to Live until each zone has been tripped on test and shows received. Closing the install starts the monthly monitoring charge on that date.

Leave Q360 without the leap. Live within a day.

A 30-minute call about how a job runs in your business, and a Q360 export. We show you your own setup and data running in Fieldproxy before you commit.

Plan my switch

Free, assisted migration. One price per company, unlimited users. Changes are a conversation.