How to switch from ServiceCore without losing a single tank, lid pin or pump-out reminder
Short answer: find your ServiceCore renewal date first. It bills monthly, but on an annual contract, so the term end is your real deadline. Before it, run the completed-jobs export for every year you may be audited on, save the pump reports and manifests attached to customers, and ask ServiceCore support for CSVs of customers, tanks, grease traps, recurring schedules and open invoices. Rebuild your state pump-out form and trip ticket, move one septic route at a time (ideally in the slow season), and keep ServiceCore readable until your last annual hauler report is filed.
With Fieldproxy, migration is free and assisted and you're live within a day: your first truck runs real pump-outs in Fieldproxy the day after the setup call, with its own tank records, readings form and load tickets. Every other route, and your grease and portable work, moves on a schedule you set. One price per company with unlimited users, so a new dispatcher or a seasonal driver never changes the bill.
Leaving ServiceCore? See your setup first
Send us a ServiceCore export. We build your stages, forms and data in Fieldproxy, free, before you decide.
Why teams leave
Why teams leave ServiceCore, with the facts checked
ServiceCore is a serious product for this trade. It keeps a record per tank with the lid pinned on a map, turns your state form into a phone form drivers can fill without signal, reports gallons dumped by plant, and is staffed by people who have run routes themselves. Its office users are free and it is priced per truck. Pumpers who leave it usually have not outgrown the tank record. They want the software to own more of the paper trail, or they want different terms. Each point below was checked against ServiceCore's own pages on 19 November 2026.
You want the next pump-out set by the readings, not the calendar
ServiceCore sets recurring pump-outs once per job type (every year up to every 5 years) or from the tech's recommended date. The regulators' triggers are measured: EPA says pump when scum is within 6 inches of the outlet, sludge within 12 inches, or the two together pass 25% of liquid depth, and Minnesota writes the same 25% and 12-inch tests into its rule. In Fieldproxy the driver records scum depth, sludge depth and liquid level before the hose goes in, and the tank's next due date is projected from how fast it actually fills. The six-tenant rental gets called back sooner; the retired couple's tank stops being pumped half empty.
source: ServiceCore: septic business softwaresource: US EPA: how to care for your septic systemsource: Minnesota Rule 7080.2450, SSTS maintenance triggers
Regulators read the load, and you want a load record
ServiceCore captures gallons and the dump site on each job and reports gallons dumped by plant. When several stops fill one truck, though, the trip ticket, the plant's receiving ticket and the fee belong to the load. Some plants even bill on the truck's capacity rather than what was dumped (Fairfax County charges per 1,000 gallons of truck capacity). We set up a Load in Fieldproxy: stops and gallons roll into it, the driver photographs the receiving ticket, our Vision agent reads it, and a gallons mismatch is flagged before month end. Texas haulers get their TCEQ-00316 totals by waste type and receiver straight from the year's loads.
source: ServiceCore: septic business softwaresource: Fairfax County, VA: hauled wastewater chargessource: TCEQ: sludge transporter reporting (TCEQ-00316)
Land application and transfer inspections need their own tracks
If you spread septage on your own fields, EPA Part 503 asks for the site, acres, rate, how pathogens and vector attraction were handled (for example pH 12 held for 30 minutes) and a signed certification, kept five years. A Massachusetts Title 5 inspection has a 30-day deadline to reach the Board of Health. ServiceCore lists a mortgage inspection job type and keeps past reports with the address; we found no land application log on its septic page. In Fieldproxy a land application load cannot close without its pH readings and certification, and each transfer inspection carries the closing date, the agents and the filing deadline.
source: ServiceCore: septic business softwaresource: 40 CFR 503.17, land application recordkeepingsource: 40 CFR 503.33, vector attraction reductionsource: 310 CMR 15.301, Title 5 inspection at transfer of title
Terms: a quote after a demo, an annual contract, a setup fee
ServiceCore's pricing page asks for a demo before it shows a price, bills monthly on an annual contract, and adds a one-time implementation fee for moving data and training. Its FAQ says onboarding typically takes 6 to 12 weeks. None of that is unusual, but it is a lot to commit before you have seen your own route run. With Fieldproxy, migration is free, your first truck is live the day after the setup call, and the price is set by job volume with unlimited users. See pricing for how plans work.
source: ServiceCore pricing (Grow and Pro, annual contract, implementation fee)source: ServiceCore software FAQs (onboarding, QuickBooks, support contacts)
The office runs on something other than QuickBooks Online
ServiceCore's septic and grease pages say customers, invoices and payments sync with QuickBooks Online. If your bookkeeper works in QuickBooks Desktop or Enterprise, Xero or Sage, Fieldproxy syncs two-way with all of them (Sage deeply: invoices, bills, credit notes and suppliers), and exactly what syncs is agreed and tested during setup. Fieldproxy is not a ledger, so the books stay where they are.
source: ServiceCore: septic business softwaresource: ServiceCore: grease trap pumping software
Backups come in at night, by phone
ServiceCore sends on-the-way texts, adds two-way SMS and an online booking portal on Pro. It does not list agents that answer the phone or a connector for ChatGPT or Claude. Our Calling agent can answer the 9 pm call about a basement drain, find the property and its tanks, ask the backup questions and open an emergency job, and our MCP server lets an owner ask ChatGPT, Claude or Copilot which tanks are due this quarter. Every change an agent or assistant proposes can require a person to confirm.
source: ServiceCore pricing (Grow and Pro, annual contract, implementation fee)source: ServiceCore homepage (industries, Satellite Sense, per-truck pricing note)
Stay on ServiceCore if
- Most of your revenue is portable restrooms, you buy Satellite equipment, and you want Satellite's sensors wired into your software. That is an exclusive ServiceCore partnership and we do not have it.
- You are mid-term on the annual contract. Build and test with us now, and set the switch for the renewal date rather than paying twice for months.
- Your state forms already work as ServiceCore phone forms, you do not land-apply, QuickBooks Online is your ledger, and your recurring reminders are not leaking work. Don't switch to fix a problem you don't have.
- You run roll-off on Docket, also a ServiceCore company, and value one vendor across both. Moving septic alone would split your stack in a new place.
- You want a US support team made up of former operators who know what a riser is. ServiceCore makes that its headline, and it is a fair reason to stay.
Before you go
What to export from ServiceCore, and how
ServiceCore's help center needs a login and we found no public article that describes a full data export. Two routes are documented on its own site: its septic page says everything completed in a date range can be exported for an audit, and its reports show gallons pumped and gallons dumped by treatment plant, zip or town. For the rest, ask ServiceCore support for CSVs (its FAQ lists 1-888-691-1333 and support@servicecore.com), and get them well before your annual term ends.
| Data | How to get it out of ServiceCore | What happens to it in Fieldproxy |
|---|---|---|
| Customers and billing contacts | Ask ServiceCore support for a CSV of customers with billing addresses, contacts, billing preference (email or print) and terms. | Owners, property managers, HOAs and restaurant groups, each with who pays and how they want invoices. |
| Tanks and septic details | Ask for a CSV of every tank field you use: size, material, install year, lid pin coordinates, hose length, gate code, digging depth, risers, filters, bedrooms and occupants. | One Tank record per tank under the property, lid pins kept, with drivers confirming lids on the first visit. |
| Grease traps and permits | Ask for a CSV of trap records (inside or outside, size, hose, access window) and download the FOG permits attached to each account. | Each device carries its permit frequency, its utility's rule and the portal deadline; permits attached. |
| Completed jobs and gallons | Run the date-range export of completed jobs for every year your state may audit (five years in several states). | Loaded as tank history so last pump-out dates and gallons are there on day one; the export file is kept as an archive. |
| Pump reports, manifests and county logs | Download the PDFs saved to each customer for the period you must keep, and a blank copy of each state form you uploaded. | Attached to each tank or trap; the blank forms are rebuilt field for field as phone forms with required fields. |
| Recurring schedules and due dates | Ask for a CSV of recurring jobs with interval and next due date per tank or trap, and print the customers-due report. | Next due dates loaded so no reminder lapses; readings from new visits then refine each tank's date. |
| Gallons by plant | Run the gallons dumped by treatment plant report for the current reporting year. | Opening totals per plant and waste type, so this year's state report adds up across both systems. |
| Open invoices, payments and autopay customers | Export open invoices and reconcile them against QuickBooks Online, and list customers on autopay or cards on file. | Open balances moved; autopay customers re-authorize through a payment link, since stored cards stay with the processor. |
| Price book | Ask for the service and charge list: base pump-out, extra gallons, hose, digging, risers, area and customer pricing. | Invoice lines and customer-specific rates, priced by the office, added by drivers on site. |
source: ServiceCore: septic business softwaresource: ServiceCore: grease trap pumping softwaresource: ServiceCore software FAQs (onboarding, QuickBooks, support contacts)
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 forms as configured
The phone versions of your manifest, pump report and county log are built inside ServiceCore. Their data comes out as PDFs and job fields, but the form itself does not. Keep a blank of each state form and a filled example, and we rebuild them with the same required fields.
Routes and optimization settings
Route days, dump stops dragged onto routes and optimization settings are how you run, not records. Print one week of routes per truck before you leave, and we set up the same route days with disposal stops placed by tank capacity.
Payments and stored cards
ServiceCore offers its own payment processing, and stored cards and autopay set-ups stay with the processor. Plan to send autopay customers a payment link to set up again, and stagger it so they are not all asked in one week.
source: ServiceCore software FAQs (onboarding, QuickBooks, support contacts)
Portal logins, sensors and the QuickBooks link
Customer portal accounts on Pro, any Satellite sensor feed, and the QuickBooks Online sync all stop with ServiceCore. List who uses each one. Your QuickBooks file keeps its history; the new sync starts from the cutover date.
source: ServiceCore pricing (Grow and Pro, annual contract, implementation fee)source: ServiceCore: Satellite Industries partnership FAQ
Do these before you cancel ServiceCore
- Find the annual contract term end and the notice period, and diarize the notice date.
- Run the completed-jobs export by date range for every year your state can audit, and check the files open.
- Download the pump reports, manifests and FOG paperwork attached to customers for the same period.
- Get CSVs of customers, tanks, grease traps, recurring schedules, open invoices and the price book.
- Run the gallons-by-plant report for the current reporting year, so your annual hauler report can be completed.
- List autopay customers, portal users and anything fed by the QuickBooks Online sync.
- Keep read access until the last state or county report that depends on ServiceCore data is filed.
Send us your ServiceCore export and see it running in your setup.
Get DemoLive within a day
The move from ServiceCore, 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 truck runs real jobs the day after the setup call, not that every route moves at once. Large fleets, land application sites and several states add time, and we say so on the first call. Many pumpers move the rest in the slow season.
What happens on go-live day- 1
Before the call: contract date, exports, pilot truck
You, about an hour
Find your renewal date, start the exports, and pick a pilot: one septic truck and its route, ideally one that dumps at a plant with receiving tickets. Have a blank state form, a filled pump report and a sample invoice to hand. - 2
The setup call: one tank, one load, one report
You and Fieldproxy, 30 minutes
Walk us through a real pump-out from the call to the invoice: how you find the lids, what the driver measures, where the load goes, what the plant gives you back, which form the state or county wants, and how you invoice extra hose or digging. - 3
We build your setup
Fieldproxy's team
Tank records with lid pins, the pump-out form with scum, sludge and level readings, job types and statuses, loads with trip tickets and receiving tickets, your plants and their fees, and the screens each role sees on the web and the Android and iOS app. - 4
We move your data, free
Fieldproxy's team and Fieldproxy AI
Customers, properties, tanks and traps mapped from your ServiceCore CSVs and checked for duplicates. Completed jobs loaded as history, PDFs attached, and next due dates set so reminders carry on without a gap. - 5
We connect the books
Fieldproxy's team, with your bookkeeper
Two-way sync with QuickBooks Online, Desktop or Enterprise, Xero or Sage, tested on a real day of invoices and payments before anyone relies on it. - 6
Live: the first truck runs real pump-outs
Day one
The pilot driver opens each tank on the Fieldproxy app, records readings and gallons, photographs the lids and the receiving ticket, and the office invoices from the completed job. Every other truck stays on ServiceCore. - 7
Weeks or months: route by route, then switch off
Your schedule
After a clean week, move the next route. Grease stops and portables follow when you choose. When the last route has moved and the year's report is filed, take final exports and let the ServiceCore term end.
Cutover
Running ServiceCore and Fieldproxy side by side
For a short, dated window, both tools are open. Fieldproxy is there to replace ServiceCore, 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.
Each route and each tank lives in one system
A route that has moved books, pumps, reminds and invoices only in Fieldproxy; one still on ServiceCore stays there. No tank gets two reminders and no homeowner two invoices.
Loads stay whole
A truck runs a whole day in one system, so every load, trip ticket and receiving ticket is complete in one place. Annual totals are the sum of both systems for the overlap year, which is why the gallons-by-plant report comes out before you start.
A fixed switch-off date
Keep ServiceCore readable, not in use, until the contract term ends and the year's report is filed. Meanwhile the Watcher agent flags loads missing a receiving ticket and reports near their deadline while the team is new to Fieldproxy.
The fear
What if a pump-out reminder or a grease pump-out slips during the move?
Recurring work is most of a pumper's revenue, and grease stops have deadlines set by the city or the utility (JEA in Jacksonville wants reports within 5 days). The risk in any move is a due date that lives in neither system. This is how we close that gap.
- 1
Due dates move before routes do
We load every tank's and trap's next due date from your export on day one and check a sample against ServiceCore's customers-due report, so nothing depends on which system a route is in. - 2
Grease moves as a block, not stop by stop
Grease devices move together, with each permit's frequency and each utility's portal deadline, and the next stop counts from the last actual pump date in your export. - 3
One weekly due list across both systems
During the overlap, the office gets one Monday list: tanks and traps due in the next 30 days, which system each is in, and whether it is booked. - 4
One truck at risk, not the company
Only the pilot truck moves first. If a form field or a plant fee is missing, one driver finds it and every other truck keeps running on ServiceCore until you decide.
Where things live
ServiceCore terms and where they go in Fieldproxy
So the office and drivers know where things went on the first day. Anything not listed is agreed on the setup call.
| In ServiceCore | In Fieldproxy |
|---|---|
| Customer record | Customer with properties, who pays, billing preference |
| Tank record (lid pin, hose, gate code, size) | Tank record with lids from two fixed points, pin, photos, well distance, compartments |
| Pumping frequency by job type | Next due date projected from scum and sludge readings, with a fallback interval |
| Gallons pumped and dump site per job | Gallons per compartment, rolled into a Load with trip ticket, plant and receiving ticket |
| Uploaded state form, manifest or county log | The same form rebuilt with required fields, PDF in your layout |
| Gallons dumped by plant report | Totals by plant and waste type from loads, including the TCEQ-00316 layout |
| Mortgage inspection job type | Transfer inspection track with closing date, agents and the filing deadline |
| Grease trap record and FOG permit | Grease device with permit frequency, utility rule, sludge judge reading and portal deadline |
| Dump stop on the route | Disposal stop placed by the truck's tank capacity |
| Pro customer portal | Links without a login to approve, sign, view reports and pay; portals per property manager or restaurant group |
| ServiceCorePAY and autopay | Payment links, Tap to Pay in the truck, recurring billing for service contracts |
| QuickBooks Online sync | Two-way QuickBooks Online, Desktop and Enterprise, Xero or Sage |
Straight answers
Switching from ServiceCore: FAQ
How long does it take to switch from ServiceCore to Fieldproxy?
Is migrating from ServiceCore free?
What can I export from ServiceCore?
Can I keep ServiceCore for portable restrooms and move septic to Fieldproxy?
Does Fieldproxy work with QuickBooks, Xero and Sage?
Does the driver app work on rural roads with no signal?
Can AI agents answer after-hours backup calls?
Can ChatGPT or Claude work with my pumping data?
Can Fieldproxy produce the Texas Annual Summary Report and Minnesota pumping records?
Sources
Where the facts on this page come from
Every ServiceCore fact links to ServiceCore'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 septic and portable toilet companies.
- source: ServiceCore homepage (industries, Satellite Sense, per-truck pricing note)
- source: ServiceCore: septic business software
- source: ServiceCore: grease trap pumping software
- source: ServiceCore pricing (Grow and Pro, annual contract, implementation fee)
- source: ServiceCore software FAQs (onboarding, QuickBooks, support contacts)
- source: ServiceCore: Satellite Industries partnership FAQ
- source: Mainsail Partners (Feb 2022): ServiceCore announces $54M investment
- source: Mainsail Partners case study: ServiceCore acquires Docket (2023)
- source: US EPA: how to care for your septic system
- source: Minnesota Rule 7080.2450, SSTS maintenance triggers
- source: Minnesota Rule 7083.0770, pumping record and 30-day deadline
- source: TCEQ: sludge transporter reporting (TCEQ-00316)
- source: 40 CFR 503.17, land application recordkeeping
- source: 40 CFR 503.33, vector attraction reduction
- source: 310 CMR 15.301, Title 5 inspection at transfer of title
- source: JEA: FOG certified hauler program (5-day reporting)
- source: Fairfax County, VA: hauled wastewater charges
Leave ServiceCore without the leap. Live within a day.
A 30-minute call about how a job runs in your business, and a ServiceCore 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.