How to switch from CRO Software without a single unit missing its weekly service
Short answer: ask CRO or RapidWorks for your renewal date and notice terms in writing first. Then ask CRO support for CSV exports of customers, sites, units and containers, active rentals, routes, open jobs and invoices (CRO publishes no self-serve export guide, but its switching page says your data belongs to you). Rebuild your units and rentals with their billing start dates, move one truck's route at a time after a billing batch, and keep CRO readable until a fixed date.
With Fieldproxy, migration is free and assisted and you're live within a day: your first team runs real jobs the day after the setup call, with its own units, stops and driver checklists. Every other route moves on a schedule you set. One price per company, unlimited users, so adding a dispatcher or a seasonal driver never changes the bill.
Leaving CRO Software? See your setup first
Send us a CRO Software export. We build your stages, forms and data in Fieldproxy, free, before you decide.
Why teams leave
Why teams leave CRO Software, with the facts checked
CRO is a capable product. It runs portables, roll-off, septic and scrap on one dispatch board, routes pump trucks to the nearest pump-out, and doesn't charge per office user. Most operators who leave it aren't unhappy with the board. They're reacting to a change of owner, or they've hit a gap in how a rental business bills and proves its work. Each point below is checked against CRO's and RapidWorks' own pages on 19 November 2026.
The owner changed, and so did the owner's CEO
RapidWorks bought CRO on 1 October 2025. Its release says CRO keeps its product identity and keeps serving its customers, and that is a fair promise to take at face value. But CRO is now one of several RapidWorks products built mostly for concrete pumping, hydrovac and crane work, and in September 2026 RapidWorks named a new CEO. A product's roadmap follows its owner. Fieldproxy is set up around your process: the screens, statuses and forms are built for your yard and routes, not inherited from another trade.
source: RapidWorks (1 Oct 2025): RapidWorks acquires CRO Softwaresource: RapidWorks (25 Sep 2026): Matt DePaolis appointed CEOsource: RapidWorks: portable sanitation industry page
28-day rent isn't named on CRO's pages
CRO's pages describe recurring billing, pre-billing and billing daily. None of the pages we read mention 28-day cycles, per-unit anniversaries or proration, and ServiceCore's benchmark found 83% of portable operators bill every 28 days. In Fieldproxy every rental line carries its own start date, bills on its own anniversary, prorates the first and last partial cycle, and a weekly batch picks up every anniversary that fell that week.
source: RapidWorks: CRO product page (features, pricing model)source: RapidWorks: CRO software for portablessource: ServiceCore: 28-day billing vs monthly billing
Accounting stops at QuickBooks
CRO syncs customers, products and invoices with QuickBooks Online and Desktop, and that is a real strength for Desktop users. It doesn't list Xero or Sage, and one review CRO shows on its own homepage says the QuickBooks web connector needs frequent work with the reviewer's IT firm. Fieldproxy syncs two-way with QuickBooks Online, Desktop and Enterprise, Xero and Sage, and exactly what syncs is agreed and tested during setup.
source: RapidWorks: CRO product page (features, pricing model)source: CRO Software homepage (industries, pricing terms, reviews)
Quotes sized by hand
A 35-worker site serviced weekly needs 4 units under ANSI/PSAI Z4.3, against the OSHA minimum of 1 seat and 1 urinal. CRO doesn't list a sizing calculator. We put one on the quote: Z4.3 counts from peak workers and service frequency, the PSAI event chart with an allowance for alcohol, 5% ADA units per cluster and hand wash stations, with the basis printed so the contractor sees why.
source: ANSI/PSAI Z4.3-2016, Portable sanitation at work sitessource: RapidWorks: CRO product page (features, pricing model)
Manifests by jurisdiction, not just gallons
CRO's pump trucks log gallons and route to the nearest pump-out, which helps. Receiving plants want more: UOSA in Virginia wants a complete manifest per load, the deodorizer's safety data sheet, and only takes waste from listed jurisdictions. Land application records must be kept five years. In Fieldproxy each load is a record with the plant, permit, gallons by originating county, manifest number and a receipt photo, and a missing manifest at day's end becomes a task for the driver.
source: RapidWorks: CRO product page (features, pricing model)source: UOSA septage receiving facility registration and rules (2027)source: 40 CFR 503.17, recordkeeping
Calls, texts and assistants
Event planners still phone at 9 pm to ask for 40 units. We found no AI call or email agents, and no ChatGPT or Claude connector, on CRO's pages. Fieldproxy's AI agents answer calls, texts and emails, ask the sizing questions, check availability and leave a draft quote for a person to approve. Our MCP server lets ChatGPT, Claude and Copilot work with your data, with a person confirming each change.
source: RapidWorks: CRO product page (features, pricing model)source: CRO Software homepage (industries, pricing terms, reviews)
Stay on CRO Software if
- You run roll-off, portables, septic and scrap together and CRO's single board works for your dispatchers. That breadth is CRO's strength. Ask us to show the same mix on a call before you decide.
- RapidWorks has given you its CRO roadmap and renewal terms in writing and you're comfortable with both.
- You value no sign-up contracts and no setup fees, which CRO's homepage states. We don't charge for migration either, but we start with a call and a guided setup.
- You're mid-season with a large event booked. Build and test now, and move after the event.
- Your only gap is a report or a field. Ask CRO first; switching to fix one report is rarely worth it.
Before you go
What to export from CRO Software, and how
CRO's switching page says โyour data belongs to youโ and tells you to ask its support staff for custom formats. We found no published self-serve export guide, so treat every row below as a request to CRO support for a CSV, and check each file opens before your notice date. If you sync with QuickBooks, your customers and invoices are also there, which gives you a second copy to check against.
| Data | How to get it out of CRO Software | What happens to it in Fieldproxy |
|---|---|---|
| Customers and billing contacts | Ask CRO support for a CSV of customers with billing contacts, terms and payment method type (not card numbers). | Customers with contacts per site, ready for the portal and for no-login quote and payment links. |
| Sites and placement pins | Ask for sites with addresses, GPS pins (CRO allows several pins per location) and access notes. | Sites with every pin kept, gate codes and placement notes, shown to the driver at the stop. |
| Units and containers | Ask for the inventory list: ID or serial, type and size, status and current site, including customer-owned units. | A unit register by serial and QR tag with statuses (In yard, On rent, Needs repair, Missing) and a location history from day one. |
| Active rentals | Ask for each rental line: units per site, rental start date, rate, service day and frequency. | Rental lines that generate their own weekly stops and bill on their own 28-day anniversary. We check every start date with you. |
| Recurring routes | Ask for routes with their stops in order, truck and driver. | Routes per truck with fresh-water and waste gallon allowances, rebuilt and checked against a week of real stops. |
| Open jobs | Ask for scheduled deliveries, swaps, pickups and pump-outs for the next 60 days. | Jobs at the right status on the right route, so nothing booked in CRO is lost. |
| Invoices, payments and aging | Ask CRO for open invoices and aging, and pull the same from QuickBooks if you sync. | Open balances carried over; history stays in your accounting system, which keeps syncing. |
| Service history and photos | Ask what history CRO can export; screenshot or save photos for customers likely to dispute damage. | Attached to the unit or site, so a damage dispute next month still has the delivery photo. |
source: CRO Software: making the switchsource: RapidWorks: CRO product page (features, pricing model)
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.
Dispatch rules and auto-dispatch settings
How CRO auto-dispatches recurring routes and handles holidays is configuration, not data. Write down how each route behaves on a holiday and in an emergency, and we set the same rules up as automations.
source: RapidWorks: CRO product page (features, pricing model)
Collections Baskets and portal accounts
CRO's collections groupings and your customers' portal logins stay in CRO. Save the aging list on your last day, and tell portal customers where their invoices and service photos will be from next cycle.
source: RapidWorks: CRO product page (features, pricing model)
The QuickBooks connector and third-party hauler access
The QuickBooks link and any outside haulers set up in CRO's third-party hauler app stop when CRO stops. Turn the CRO QuickBooks sync off on the day the new sync is checked, never both at once, so no invoice posts twice.
source: RapidWorks: CRO product page (features, pricing model)
Reports and driver messages
Inventory and aging reports are views, and in-app messages with drivers live in CRO. Save the reports you use each month as PDFs, and keep CRO readable until the switch-off date.
Do these before you cancel CRO Software
- Get your renewal date and notice terms from CRO or RapidWorks in writing.
- Ask CRO support for every CSV above and open each one.
- Count units in the yard and match the count to CRO's inventory report, so missing units are known before the move.
- Check every active rental's start date: it sets the 28-day anniversary in the new system.
- Run one full billing batch from Fieldproxy and check it in QuickBooks, Xero or Sage before turning CRO's sync off.
- Save photos for any open damage or tip-over dispute.
- Tell portal customers and outside haulers the date things change.
Send us your CRO Software export and see it running in your setup.
Get DemoLive within a day
The move from CRO Software, 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 the day after the setup call, not that every truck moves at once. A large fleet, a mixed roll-off and portable operation or a busy event season adds time, and we say so on the first call.
What happens on go-live day- 1
Before the call: terms, exports, pilot route
You, about an hour
Ask CRO for your terms and the CSVs. Pick a pilot: one truck's weekly route, ideally one with a mix of construction sites, hand wash stations and a holding tank. Pick a Monday after a billing batch to start. - 2
The call: one route, from enquiry to invoice
You and Fieldproxy, 30 minutes
Walk us through how an order comes in, how you size it, how units leave the yard, what the driver does at each stop, where the truck dumps, and how a 28-day invoice goes out. Send the exports and one sample invoice. - 3
We build your setup
Fieldproxy's team
Order types and statuses, the sizing calculator on your quote template, the unit register, rental lines that generate stops and rent, truck tank allowances, driver checklists per unit type, the manifest form, and the screens each role sees on the web and the Android and iOS app. Roll-off containers sit in the same register if you run both. - 4
We move your data, free
Fieldproxy's team and Fieldproxy AI
Customers, sites and pins, units and containers, active rentals with start dates, routes and open jobs, mapped and checked for duplicates. A QR code per unit if you want to tag them. - 5
We connect the books
Fieldproxy's team, with your bookkeeper
Two-way sync with QuickBooks Online, Desktop or Enterprise, Xero or Sage, agreed and tested against a real billing batch before anyone relies on it. - 6
Live: the first route runs the next day
Day one
The pilot driver opens the route on the Fieldproxy app, scans or picks each unit, completes the checklist, takes the after-service photo and logs the load at the plant. Every other truck stays on CRO. - 7
Weeks or months: truck by truck, then switch off
Your schedule
After two weekly cycles, compare stops, missed-stop reasons and gallons, then move the next truck, always after a billing batch. When the last route has moved, take final exports and end CRO on the agreed date.
Cutover
Running CRO Software and Fieldproxy side by side
For a short, dated window, both tools are open. Fieldproxy is there to replace CRO Software, 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 rental lives in one system
A route that has moved is serviced, logged and billed only in Fieldproxy. Its rentals are closed in CRO the same day. No unit is serviced twice and no customer gets two invoices for one cycle.
Move after a billing batch
Move each route on the Monday after a weekly billing batch, so every anniversary in the next cycle bills from one system. Check one real batch in your accounting system before the next route moves.
A fixed switch-off date
Keep CRO readable, not in use, and set the date it ends, ideally at your renewal. The Watcher agent flags on-rent units that pass 8 days without a service and loads without a manifest while drivers are new to the app.
The fear
What if a unit misses its weekly service during the move?
A missed service on a busy construction site is an angry superintendent and an overflowing unit by Friday. This is how we keep the move from causing one.
- 1
Every on-rent unit has a stop before day one
Before the pilot route starts, we list every active rental line on it and check each one has a service day. A rental with no stop shows up on a list, not on a job site. - 2
An alert at 8 days
If an on-rent unit passes 8 days without a completed service, dispatch gets an alert with the unit and the site, the same day. - 3
A ride-along on the first route
The pilot driver runs the first day with the dispatcher on the phone. Anything that doesn't match the yard, such as a unit type or a gate code, is fixed that afternoon. - 4
One truck at risk, not the company
Only the pilot truck moves. Every other route keeps running on CRO until you decide to move it.
Where things live
CRO Software terms and where they go in Fieldproxy
So dispatchers and drivers know where things went on day one. How roll-off and portables share the board is agreed on the call.
| In CRO Software | In Fieldproxy |
|---|---|
| Jobs: deliveries, exchanges, services, final pickups | Orders with rental lines; delivery, service, swap and pickup stops generated from them |
| Recurring routes and auto-dispatch | Stops generated from each active rental's service day; routes per truck; automations for holidays |
| Unassigned jobs queue | Unassigned stops on the dispatch board, assigned by dispatch |
| Asset tracking and job-site map pins | Unit register by serial and QR, with GPS, time, driver and photo on every move |
| Inventory report | Availability calendar by unit type, idle units over 30 days, missing units |
| Failed jobs with reason and photo | Missed-stop reason codes with required photo, and a dry-run or extra charge line |
| Pump truck gallons and nearest pump-out | Truck tank allowances, running gallons on the route, and a manifest per load by jurisdiction |
| Invoices from completed jobs, recurring billing | 28-day anniversary billing per rental line, proration, weekly batch |
| Interactive collections and Collections Baskets | Aging views and the Autopilot agent drafting payment reminders for a person to approve |
| Customer portal | Portal per customer with units, last service photo, invoices and pickup requests; no-login links |
| QuickBooks Online and Desktop sync | QuickBooks Online, Desktop and Enterprise, Xero and Sage, two-way |
| Driver app (iOS and Android) | Driver app with per-unit checklists, QR scan, photos, signatures, 27 languages |
Straight answers
Switching from CRO Software: FAQ
How long does it take to switch from CRO Software to Fieldproxy?
Is migration from CRO free?
Can I get my data out of CRO?
Is CRO Software going away after the RapidWorks acquisition?
Can I keep CRO for roll-off and use Fieldproxy for portables?
Does Fieldproxy work with QuickBooks Desktop, Xero and Sage?
Does Fieldproxy bill portable toilet rent every 28 days?
Do AI agents answer calls from event planners and contractors?
Can ChatGPT or Claude work with my portable toilet data?
Sources
Where the facts on this page come from
Every CRO Software fact links to CRO Software'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 portable toilet and roll-off companies.
- source: CRO Software homepage (industries, pricing terms, reviews)
- source: CRO Software: about (founders, clients)
- source: CRO Software: making the switch
- source: RapidWorks: CRO product page (features, pricing model)
- source: RapidWorks: portable sanitation industry page
- source: RapidWorks: CRO software for portables
- source: RapidWorks (1 Oct 2025): RapidWorks acquires CRO Software
- source: RapidWorks (25 Sep 2026): Matt DePaolis appointed CEO
- source: RapidWorks blog: CRO vs ServiceCore for portable sanitation
- source: ServiceCore: 28-day billing vs monthly billing
- source: ANSI/PSAI Z4.3-2016, Portable sanitation at work sites
- source: UOSA septage receiving facility registration and rules (2027)
- source: 40 CFR 503.17, recordkeeping
Leave CRO Software without the leap. Live within a day.
A 30-minute call about how a job runs in your business, and a CRO Software 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.