How to switch from Service Autopilot without losing a client, a program or a spring
Short answer: your data is not locked in, it is behind a permission. Service Autopilot's exports are off by default under User Roles and Rights; once the owner switches them on, clients export from CRM, Clients, Actions, Export Clients, and invoices, payments and the dispatch board export from their own lists. The files land on My Day under Recent Exports as .xls. Your QuickBooks sync already holds customers, invoices and receivables outside Service Autopilot. Check your renewal date, export, move one crew at a time and keep Service Autopilot readable until the term ends.
With Fieldproxy the move is free and assisted and you're live within a day: your first crew runs real jobs in Fieldproxy the day after the call, on your own statuses, services and price list. Everyone else moves on a schedule you set, ideally before the spring rush. One price per company with unlimited users, so seasonal crew members never add a seat.
Leaving Service Autopilot? See your setup first
Send us a Service Autopilot export. We build your stages, forms and data in Fieldproxy, free, before you decide.
In buyers' words
What people leaving Service Autopilot told us
From our sales calls between August and November 2026, word for word. We don't name the people or companies. These are the reasons they gave, not a survey.
โonce they accept that contract, one of the hardest things is then getting it on our schedule board and getting our guys work orders that have all the descriptions and everything on there. It's just we have excel sheets that we got to enter them intoโ
โservice autopilot, especially this year seems to be kind of lacking in the service department. We notice it goes down quite a bit. It's been slower.โ
โwe just look at service autopilot ... and we manually enter the data for that crew about what they actually completed.โ
Why teams leave
Why teams leave Service Autopilot, with the facts checked
Service Autopilot has run recurring lawn and landscape routes for a long time, and plenty of companies are well served by it. The ones that move tend to hit one of the reasons below. Each is either from Service Autopilot's own pages, checked 20 November 2026, or from owners who told us on a call.
Approved estimates don't reach the crew on their own
The most common thing we hear: a client accepts, and someone retypes the work into a spreadsheet so the crew gets a work order with the full description. In Fieldproxy an accepted estimate becomes the job, with every line, note and photo, on the crew's phone. Nothing is keyed twice.
Add-on options that change the total
Owners want to show the main job and its total, then list options (lighting, an extra bed, a drainage fix) that only change the total when the client ticks them. Fieldproxy estimates carry optional lines the client picks from a link, and the accepted ones flow into the job and the invoice.
The bill depends on the plan, not the work
Service Autopilot bundles licences into each plan and some of the features owners ask for most, such as the client portal and two-way texting, sit on the top plan, which is priced on request. See the full Service Autopilot pricing breakdown. Fieldproxy is one price per company with unlimited users and the same features for everyone.
source: Service Autopilot: Pricing (plans, licences, add-ons, FAQ)
Crew pay and bonuses live in a second system
Lawn companies that pay production bonuses often read the day's jobs out of Service Autopilot and retype them into Google Sheets. Fieldproxy works bonuses and commissions out from completed jobs, budgeted against actual hours, so the sheet goes away. The budgeted versus actual hours view was built while we moved Service Autopilot customers across.
Slower days and outages in season
Owners have told us it goes down more than it used to and has felt slower since the ownership change. That is their experience, not a measurement, and your account may be fine. If it isn't, it is a fair thing to raise at renewal.
No public API to build around
Service Autopilot connects to other tools through Zapier; there is no public API. If you want your own reporting or a custom link to another system, that limits you. Fieldproxy has an API and an MCP server, so ChatGPT or Claude can read and update your data with a person confirming each change.
Stay on Service Autopilot if
- Your routes, automations and recurring billing run smoothly and your crews like the app. Don't switch to fix a problem you don't have.
- You're mid-term on an annual subscription with months to run. Plan the move for the renewal date rather than paying for two systems.
- You're a one-truck operation on the Startup plan and it does what you need. Fieldproxy isn't the cheapest option at that size.
- You depend on a Service Autopilot marketplace add-on or a Zapier flow you can't live without for a season. List those first.
Before you go
What to export from Service Autopilot, and how
Service Autopilot's export is a permission, not a lock. It is off by default: the account owner opens User Roles and Rights and turns export on for their role. After that, each list exports from its own screen and the files land on My Day under Recent Exports as .xls. There is also an Import/Export screen under your avatar. The full click path is in how to export your data from Service Autopilot.
| Data | How to get it out of Service Autopilot | What happens to it in Fieldproxy |
|---|---|---|
| Clients and properties | CRM, Clients, Actions, Export Clients. Needs the export permission on your role. | Clients, service addresses and contacts, checked for duplicates. Each property can carry its own notes, gate codes and photos. |
| Recurring services and programs | Export from the client and job lists, or ask Service Autopilot for a list of every recurring service with its next date. | Rebuilt as recurring visits per property: mowing weekly, rounds every few weeks, the season's start and stop dates, and compound schedules. |
| Estimates | Check Actions on your estimates list. Service Autopilot's help article for that list shows bulk edit, copy, email and print but no export, so if yours has none, print the open ones or ask support for a file. | Open estimates carried over with their lines and options; won estimates become jobs. |
| Jobs and visit history | Jobs only export once they are closed out with times entered. Close out the season first. | Visit history per property, so crews and the office see what was done and when. |
| Invoices and payments | Export invoices and payments from their lists. If you used the 2-way QuickBooks sync, they are already in QuickBooks. | Only open balances move. Accounting history stays in QuickBooks, now with two-way sync from Fieldproxy. |
| Dispatch board | Export the dispatch board for the days ahead. | Next week's routes loaded in the right order for each crew, so day one looks like any other day. |
| Services, rates and price list | Export or screenshot your services and rate tables. | Your price list, rate tables and budgeted hours per service, ready for estimates from the phone. |
| Employees and equipment | A plain list: name, role, phone, email; trucks, mowers and trailers. | Unlimited users with roles; equipment with service intervals. |
source: Service Autopilot Help: Export the client listsource: Service Autopilot Help: User rights for Other Access (Export Lists)source: Service Autopilot Help: Invoice list exportsource: Service Autopilot Help: Payments list exportsource: Service Autopilot Help: Overview of the estimates listsource: Service Autopilot Help: Import data (Import/Export screen)
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.
Photos, attachments and note history
These don't come out of Service Autopilot cleanly. If a property's photos or a long note thread matter (a dispute, a damage claim, a picky HOA), save them by hand or ask Service Autopilot in writing how to get them, well before your term ends.
Automations, templates and settings
An export carries records, not how your account behaves. Automations, email and text templates, ticket categories and statuses are rebuilt. We mirror the names your office already uses, so the first morning feels familiar.
Jobs that were never closed out
Open jobs without times entered won't appear in a job export. Close out what is finished, and list what is still open so it can be carried over by hand.
Zapier flows and marketplace add-ons
Anything wired through Zapier or a Service Autopilot marketplace add-on stays behind. List each one and what it does; most become a built-in step or an automation in Fieldproxy.
Do these before you cancel Service Autopilot
- Find your renewal date and the notice your agreement asks for: 60 days before an annual term ends under the terms page live today, 30 days under the 2024 Xplor version. Cancellation starts with a call to a customer service rep, not an email.
- Turn on the export permission under User Roles and Rights, then export clients, invoices, payments, timesheets and the dispatch board. Download every file from My Day, Recent Exports.
- Close out finished jobs with times entered so they appear in the job export.
- Save photos, attachments and important note threads by hand. They don't export cleanly.
- Check QuickBooks has every customer, invoice and payment it should. Turn off Service Autopilot's sync for anything Fieldproxy now invoices, so nothing reaches the books twice.
- Screenshot your automations, templates, statuses and rate tables.
Send us your Service Autopilot export and see it running in your setup.
Get DemoLive within a day
The move from Service Autopilot, 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 is when the first crew runs real jobs, not a deadline for everyone. A big client list, a lot of photos to save or a data clean-up adds time, and we say so on the first call.
What happens on go-live day- 1
Before the call: check the term and turn on exports
You, about an hour
Find your renewal date. Turn on the export permission and pull clients, invoices, payments and the dispatch board. Pick a first crew to move and a date for Service Autopilot to go read-only. - 2
The call: one client, from estimate to paid invoice
You and Fieldproxy, 30 minutes
Walk us through an install estimate with options, a mowing program and a fertilizer round: statuses, who approves what, how crews are paid and what has to be true before you invoice. Send the exports and a few estimates and invoices. - 3
We build your setup
Fieldproxy's team
Clients and properties; your job stages and ticket categories; estimates with optional lines, cost, margin and budgeted hours per section; recurring programs; the crew app screens; and the reports you check on Monday. - 4
We move your data, free
Fieldproxy's team and Fieldproxy AI
Clients, properties, recurring services, open estimates, scheduled visits and equipment, mapped and checked for duplicates. Each program gets its next date, so spring is on the calendar before the first warm week. - 5
We connect the books
Fieldproxy's team, with your bookkeeper
Two-way sync with QuickBooks Online, Desktop or Enterprise, checked against real invoices. Card and ACH payment links with no login, and Tap to Pay for crews collecting on site. - 6
Live: the first crew on Fieldproxy
Day one
One crew runs today's route in Fieldproxy, offline in back yards if needed, with GPS check-in, before and after photos and the client notified on the way. Everyone else stays on Service Autopilot for now. - 7
Weeks, not a big bang: one crew at a time, then switch off
Your schedule
Move the next crew when the last one is settled. Aim to finish before spring, or after the fall cleanups. When the last crew has moved and open jobs are closed, take a final export and let the term end.
Cutover
Running Service Autopilot and Fieldproxy side by side
For a short, dated window, both tools are open. Fieldproxy is there to replace Service Autopilot, 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 crew, not by job
During the move each crew works in one system. A crew on Fieldproxy creates every new job there; a crew still on Service Autopilot stays there. Nobody keys a visit twice.
One system owns each client and each invoice
Once a client moves, their programs and invoices live only in Fieldproxy, and only one tool sends their invoices to QuickBooks. Turn off the Service Autopilot sync for anything Fieldproxy bills.
A switch-off date on the calendar
Keep Service Autopilot readable, not in use, until a fixed date, ideally your renewal date with notice already sent. See how to cancel Service Autopilot.
The fear
What if spring lands in the middle of the move?
For a lawn company the worst outcome isn't a slow week in the office. It's a round that never goes out because its date was lost, or a crew learning a new app in the first big week of mowing. This is how to keep both from happening.
- 1
Every program is on the calendar before a crew moves
We load your recurring services first, with the next date per property, and show you the season. You check it against Service Autopilot before anything changes. - 2
Move in the slow season
December to February is when most lawn and landscape companies switch. Plan the crew-by-crew move for then, with notice already sent. - 3
If it gets busy, nobody changes apps mid-route
Crews still on Service Autopilot stay there until things calm down. The rest keep going in Fieldproxy. Nothing forces everyone over on one day.
Where things live
Service Autopilot terms and where they go in Fieldproxy
What the screens your office uses every day become in Fieldproxy. This mapping comes from rebuilding a Service Autopilot customer's own setup, down to their pricing grid.
| In Service Autopilot | In Fieldproxy |
|---|---|
| My Day (calendar, tickets due, notifications) | A home screen with today's calendar, tickets due, watched items and an activity feed of who did what |
| Tickets with categories, Watching and saved filters | Tickets with your categories, a watch list, and named filters the whole office can share |
| Client activity: emails, notes, calls, forms | One timeline per client, typed by channel, with calls logged separately from notes |
| Estimate grid: services, materials, budgeted hours, cost, margin, markup | The same grid, with won or lost per section, budgeted against actual hours, and $ per hour shown so nobody needs a calculator |
| Recurring services and the dispatch board | Recurring programs per property and a drag-and-drop board by crew, with route planning |
| Automations | Automations rebuilt step by step, plus AI agents that chase estimates and invoices for a person to approve |
| QuickBooks sync | Two-way QuickBooks Online, Desktop or Enterprise |
| Zapier | A full API and an MCP server for ChatGPT or Claude, plus Zapier if you still want it |
Straight answers
Switching from Service Autopilot: FAQ
Can I export my data from Service Autopilot?
What doesn't come out of Service Autopilot?
Does Service Autopilot have an API for migration?
How long does it take to move from Service Autopilot to Fieldproxy?
Does Fieldproxy charge to migrate from Service Autopilot?
When should a lawn company switch software?
Sources
Where the facts on this page come from
Every Service Autopilot fact links to Service Autopilot's own pages, opened on 20 November 2026. Features and terms change, so check the current page before you decide. More detail, with every source, is in Full side-by-side: Fieldproxy vs Service Autopilot.
- source: Service Autopilot: Pricing (plans, licences, add-ons, FAQ)
- source: Service Autopilot: Price calculator (labelled an estimate; one-year agreement rates)
- source: Service Autopilot: QuickBooks Online page (2-way sync, upgrade for $29/mo)
- source: Service Autopilot: Terms of Service, live page, last modified 26 May 2021 (BACKTELL LLC)
- source: Service Autopilot: Terms of Service, Xplor version last modified 20 Feb 2024 (Internet Archive copy of 31 Oct 2026)
- source: Service Autopilot Help: Export the client list
- source: Service Autopilot Help: User rights for Other Access (Export Lists)
- source: Service Autopilot Help: Zapier integration overview
- source: Service Autopilot Help: Integrations
- source: Xplor: Service Autopilot by Xplor (16 Jan 2025)
Leave Service Autopilot without the leap. Live within a day.
A 30-minute call about how a job runs in your business, and a Service Autopilot 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.
Leaving Service Autopilot: the full guide
Every question about moving off Service Autopilot, one page each
Start here
Leaving
- How to export your data from Service Autopilot
- How to cancel Service Autopilot
- Switching from Service Autopilot, step by step (this page)
Head to head
By trade
Problems owners bring us
- Get an approved estimate to the crew without retyping it
- Reschedule a rained-out route and tell every customer
- Work out crew bonuses from completed jobs
- Bill recurring lawn customers without chasing cards
- Renew programs and sell prepay over the winter
- Keep pesticide and fertilizer application records
- Route 1,000 lawns a week across crews