FieldproxySwitching guide ยท sources checked 19 November 2026

How to switch from Syncta without missing a single purveyor deadline

Short answer: plan the move for your quiet season, not for notice season. Check your Syncta plan's billing term, then ask Syncta for CSVs of customers, properties, every assembly with its purveyor device number, test history with readings, and due dates. Save your filed reports as PDFs, and your tester certifications and gauge calibration certificates as files. Move one or two testers first, file real reports from the new system, and keep Syncta open until every test done in it has been filed and accepted.

With Fieldproxy, migration is free and assisted and you're live within a day: your first testers run real tests the day after the setup call, on forms built for your purveyors. Everyone else moves on a schedule you set. One price per company, with unlimited users, so plumbers, office staff and part-time testers all get a login.

Leaving Syncta? See your setup first

Send us a Syncta 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 Syncta, with the facts checked

Syncta was built by a backflow tester turned software engineer, and Watts, the valve and assembly maker, has owned it since 2018. Its strength is focus: the right readings on the right purveyor's form. Companies rarely leave because the test form is wrong. They leave because the business around the test has grown. Each point below was checked against Syncta's own pages on 19 November 2026.

Backflow is one line of a bigger business

When a failed RP needs a rebuild, or the same customer wants a water heater, an irrigation repair or a fire line job, the work often lands in a second system. Customers, technicians and invoices are then split in two. In Fieldproxy, tests, repairs, plumbing and fire line work share one customer, one property and one invoice, and a failed test can turn into a repair quote the owner approves from a link.

The bill grows with every tester

Syncta's help center lists three plans: per test ($25 monthly minimum, first five tests free, then $4.95 a test), per tester ($99 per tester per month, billed annually) and unlimited ($549 a month, billed annually). Those prices are from an August 2024 article, so confirm them. At six testers the per-tester plan is close to the unlimited one. Fieldproxy is one price per company, set by job volume, with unlimited users. See pricing.

source: Syncta help center: Syncta's plans (per test, per tester, unlimited)source: Syncta: backflow testers solution (features, plans)

Every purveyor has its own portal and fee

Reports go to BSI Online, SwiftComply, The Compliance Engine, VEPO or a city's own portal, and fees differ: Raleigh charges $9.95 per report through VEPO, Piqua, Ohio $15.95 through BSI Online. Offices often track filed, paid and accepted on a spreadsheet. In Fieldproxy each purveyor is a record with its form, portal, fee and deadline, and the office sees which reports are still unfiled.

source: Raleigh Water: certified tester VEPO go-live letter (filing fee per report)source: Piqua joins the BSI Online backflow community (filing fee per report)

A one-way invoice push into QuickBooks

Syncta's QuickBooks connection works with QuickBooks Online Plus or higher or QuickBooks Desktop 2013 or newer. Customers come in from QuickBooks and invoices go out to it; invoices created in QuickBooks don't come back. Fieldproxy syncs two-way with QuickBooks Online, Desktop and Enterprise, two-way with Xero, and deeply with Sage. Exactly what syncs is agreed and tested in setup.

source: Syncta help center: QuickBooks connection overview

Fire lines and property managers

Fire line assemblies carry NFPA 25 work beyond the annual backflow test, such as the forward flow test and the five-year internal inspection, and those are worth scheduling as their own tasks. Property managers with dozens of sites want one place to see every assembly, last result and next due date. Fieldproxy schedules each task on its own cycle and gives each client a portal scoped to its own sites.

source: PHCP Pros: inspecting and testing backflow preventers in fire protection systems (NFPA 25)

Notice season floods the phones

When purveyors mail their annual letters, the office gets a wave of โ€œI got a backflow letterโ€ calls. Fieldproxy's AI agents answer calls, texts and emails, find the assembly from the address or account number, and book the test inside the purveyor's window, with a person confirming where you want that. Through the Fieldproxy MCP server, Claude or ChatGPT can read your book and draft the week's route.

Stay on Syncta if

  • You are a one or two person shop that only tests backflow. Syncta's per-test plan will almost certainly cost less than Fieldproxy, and it is faster to start, since Fieldproxy is a guided setup, not a self sign-up.
  • Your purveyors run Syncta for their own programs. Tester and purveyor in the same system is a real advantage, so check how filing would work from elsewhere before you move.
  • You do a few hundred residential tests a year and nothing else. Fieldproxy is more system than you need.
  • The one-way QuickBooks push is enough for you, and you have no plumbing, repair or fire line work living in a second tool.
  • You are in the middle of notice season. Wait for the quiet months; a move in the busiest weeks helps nobody.
How Fieldproxy is set up for backflow testers

Before you go

What to export from Syncta, and how

The Syncta help center articles we read don't document a full data export, so ask Syncta support for each of the files below before you stop paying, and save any reports you can download yourself. Keep test history at least as long as your longest record rule: Texas asks for three years and Washington purveyors five.

DataHow to get it out of SynctaWhat happens to it in Fieldproxy
Customers and propertiesAsk Syncta for a CSV of customers and properties with contacts and billing addresses. If you use the QuickBooks connection, your customer list is also in QuickBooks.Owners, property managers and properties, with the bill-to kept separate from the service address.
AssembliesAsk for every assembly: type, make, model, size, serial, location, service, purveyor and purveyor device number.One record per assembly, not per address, each with a QR tag that opens its history and the right test form.
Test history and readingsAsk for test results with readings, tester, gauge and date, as a CSV, and save the filed reports as PDFs.Past tests attached to each assembly as history, so last year's readings are on the phone at the next test.
Due datesExport the due dates and check them against each purveyor's own notice, not only Syncta's calculation.The purveyor's due date and the earliest date a test counts, on each assembly, driving reminders and booking.
Open work orders, quotes and invoicesAsk for open work orders and repair quotes, and run an unpaid invoice list at cutover.Open repairs at the right stage; quotes the owner can approve from a link. Unpaid invoices are collected where they were raised.
Unfiled and rejected reportsList every test not yet filed or accepted by its purveyor.Finished and filed from Syncta before switch-off, so nothing has to be retyped into a portal.
Testers and gaugesSave each tester's certification card and each gauge's calibration certificate as files.Certification and calibration dates on each tester and gauge; a test can't close on an expired card or an overdue gauge.

source: Syncta help center: QuickBooks connection overviewsource: TCEQ Form 20700: Backflow Prevention Assembly Test and Maintenance Reportsource: Washington WAC 246-290-490: cross-connection control (records)source: Syncta help center: backflow test kit recalibration

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.

Purveyor form layouts

Syncta already knows many purveyor forms. Those layouts are Syncta's work and don't come with an export. Send us a filed report for each purveyor you work with, and we build each form in Fieldproxy before your testers use it.

source: Syncta: backflow testers solution (features, plans)

Filing inside a Syncta-run program

Some purveyors run Syncta for their own programs, so the tester and the program sit in the same system. If you move, check with each of those purveyors how you will submit from another system, and whether you need to register again.

source: Syncta: water purveyors solution

Portal accounts and registrations

Your logins on BSI Online, SwiftComply, VEPO or a city portal belong to your company, not to Syncta, and stay as they are. Re-check each one if anything about how you file changes.

QuickBooks history

Invoices already pushed to QuickBooks stay there. Only invoices Fieldproxy raises from the switch date flow through the new two-way sync, so turn off Syncta's connection for those first.

source: Syncta help center: QuickBooks connection overview

Do these before you cancel Syncta

  • Check your Syncta plan's billing term; the per-tester and unlimited plans are billed annually.
  • Ask Syncta support for every export in the table above, and keep the files somewhere you control.
  • Save filed reports as PDFs for at least as long as your strictest record rule.
  • Make sure every test done in Syncta has been filed and accepted by its purveyor.
  • Save tester certification cards and gauge calibration certificates, with their dates.
  • Ask any purveyor that runs Syncta how you will submit once you leave.
  • Turn off Syncta's QuickBooks connection for anything Fieldproxy now invoices.

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

Get Demo

Live within a day

The move from Syncta, 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 testers run real tests the day after the setup call, not that every purveyor form is ready at once. Many purveyors with different forms add time, and we say so on the first call.

What happens on go-live day
  1. 1

    Before the call: pick the quiet month and request the exports

    You, about an hour

    Many programs bunch tests into spring and summer (Longmont, for one, names April to August), so plan the cutover for late fall or winter. Ask Syncta for the exports and pick one or two testers to move first.
  2. 2

    The setup call: one assembly, from notice to filed report

    You and Fieldproxy

    Walk us through a test from the purveyor's letter to the accepted report: how you book, what the tester records, how repairs and retests work, where you file and what you invoice. Send a filed report for each purveyor.
  3. 3

    We build your setup

    Fieldproxy's team

    The assembly register, a purveyor rulebook (form, portal, fee, deadlines), test forms for RP, DC, PVB and SVB that check readings against pass marks, repair and retest on the same report, tester and gauge records, and invoices, on the web and the Android and iOS app.
  4. 4

    We move your data, free

    Fieldproxy's team and Fieldproxy AI

    Customers, properties, assemblies with purveyor device numbers, test history, due dates, open repairs, testers and gauges, mapped and checked for duplicates.
  5. 5

    We connect the books

    Fieldproxy's team, with your bookkeeper

    Two-way sync with QuickBooks Online, Desktop or Enterprise, or Xero, or the Sage link, checked against real invoices. Tap to Pay for homeowners who pay at the meter.
  6. 6

    Live: the first testers on Fieldproxy

    The day after the call

    One or two testers run real tests in Fieldproxy, scan the assembly tag, enter readings, take photos and file the report. Everyone else stays on Syncta for now.
  7. 7

    Weeks: compare, then move everyone

    Your schedule

    When each purveyor has accepted reports from Fieldproxy with no retyping, move the rest of the testers, switch on due-date reminders and owner notices, and close Syncta once the last report filed from it is accepted.

Cutover

Running Syncta and Fieldproxy side by side

For a short, dated window, both tools are open. Fieldproxy is there to replace Syncta, 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.

Split by tester, file each test once

A tester on Fieldproxy enters and files every test there; a tester still on Syncta stays there. Each test is entered and filed from one system only, so no purveyor gets a duplicate report and no fee is paid twice.

One system invoices and reminds

Agree which system invoices each customer during the overlap, and turn off reminders in the other, so a homeowner never gets two notices for the same assembly.

A fixed switch-off date

Close Syncta on a set date, after every report filed from it is accepted. The Watcher agent flags tests close to a purveyor deadline and reports not yet filed while the team is new to Fieldproxy.

The fear

What if a purveyor deadline falls in the middle of the move?

A late report can mean a fine for the customer or a water shut-off notice, and the purveyor won't care which software you were changing. This is how we keep deadlines safe during the switch.

  1. 1

    Move in the quiet months

    Cut over in late fall or winter, when few tests are due and gauges are at the lab, not in the weeks after the notices go out.
  2. 2

    Check each form before it counts

    We build each purveyor's form from a report it already accepted, and your first testers file real reports from Fieldproxy while the rest of the team stays on Syncta.
  3. 3

    Due dates carried over and checked

    Every assembly keeps its purveyor's due date. The office sees, per purveyor, what is due, tested, filed and accepted, from the first day.
  4. 4

    Syncta stays open until the last report is accepted

    Nothing is switched off until every test done in Syncta is filed and accepted, so you never lose the easy way to resubmit.

Where things live

Syncta terms and where they go in Fieldproxy

So testers and the office know where things went on the first morning.

In SynctaIn Fieldproxy
CustomersOwners and property managers, with properties under them
DevicesAssemblies with purveyor device number, due date and QR tag
Test reports on purveyor formsTest forms per assembly type and purveyor, readings checked against pass marks
Electronic submissionReport PDF in the purveyor's layout, with filing status, fee and acceptance tracked per purveyor
Routing and map viewScheduling by street and purveyor window, with routes and GPS check-in
Automated reminders and email notificationsDue-date reminders and owner notices by email and text, plus AI agents on phone, text and email
Work ordersRepair and retest jobs on the same assembly, with parts used
Quotes and invoicesRepair quotes the owner approves from a link; invoices with payment links and Tap to Pay
Customer portalClient portal scoped to each customer's or property manager's own sites
QuickBooks connection (one-way invoices)Two-way QuickBooks Online, Desktop and Enterprise; two-way Xero; Sage
Test kitsGauge records with calibration dates that block a test on an overdue gauge

Straight answers

Switching from Syncta: FAQ

How long does it take to switch from Syncta to Fieldproxy?
You're live within a day: your first testers run real tests the day after the setup call, with free, assisted migration. The rest moves on your schedule, usually once each purveyor has accepted reports from Fieldproxy. Plan the cutover for the quiet season.
Is Fieldproxy cheaper than Syncta?
Not for a one or two person backflow-only shop. Syncta's per-test plan has a $25 monthly minimum with the first five tests free, then $4.95 a test, and that is hard to beat. Fieldproxy fits companies with several testers, plumbing or fire line work, or a busy office. It is priced per company by job volume with unlimited users.
Is migration from Syncta free?
Yes. Migration to Fieldproxy is free and assisted: we import your Syncta exports, map customers, properties and assemblies with their purveyor device numbers, check for duplicates and build your purveyor forms.
Can I keep Syncta for test entry and use Fieldproxy for the rest?
Yes, as long as one system owns the customer and the invoice, so nothing is billed twice. Some companies do this for a season before moving testing too.
Does Fieldproxy work with QuickBooks, Xero and Sage?
Yes. Fieldproxy syncs two-way with QuickBooks Online, QuickBooks Desktop and Enterprise, and Xero, and connects deeply with Sage. Exactly what syncs is agreed and tested during setup.
Does the tester app work offline in a meter pit or basement?
Yes. Testers enter readings, take photos and capture signatures offline, and the test syncs when the phone has signal again.
Can AI answer the calls that come after purveyor notices go out?
Yes. Fieldproxy's AI agents answer phone calls, texts and emails, find the assembly from the address or account number, book the test inside the purveyor's window and send reminders. Any change can wait for a person to confirm.
Can I use ChatGPT or Claude with Fieldproxy?
Yes. Fieldproxy's official MCP server lets ChatGPT, Claude, Copilot and other assistants read your assemblies, tests and due dates and create or edit jobs, schedules, quotes and invoices, with a person confirming each change.
Will Fieldproxy stop a test with an expired certification or an overdue gauge?
It can be set up to. Each tester carries a certification expiry and each gauge a calibration date, and a test can be blocked from closing if either is out of date. Syncta's help center says kits are usually recalibrated yearly, or every six months under heavy use.

Leave Syncta without the leap. Live within a day.

A 30-minute call about how a job runs in your business, and a Syncta 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.