FieldproxyAI-native field service softwareSwitching software
Our field service software is being shut down. What should we do and what should we move to?
Find the three dates that matter (when work stops, when logins stop, when your data is deleted), then export everything before the earliest one: customers, sites, jobs with their history, assets, attachments, recurring schedules, users and price lists. Treat the replacement your vendor offers as one option, not the default, and test every candidate on your own exported data before you commit. Plan backwards from the shutdown date so the new system runs in parallel with the old one for at least two weeks before the old one goes dark.
- Write down three dates: last day of service, last day of login, and the data deletion date. Plan to the earliest.
- Export first, choose second. The export is the one task with a hard deadline you cannot buy back.
- Exports usually miss recurring schedules, users, custom fields and settings. Screenshot or list them by hand.
- The vendor's suggested replacement is a sales referral. Score it on your workflow like any other option.
- Run old and new side by side for two weeks or more, then cut over at a quiet point in the billing cycle.
This page is about moving off a product that is being retired. If your software still works and you just want to leave, the timeline is yours to set, and most of the export advice still applies.
Facts checked as of November 2026. Sources at the end of the page.
Step by step
How it works, step by step
Start with the dates. These are recent field service shutdowns and what each vendor has published. Where a date could not be found in a public source, the table says so.
| Product | What is happening | Key dates | Where users are pointed |
|---|---|---|---|
| GeoOp and GeoNext (AU, NZ, UK) | Geo went into receivership on 26 September 2024. The Access Group, which also owns Tradify, announced it had acquired GeoOp and GeoNext on 4 February 2025. New sign-ups are closed and the platforms are being phased out. | No public shutdown date found. Customers were given dates directly; one NZ firm we spoke to in May 2026 had a June move date and an end-of-June shutdown. | Tradify, the Access Group's own product |
| Verizon Connect Work, formerly Fleetmatics WORK (US, Canada, international) | Retired. Verizon says it is not building a replacement field service product. | Active service ends 31 Dec 2026. App and Work Mobile stop 4 Jan 2027. Last day to start an export 28 Feb 2027. Data purged after 31 Mar 2027. | Preferred partners GoCanvas and Service Fusion, or any vendor you choose |
| Salesforce Click Field Service Edge (formerly ClickSoftware FSE) | Being retired. Salesforce honors existing subscriptions until their end date, then access stops and customer data is deleted. | Salesforce's notice (published 3 Oct 2026) gives no single date; it points to each subscription's end date. Partners widely cite 31 Dec 2026. | Salesforce Field Service |
| ClickSoftware Service Optimization 8.3 (on-premise Click) | Reached end of life. No bug fixes, security updates or technical support. | End of life 31 Dec 2023 | Field Service Edge at the time, now Salesforce Field Service |
| Pendragon Forms (mobile forms used for field data collection) | The company is closing its software business after 30 years. No new licenses and no support renewals. | Expects to wind down over the next 12 months; no end date on its site | No named successor; questions go to its support address |
As of November 2026, from each vendor's own pages or the press where noted. Vendors have moved these dates before, so check your own account notices.
Then list what you need out. Exports vary by vendor; the gaps in the right-hand column are the ones that show up most.
| Data | Why you need it | Often missing from the standard export |
|---|---|---|
| Customers and contacts | Every job, quote and invoice hangs off them | Secondary contacts, notes, tags |
| Sites and site notes | Access codes, hazards, parking, gate times | Sites stored only as address lines on each job |
| Jobs with full history | Warranty claims, disputes, repeat visits | Status history, who did what and when |
| Assets and equipment | Serial numbers, install dates, service intervals | Asset to site links, readings over time |
| Attachments | Photos, signatures, certificates, signed PDFs | Exported as separate ZIPs that take days to build |
| Recurring schedules | Maintenance visits that should keep happening | Frequently not exported at all |
| Quotes, invoices, payments | Open balances and quote follow-ups | Payments, if your accounting system holds them |
| Users, roles, skills, certifications | Who can be sent to what | Almost never exported |
| Price lists, items, forms, checklists | Rebuilding estimates and inspections | Form designs and checklist logic |
Example: Verizon's Work export covers clients, jobs, attachments, quotes, invoices, POs and suppliers, but not users, recurring schedules or payments, and download links expire after 3 weeks.
Now plan backwards from the earliest date. Week numbers count down to the day work stops.
Week 12 or as soon as you hear: confirm the dates
Get the shutdown notice in writing. Ask the vendor three questions: last day we can create jobs, last day we can log in, and the day the data is deleted. Ask whether billing continues until then and how refunds work.
Week 11: start the slow exports first
Attachment exports are the slowest. Request them first, oldest date range first, and save every file to a shared drive the day it is ready. Then export customers, sites, jobs, assets, quotes, invoices and price lists in both CSV and the native format if offered.
Week 10: record what the export misses
Screenshot or list users and roles, technician skills and certifications, recurring schedules (customer, frequency, next date), job types, custom fields, form and checklist designs, and automation rules. These are what teams discover are missing after the switch.
Week 10: check the files
Count rows against the old system: customers, open jobs, jobs last month. Open ten attachment folders at random. A zero-row file for a busy month means re-run the export.
Weeks 9 to 7: shortlist and test on your data
Pick two or three candidates, including the vendor's suggestion if it is plausible. Send each one the same export and the same three real jobs. Judge them on whether your workflow runs, not on the demo.
Weeks 6 to 4: build and import
Set up stages, forms, checklists and permissions, then import customers, sites and assets, then open jobs and recurring schedules. Import history last; it is the least urgent and the largest.
Weeks 3 to 2: run in parallel
Book new work in the new system while finishing open work in the old one. Field staff use the new app on real jobs. Compare a week of completed jobs and invoices between the two.
Week 1: cut over, then keep the exports
Pick a cutover day early in a billing cycle, not on the last day of the month. Close the old system to new jobs, finish the last invoices, and keep the original export files read-only for as long as your tax records need them.
Where it breaks
Why it goes wrong
These are the problems buyers described on our sales calls, by trade and size.
The forced move lands on a tool built for a different business
A New Zealand risk inspection firm with about 40 users, most of them long-serving contractor field agents, was moved from GeoOp to Tradify. Its jobs are mostly unscheduled: contractors batch them by area, and the office chases availability by phone. A tool built around booked appointments for small trade crews made the office double-handle every job.
Silence from the new vendor during the countdown
The same firm had heard nothing from the replacement vendor for four weeks with the shutdown a month away. No training plan, no import help. When the deadline belongs to someone else, your plan cannot depend on their calendar.
The workarounds never make it across
A US electrical contractor doing EV charger installs and panel upgrades lost its FSM to a sunset. Around it, the team had built WhatsApp groups as a stand-in customer and subcontractor portal, estimates in a Google Sheet, and Zapier glue to QuickBooks. None of that is in any export. It has to be listed and rebuilt on purpose, or it quietly disappears.
Technician qualifications live in people's heads
User lists, skills and certifications are rarely exported. For EV charger work funded under the federal NEVI program, electricians must hold EVITP certification or have finished an apprenticeship with charger-specific training, and at least one electrician on a multi-electrician project must be in a registered apprenticeship. If those records are not rebuilt, dispatch cannot check them.
Bulk data that needs cleaning before import
The risk inspection firm wanted to load 200 to 300 jobs at once and fix the data before it went in. Old systems carry years of duplicate customers and half-filled fields. Importing them as-is moves the mess into the new system.
A second forced move
A Queensland multi-trade business that had watched the GeoOp shutdown asked what happens if the next vendor shuts down too. That is a fair question for any replacement: ask how you get all your data out, in what format, and how quickly.
The options
Ways to do it
| Approach | How the move works | Weak spot | Good for |
|---|---|---|---|
| Take the replacement the vendor names (Tradify for GeoOp; GoCanvas or Service Fusion for Verizon Connect Work; Salesforce Field Service for Click FSE) | The vendor's referral or migration path, often with a set import format | Chosen by who bought or partners with the old product, not by fit. It may be a different kind of tool from the one you had | Teams whose workflow already matches the suggested product |
| Move to a mainstream template FSM | Self-serve signup and CSV import of customers and jobs | Your old custom fields, forms and workarounds have to fit its fixed screens | Small crews with booked appointments and simple jobs |
| Spreadsheets and messaging as a stopgap | Export to Excel, run jobs from sheets and WhatsApp until you decide | No app, no history, nothing checks qualifications or photos; a stopgap tends to stay | A few weeks at most, for a very small team |
| Enterprise suite with a partner (Salesforce, Dynamics 365, IFS) | A partner scopes, builds and migrates | Months, not weeks; often longer than the shutdown window | Large firms already on that platform |
| Configurable FSM set up for you (Fieldproxy) | You send the export and walk through how you work; stages, forms and rules are built to match, then your data is migrated | You still need to make time to explain your process and test it | Best for processes that don't fit a template, set up for you. |
As of November 2026. Vendor facts are from the vendors' own pages (sources below). See our comparisons of GeoOp, Tradify and Salesforce Field Service for more detail.
Worked example
A worked example: a 40-user inspection firm with 12 weeks' notice
Say an inspection firm has 30 contractor field agents, 6 desk investigators and 4 office staff. It has about 900 customers, 250 open jobs and six years of photo-heavy history, and the vendor gives 12 weeks' notice. Made-up numbers to show the order of work.
| Weeks before shutdown | Task | Result |
|---|---|---|
| 12 | Get the three dates in writing; request photo and attachment exports for six years in two-year ranges | Exports queued on day one; the longest one takes 8 business days |
| 11 | Export customers, sites, jobs, invoices; list all 40 users with their job types (e.g. energy meter vs corporate) | Row counts match except one month, which is re-run |
| 10 | List recurring work and the Excel invoicing macros the office uses | 14 recurring rules and 2 invoice formats written down |
| 9 to 7 | Three vendors get the same export and the same three jobs: a desk job that turns into a field visit, a rural meter read, a batch of 20 jobs in one area | One option fails the batch-by-area job; one needs every job booked to a time slot |
| 6 to 4 | Clean duplicates (900 customers become 860), import, set up skills, photo rules and Xero | Agents log in and see only their own area's jobs |
| 3 to 2 | All new jobs go into the new system; 5 senior agents test first, then the rest | Two weeks of invoices match the old macros line for line |
| 1 | Close the old system to new work; archive the export files | Six years of history kept read-only, as tax records require |
The point of the sequence: exports and the user list happen before any software choice, because the export window is the only deadline nobody can extend.
Before you buy
What to check before you buy
Good signs
- They ask for your actual export files before the demo and show your own jobs in it
- They can name what your export is missing (users, recurring schedules, forms) and how they will rebuild it
- Your oddest real job runs end to end: an unscheduled batch, a desk job that becomes a site visit, a job with a required certification
- A written plan with dates for import, parallel run and cutover that finishes before your shutdown date
- Your accounting connection (Xero, QuickBooks) tested on a real invoice before go-live
- A clear answer on how you would export everything from them, and in what format
- Support hours that overlap your working day in your time zone
Red flags
- A demo on sample data only, with "we'll import later"
- No one owns the migration on their side; you get a CSV template and a help article
- The vendor's suggested replacement is presented as the only path
- Go-live planned for the same week the old system shuts down, with no parallel run
- Your workflow has to change to fit fixed screens, and nobody says so until after you sign
- Silence for weeks after you sign, during your countdown
In Fieldproxy
Setting it up in Fieldproxy
Fieldproxy is set up around your process, and moving your data across is part of that setup. Names marked e.g. are examples.
Send the export, we map it
Send the files from your old system: CSV, JSON or ZIP folders of attachments. Customers, sites, jobs, quotes, invoices and photos are mapped and imported, with a dry run first. See /mcp/imports-and-data-migration for how imports and migration work.
Your stages and forms, rebuilt as they were
Your job stages, statuses, custom fields, forms and checklists are set up to match the way you worked, including the workarounds that lived outside the old system (e.g. a desk_job status that converts to a field visit, or an estimate sheet rebuilt as a quote template).
Recurring work and assets
Recurring schedules you listed by hand become recurring jobs and contracts (/solutions/recurring-jobs). Assets carry their serial numbers and service history, with QR codes (/solutions/asset-management).
Skills, certifications and contractors
Users get roles, skills and certifications (e.g. evitp_certified), and contractors see only their own jobs (/solutions/subcontractor-management). The Dispatch agent (/agents/dispatch-agent) assigns by distance, skills and certifications, so a job that needs a certified electrician cannot go to someone without the record.
Run in parallel without double handling
During the parallel run, the Command Center (/agents/command-center) answers questions such as "which open jobs from the old system have no visit booked yet?" and makes changes as confirm cards with Undo. The Watcher agent (/agents/watcher-agent) flags jobs that go overdue while the team is learning the new app.
One price per company
Field staff, contractors and office staff are all on the same system. Fieldproxy is one price per company with unlimited users. See /pricing.
By region
How long to keep the old data
Keep the original export files even after the import works. In New Zealand, Inland Revenue says to keep business records, including electronic ones, for at least 7 tax years. That covers six years of job and invoice history exported from GeoOp.
In the US, the IRS says to keep records that support a tax return for 3 years in most cases, 4 years for employment tax records, 6 years if income was underreported by more than 25 percent, and 7 years for bad debt deductions. Keep job records that back an invoice at least as long as the invoice.
Verizon Connect Work customers in every region face the same dates, and Verizon will not transfer data to another vendor for you. Our page on the Verizon Connect Work shutdown has the full export steps.
How switching works
How switching to Fieldproxy works
We move your data over and set the system up to the way you already work. Fieldproxy replaces the old tool; it does not run alongside it.
Send us your export and the shutdown dates
Whatever you have so far: the vendor notice, customer and job files, attachment ZIPs. We tell you what is missing while the old system is still open.Walk us through three real jobs
Your normal job, your oddest job and the one the forced replacement could not handle. We set up stages, forms and rules to match.We import and you test on your own data
Customers, sites, assets, open jobs and recurring work come across first, history after. Your team checks it against the old system.Parallel run, then cut over
New work goes into Fieldproxy while old jobs finish in the old system. Cut over before the shutdown, not on the day.
FAQ
Questions people ask
- Our field service software is being sunset. What should an EV charger installation contractor move to?
- Something that holds the full flow from lead to permit to install to close-out, with technician certifications on each user so charger jobs only go to qualified electricians. Export your jobs, customers, photos and the list of your electricians' certifications first, then test two or three options on those files.
- GeoOp is shutting down and Tradify is not a good fit. What are the alternatives for a risk inspection company with 40 contractor field users?
- Look for software that handles unscheduled jobs batched by area, restricts each contractor to their own jobs, checks required photos before a job can close, and connects to Xero. You do not have to take Tradify. Test any option on your own GeoOp export before the shutdown date.
- Do we have to move to the replacement our vendor recommends?
- No. Verizon confirms Work customers can move to any provider. Salesforce recommends Salesforce Field Service to Click Field Service Edge customers, but nothing requires you to take it. The suggested product is one option to score like any other.
- What should we export before the shutdown?
- Customers, contacts, sites, jobs with history, assets, attachments, quotes, invoices, price lists and recurring schedules. Then record by hand what exports usually skip: users, roles, skills, certifications, custom fields, forms and automation rules.
- How long does a forced migration take?
- For a small or mid-sized team, plan about 12 weeks from notice to cutover, with at least two weeks in parallel. The export is the part with a hard deadline, so start it first.
- Should we bring over all our job history?
- Bring open work, recurring work and assets first. Import history after go-live, and keep the original export files read-only for as long as your tax rules require.
- What if the new vendor shuts down too?
- Ask before you sign how you can export all of your data yourself, in what format, and whether there is an API. If the answer is a support ticket, that is a risk.
Sources
Competitor details on this page come from the vendors' own pages and documentation, checked as of November 2026. Plans and prices change, so check the vendor's current page before you decide.
- NZ Herald: Tradify sells to UK firm; GeoOp receivership (1 Oct 2024): https://www.nzherald.co.nz/business/companies/former-sparkie-in-for-9m-payday-as-his-tradify-app-sells-to-uk-firm-for-100m/EDCBQJHMIVEXNIZFNT5B7M7RNE/
- The Access Group: acquisition of GeoOp and GeoNext (4 Feb 2025): https://www.theaccessgroup.com/en-gb/about/news/the-access-group-acquired-the-job-management-platforms-geoop-and-geonext/
- Tradiepad: GeoOp and GeoNext discontinued: https://www.tradiepad.com.au/geoop-geonext-discontinued/
- Verizon Connect Work: final transition deadlines and data export cutoffs: https://support.work.fleetmatics.com/hc/en-us/articles/51620051793683-Final-Transition-Deadlines-Data-Export-Cutoffs
- Salesforce Help: Click Field Service Edge product retirement: https://help.salesforce.com/s/articleView?id=004518833&language=en_US&type=1
- Solvares: ClickSoftware is being discontinued: https://solvares-fieldservice.com/en/clicksoftware-is-being-discontinued-choose-the-appropriate-fsm-alternative-now/
- ClickSoftware: Product Life Cycle Policy (archived December 2023): https://web.archive.org/web/20231203073219/https://wiki.cloud.clicksoftware.com/display/CS/Product+Life+Cycle+Policy
- Pendragon Forms: closing announcement: https://pendragonforms.com/
- 23 CFR 680.106: NEVI installation, operation and maintenance standards: https://www.law.cornell.edu/cfr/text/23/680.106
- Inland Revenue (NZ): record keeping: https://www.ird.govt.nz/managing-my-tax/record-keeping
- IRS: how long should I keep records?: https://www.irs.gov/businesses/small-businesses-self-employed/how-long-should-i-keep-records
Related
Keep reading
- Salesforce Click Field Service Edge is reaching end of life. What are the alternatives?
- GeoOp compared
- Tradify compared
- Salesforce Field Service compared
- What is the best field service software for a 5-10 person HVAC team?
- Cheaper ServiceTitan alternatives for small plumbing and HVAC companies, without payment processor lock-in