How to move off ADD Systems, or just its service side, without losing a single leak check or budget balance
Short answer: first decide whether ADD stays for deliveries and fuel billing. Many dealers should keep E3 and RAVEN and move only the service department, tank sets, leak checks and DOT records. Either way, read your ADD agreement for the term and notice date, and ask ADD in writing for CSVs of accounts, sites, tanks, contracts, equipment and open calls, because it publishes no export guide. Rebuild your leak check and service process, move service techs before drivers, move budget and pre-buy balances once at a reconciled cut-off outside the heating season, and keep ADD readable until a fixed date.
With Fieldproxy, migration is free and assisted and you're live within a day: your first service techs run real calls in Fieldproxy the day after the setup call, with your own job types, leak check record and gates. Everyone else moves on a schedule you set. One price per company, unlimited users, so seasonal drivers and CSRs never change the bill.
Leaving ADD Systems? See your setup first
Send us a ADD Systems export. We build your stages, forms and data in Fieldproxy, free, before you decide.
Why teams leave
Why teams leave ADD Systems, with the facts checked
ADD Systems has served fuel dealers since 1973 and says it has 500+ clients in 46 states. Its fuel back office is deep: budget, capped and pre-buy plans, credit, fuel inventory down to the van, and RAVEN in over 8,000 trucks. Dealers who look elsewhere are usually not unhappy with deliveries. They want the service side, the compliance records and the phones to work differently. Each point below was checked against ADD's own pages on 19 November 2026.
The service screens are ADD's, not yours
Pegasus does a lot: quotes, invoices, signatures, payment on site, photos and propane leak and pressure tests. Its page doesn't describe checklists you design, required photos, offline use or a gate that stops a call closing until the record is complete. We build those around your process: an odor call can't close without a leak check, a tank can't go In service until the pressure test and leak check are both on file, and each appliance relit gets its own line.
The out-of-gas record is the one that ends up in court
RAVEN can capture leak and pressure readings and a Gas Check. What matters is whether it happens every time. Iowa's rule has the driver shut and tag the valve on an out-of-gas fill until a qualified person checks, and LP Gas magazine's legal columnist warns that โleak check passedโ on a ticket isn't a defense. In Fieldproxy a zero gauge or a reported run-out opens a leak check record with method, start and end pressure, time held and gas in tank, or a shut-and-tagged record with a photo of the tag, before anything closes.
source: ADD Systems: RAVEN Mobile Delivery (over 8,000 deployed, leak and pressure tests, QR tank labels)source: Iowa Administrative Code 661-226.5 (out-of-gas shut and tag, leak check)source: LP Gas magazine, John McCoy, Servicing out-of-gas calls (2020)
DOT dates live on a clipboard
ADD's product pages don't describe driver hazmat training, CDL endorsements, monthly hose inspections or cargo tank test dates. Federal rules want hazmat training every three years and every delivery hose inspected each calendar month. We hold those as records with due dates: a route can't go to a driver whose training has lapsed, and a truck with an overdue hose check can't be loaded.
source: ADD Systems: ADD Energy E3 (payment plans, dispatching board, service sites, inventory, partner interfaces)source: 49 CFR 172.704, hazmat employee training (via Cornell LII)source: 49 CFR 180.416, delivery hose and discharge system inspection (via Cornell LII)
Nobody answers the 2 a.m. out-of-gas call but a person
ADD sends texts and emails when a truck or tech is dispatched, and SmartConnect lets you build a customer site. We found no phone, text or email agent and no ChatGPT or Claude connection on ADD's pages. Our AI agents answer the after-hours run-out or odor call, find the account, read your odor script, check the last fill and book the emergency job. Our MCP server lets ChatGPT, Claude and Copilot work on your data, with a person confirming each change.
source: ADD Systems: ADD Energy E3 (payment plans, dispatching board, service sites, inventory, partner interfaces)source: ADD Systems: SmartConnect web services (customer portal, tank monitor readings)
Delivery and service don't see each other
When service runs on paper or a separate tool, the tech on a no-heat call doesn't know the tank was filled from empty yesterday. In Fieldproxy the site holds the tank, the last fill, the out-of-gas flag and the last leak check, whether the fill came from our driver app or from ADD by account number.
source: ADD Systems: RAVEN Mobile Delivery (over 8,000 deployed, leak and pressure tests, QR tank labels)source: ADD Systems: Pegasus for service technicians
A price you only see in a quote
ADD doesn't publish pricing for its modules, handhelds or cloud option. We don't publish a dollar figure either, but the model is simple: one price per company by monthly job volume, unlimited users, AI credits included, migration free. See how plans work.
source: ADD Systems: homepage (ADD Energy E3, RAVEN, Pegasus, SmartConnect, ADD Cloud)
Stay on ADD Systems if
- Your fuel accounting lives in E3: fuel taxes, multi-product inventory, transport and many budget and pre-buy accounts. Keep ADD for that. Fieldproxy is not a general ledger, and adding us for service is the better move than ripping out your back office.
- Your drivers are settled on RAVEN with metered registers, QR tank labels and printers in every truck. There is no need to touch the delivery side to fix the service side.
- You value an independent, family-led vendor that has been in the fuel business since 1973 and want to stay with it.
- Your Pegasus setup already gives you the leak check and service records you need and your techs trust it. Don't move to fix a problem you don't have.
- It's December or January. Plan the change now and make it after the heating season.
Before you go
What to export from ADD Systems, and how
ADD doesn't publish an export guide, so treat each row as a written request to your ADD account manager: ask for a CSV or Excel file with ADD account and site numbers kept, so records can be matched. If ADD is staying for deliveries, you only need the service rows, and the account number becomes the link between the two systems.
| Data | How to get it out of ADD Systems | What happens to it in Fieldproxy |
|---|---|---|
| Accounts, sites and contacts | Ask ADD for a CSV of accounts, delivery and service sites, and contacts, with ADD account numbers. | Customers and sites, with the ADD account number kept so service and delivery stay matched. |
| Tanks and K-factors | Ask for each tank: owner, serial, size, K-factor, daily use, reorder level, will-call or automatic, monitor ID. | Tank assets on each site with a QR code. If ADD keeps deliveries, the forecast stays in ADD and we hold the tank for service. |
| Delivery history | Ask for the last two seasons of fills per tank, with gallons, date and gauge readings where held. | Shown on the site so techs see the last fill; used to check K-factors if delivery moves too. |
| Budget, capped and pre-buy contracts | Ask for each contract: type, price, gallons, monthly amount, start, end and balance at cut-off. | Only if billing moves: contracts with balances drawn down per delivery and a year-end true-up. Otherwise they stay in ADD. |
| Service contracts and tune-ups | Ask for each plan with last and next due tune-up dates. | Recurring tune-ups generated on their existing due dates, so the cycle carries on unbroken. |
| Equipment per site | Ask for furnaces, boilers, water heaters, generators and regulators per site, with install dates. | Appliances with BTU input on the site, so leak checks and relights list each one. |
| Leak check and pressure test history | Ask how RAVEN and Pegasus readings can be exported; keep scanned paper records too. | Attached to each site's history, so the record you may need in a claim stays with the tank. |
| Open service calls and quotes | Ask for open calls with status, and open quotes, at cutover. | Open calls land at the right stage; quotes can be approved by the customer from a link. |
| Open receivables and payment methods | Run an AR aging at cutover and ask which card and EFT details can be exported. | Open invoices stay in your accounting system. Saved card and bank details usually can't move, so customers re-authorize. |
source: ADD Systems: ADD Energy E3 (payment plans, dispatching board, service sites, inventory, partner interfaces)source: ADD Systems: RAVEN Mobile Delivery (over 8,000 deployed, leak and pressure tests, QR tank labels)source: ADD Systems: Pegasus for service technicianssource: ADD Systems: SmartConnect web services (customer portal, tank monitor readings)
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.
Fuel accounting and its rules
Fuel taxes, product pricing rules, credit terms, dunning letters and the posting setup are E3 settings, not data. If ADD stays, they stay. If you switch fully, your accountant sets the books up in QuickBooks, Xero or Sage at a month end and we agree and test what syncs.
source: ADD Systems: ADD Energy E3 (payment plans, dispatching board, service sites, inventory, partner interfaces)source: ADD Systems: ADD Financials (Dynamics 365 Business Central, Dynamics GP; clients on QuickBooks, Sage and others)
Truck hardware and partner interfaces
RAVEN's register and printer links, routing and mapping partners, card processors, cardlock networks and tank monitor interfaces are set up per vendor. List the ones you use. Tank monitors that report through an API can feed Fieldproxy; registers and printers in the trucks are agreed on the call.
source: ADD Systems: ADD Energy E3 (payment plans, dispatching board, service sites, inventory, partner interfaces)source: ADD Systems: RAVEN Mobile Delivery (over 8,000 deployed, leak and pressure tests, QR tank labels)
Your SmartConnect customer site
A customer site built on SmartConnect web services talks to E3. If billing moves, customers use a Fieldproxy portal or links for balances, fill and service requests, approvals and payments instead, and you redirect the old pages.
source: ADD Systems: SmartConnect web services (customer portal, tank monitor readings)
Dispatch rules and reports
Datebook settings, dispatcher alerts and Atlas reports are configuration. Write down the alerts and reports your managers read each week, and we rebuild them as automations and dashboards.
source: ADD Systems: ADD Energy E3 (payment plans, dispatching board, service sites, inventory, partner interfaces)source: ADD Systems: homepage (ADD Energy E3, RAVEN, Pegasus, SmartConnect, ADD Cloud)
Do these before you cancel ADD Systems
- Decide what you're cancelling: the whole of ADD, or only Pegasus and the service side. Many dealers should keep E3 and RAVEN.
- Read your ADD agreement for the term, notice period and renewal date, and get anything unclear in writing.
- Send ADD a written export request listing every row in the table above, and open each file when it arrives.
- Export every leak check and pressure test record you hold, and keep them for as long as your insurer advises.
- If billing moves, reconcile budget and pre-buy balances at one cut-off date and have the customer statements match.
- Ask autopay customers to re-authorize before the first bill from the new system.
- Keep read-only access to ADD until after your year-end close.
Send us your ADD Systems export and see it running in your setup.
Get DemoLive within a day
The move from ADD Systems, 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 calls, not that the whole company has moved. Moving deliveries, fuel billing and budget balances off ADD takes longer and is best done outside the heating season; we say how long on the first call.
What happens on go-live day- 1
Before the call: decide what moves
You and your service manager, about an hour
Decide whether ADD stays for deliveries and billing. Find the term date. Send the export request. Pick the first team, usually two service techs, and note which states you deliver in so we set up their out-of-gas and leak check rules. - 2
The call: one out-of-gas fill and one service call, end to end
You and Fieldproxy, 30 minutes
Walk us through a recent out-of-gas fill, the leak check that followed, a tank set and a no-heat call. Send a sample leak check form, a delivery ticket, a hose inspection sheet and any exports you already have. - 3
We build your setup
Fieldproxy's team
Sites, tanks, regulators and appliances; the leak check record and the out-of-gas gate; tank set and piping test checklists; service job types; driver, truck, hose and cylinder records; and the screens each role sees on the web and the iOS and Android app. - 4
We move your data, free
Fieldproxy's team and Fieldproxy AI
Accounts, sites, tanks, equipment, service contracts and open calls, mapped and checked for duplicates, with ADD account numbers kept. Tune-ups keep their next due dates and leak check history attaches to each site. - 5
We connect the books
Fieldproxy's team, with your bookkeeper
Service invoices sync two-way with QuickBooks Online, Desktop or Enterprise, Xero or Sage, or are handed to ADD if it stays your billing system. Tested with real invoices before anyone depends on it. - 6
Live: the first techs run real calls
The day after the call
The pilot techs work in the Fieldproxy app: site history, last fill, leak check record, relight list, photos and signatures. Drivers and everyone else stay on ADD until their turn. - 7
Weeks or months: service first, delivery only if you choose
Your schedule
Move the rest of the service department, then load DOT records. If you're switching fully, move drivers route by route after the heating season and move budget and pre-buy balances at one reconciled cut-off.
Cutover
Running ADD Systems and Fieldproxy side by side
For a fuel dealer the overlap can be permanent by design: ADD keeps deliveries and billing, Fieldproxy runs service and compliance. If you're moving everything, the overlap is a season, not a weekend.
One system per job, one link per customer
A service call or tank set is worked in Fieldproxy or in Pegasus, never both. Every site carries its ADD account number, so a delivery in ADD and a leak check in Fieldproxy land on the same customer.
Balances move once
If billing moves, budget and pre-buy balances are taken at one reconciled cut-off, checked against customer statements, and only then drawn down in Fieldproxy. Until that date, ADD bills.
A fixed switch-off date for what's leaving
Agree the date Pegasus, or all of ADD, becomes read-only. While the team is new, the Watcher agent flags out-of-gas fills with no leak check, drivers whose training is due and hoses past their monthly check.
The fear
What if a customer runs out mid-switch and the leak check falls through the cracks?
The out-of-gas call is where a dealer's liability sits, and a switch is exactly when a step gets missed. This is how we keep it from happening.
- 1
Deliveries don't move first
Service techs move first and drivers stay on RAVEN, so the fills and the forecast don't change while the service side settles in. - 2
A run-out always becomes a job
Whichever system recorded the fill, a zero gauge or reported run-out creates an urgent leak check job in Fieldproxy, and the Watcher agent alerts the service manager if none is booked. - 3
The record can't close half-done
The leak check needs method, start and end pressure, time held and gas in tank, or a shut-and-tagged record with a tag photo, before the job closes. - 4
After-hours calls are answered
The Calling agent can take run-out and odor calls at night with your odor script, book the job and page the on-call tech, whichever system holds the account.
Where things live
ADD Systems terms and where they go in Fieldproxy
So your office, drivers and techs know where things went on day one. What stays in ADD is agreed on the call.
| In ADD Systems | In Fieldproxy |
|---|---|
| ADD Energy E3 accounts and service sites | Customers and sites with the ADD account number kept |
| Tank records | Tank assets with owner, serial, capacity, setbacks and a QR code |
| Automatic delivery forecast (K-factor) | Stays in ADD, or per-tank K-factor, daily use and reorder level if delivery moves |
| RAVEN delivery ticket | Stays in ADD, or driver ticket with gauge readings and the out-of-gas gate |
| RAVEN and Pegasus Gas Check, leak and pressure tests | Leak check record with method, pressures, time held and relight list |
| Pegasus work orders | Service jobs by type: no heat, tune-up, odor, regulator, generator, oil line upgrade |
| Datebook and dispatching board | Scheduling by skill and certification, with emergency odor calls first |
| Budget, capped and pre-buy plans | Stays in ADD, or contracts with balances and year-end true-up if billing moves |
| SmartConnect customer site | Customer portal and no-login links for approvals, sign-off, reports and payments |
| Pegasus quotes and on-site payment | Quotes approved from a link; Tap to Pay in the field |
| ADD Financials | No ledger in Fieldproxy: books in QuickBooks Online, Desktop or Enterprise, Xero or Sage |
| Not on ADD's pages | Driver, truck, hose and cylinder records; AI agents; MCP for ChatGPT, Claude and Copilot |
Straight answers
Switching from ADD Systems: FAQ
Should I replace ADD Systems or keep it?
How long does it take to switch from ADD to Fieldproxy?
Is migration from ADD free?
What can I export from ADD Systems?
Does Fieldproxy work with QuickBooks, Xero or Sage?
Does the app work where there's no signal?
Can AI agents take out-of-gas and odor calls?
Can ChatGPT or Claude work with my data?
Can Fieldproxy stop a ticket closing without a leak check?
Sources
Where the facts on this page come from
Every ADD Systems fact links to ADD Systems'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 propane and heating oil dealers.
- source: ADD Systems: homepage (ADD Energy E3, RAVEN, Pegasus, SmartConnect, ADD Cloud)
- source: ADD Systems: History (incorporated 1973, 500+ clients in 46 states, 150+ employees)
- source: ADD Systems: Celebrating 50 Years
- source: ADD Systems: ADD Energy E3 (payment plans, dispatching board, service sites, inventory, partner interfaces)
- source: ADD Systems: RAVEN Mobile Delivery (over 8,000 deployed, leak and pressure tests, QR tank labels)
- source: ADD Systems: Pegasus for service technicians
- source: ADD Systems: SmartConnect web services (customer portal, tank monitor readings)
- source: ADD Systems: ADD Financials (Dynamics 365 Business Central, Dynamics GP; clients on QuickBooks, Sage and others)
- source: Iowa Administrative Code 661-226.5 (out-of-gas shut and tag, leak check)
- source: LP Gas magazine, John McCoy, Servicing out-of-gas calls (2020)
- source: 49 CFR 172.704, hazmat employee training (via Cornell LII)
- source: 49 CFR 180.416, delivery hose and discharge system inspection (via Cornell LII)
Leave ADD Systems without the leap. Live within a day.
A 30-minute call about how a job runs in your business, and a ADD Systems 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.