FieldproxyFieldproxy
Get Demo
FieldproxyAI-native field service software

Switching software

Salesforce Click Field Service Edge is reaching end of life. What are the alternatives?

Salesforce is retiring Click Field Service Edge (formerly ClickSoftware FSE): it honors each existing subscription until its end date, then access stops and the customer data is deleted, and it recommends moving to Salesforce Field Service, whose scheduling engine is Enhanced Scheduling and Optimization. Salesforce's notice gives no single public end date; partners widely cite 31 December 2026, so confirm your own subscription end date with your account executive. If you only used Click for scheduling and dispatch, the real alternatives are Salesforce Field Service, a scheduling engine that runs on Salesforce such as Skedulo, Dynamics 365 Field Service with Resource Scheduling Optimization, IFS Planning and Scheduling Optimization, or a configurable FSM that handles scheduling, dispatch and the technician app together.

  • Your deadline is your subscription end date. Salesforce has not published one date for everyone.
  • After the subscription ends, Salesforce says access stops and associated customer data is deleted. Export first.
  • Salesforce's path is Salesforce Field Service. Partners recommend 9 to 18 months for an enterprise transition.
  • If Click only did scheduling, list every scheduling rule and objective you use. That list is what you are replacing.
  • Move territory by territory, with old and new schedules compared side by side before each cutover.
Fieldproxy

This page is for teams that used Click mainly for scheduling and dispatch. If Click sits inside a large Salesforce estate with a partner already engaged, Salesforce Field Service is the path of least change, and this page will mostly help you check it.

Facts checked as of November 2026. Sources at the end of the page.

Step by step

How it works, step by step

Moving off Click is mostly a scheduling-rules project with a data export attached. The order below keeps the deadline items first.

1. Get your own end date in writing

Salesforce's retirement notice says it will honor your existing subscription until its end date and tells customers to contact their account executive to plan the move. Ask for the exact date access ends and the date data is deleted.

2. Export the data before anything else

Salesforce says that after the subscription ends, access stops and all associated customer data is deleted under its Trust and Compliance documentation. Export resources and their skills, calendars and shifts, territories or districts, tasks and appointment history, and any assignment and travel history you use for reporting.

3. Write down what Click actually decides

List every rule and objective in use: skills and skill levels, territory boundaries, working hours and breaks, appointment windows, priorities, SLA due times, preferred or excluded technicians, multi-person and multi-day work, and how much travel you trade for priority. In Salesforce Field Service terms these become scheduling policies made of work rules (which remove candidates who cannot do the job) and weighted service objectives (which grade the rest).

4. Map the integrations

Note where work orders come from (Salesforce Service Cloud, SAP, ServiceNow, Maximo), where completed work goes, and which mobile app the technicians use. If Click only scheduled, the replacement has to take jobs in from one system and send assignments out to another, just as Click did.

5. Shortlist and test on one territory

Load one territory's real resources and two weeks of real jobs into each candidate. Compare the schedules it produces with what Click produced: jobs scheduled, travel time, SLA misses, overtime.

6. Cut over territory by territory

Salesforce documents setting up enhanced optimization for individual service territories, and most alternatives can also start with one area. Run the new engine for one territory while Click runs the rest, then move the next. Finish well before the end date, not on it.

Where it breaks

Why it goes wrong

These come from Salesforce's notice, partner migration guides, and what enterprise service buyers on our calls said about changing scheduling and field systems.

Waiting for a date that never comes

Salesforce's notice was published on 3 October 2026 and does not give one end date. Teams that wait for a public announcement lose months. The date that matters is in your own subscription.

Underestimating the timeline

One Salesforce partner's FSE end-of-life guide recommends 9 to 18 months for most enterprise organizations to fully transition: 9 to 12 months for a like-for-like move, 12 to 18 for a redesign. Teams starting in late 2026 have far less than that.

Rules nobody wrote down

Click configurations built up over years carry rules that only the original consultant understood. If they are not listed before the move, the new engine produces schedules that look fine and break on the third day, when a technician without a site induction is sent to a site that needs one.

Buying a whole platform to replace a scheduler

If Click scheduled work orders that live in SAP or ServiceNow, moving to a full field service suite means moving work orders, assets and the mobile app too. That is a bigger project than the one you started with.

Every change goes through a central IT queue

An oil and gas OT support team on ServiceNow told us that changing one field form had to go through the enterprise ITSM team and could take months. If the replacement scheduler needs the same queue for every rule change, dispatchers stop trusting it and work around it.

The options

Ways to do it

OptionWhat it isWeak spotGood for
Salesforce Field Service with Enhanced Scheduling and OptimizationSalesforce's recommended path. Partners describe it as FSE evolved, with a scheduling and optimization engine Salesforce released in 2023A full field service product on Service Cloud, usually built by a partner; more than a scheduler swapCompanies whose CRM and service desk are already on Salesforce
Skedulo on SalesforceA managed package from AppExchange that adds scheduling objects to your org and works with your existing records; matches jobs to workers by skills, availability and locationOptimization of a group of jobs is a premium feature licensed separatelySalesforce shops that want a scheduler without the full Field Service build
Dynamics 365 Field Service with Resource Scheduling OptimizationA paid add-in that schedules many jobs at once: overnight runs, intraday runs every 30 minutes, emergency jobs firstRequires Dynamics 365 Field Service; priced by the number of resources optimizedMicrosoft-centered companies
IFS Planning and Scheduling Optimization (PSO)Scheduling across horizons, from months-ahead resource planning to a real-time Dynamic Scheduling EngineAn enterprise product with an enterprise implementationLarge utilities, telecom and equipment service fleets
Specialist route and workforce planners (e.g. Solvares VISITOUR)Planning and routing engines that sit beside your existing systemsYou still need a technician app and a system of record for jobsRoute-heavy work with a separate work order system
Configurable FSM set up for you (Fieldproxy)Scheduling, dispatch, route planning and the technician app in one system, set up to your rules, connected to the CRM or ERP that creates the workNot a drop-in Salesforce package; jobs live in Fieldproxy with an integration backBest for processes that don't fit a template, set up for you.

As of November 2026, from each vendor's or partner's own pages (sources below). Check the current product before relying on any one feature. Our Salesforce Field Service comparison and implementation timelines page have more detail.

Worked example

A worked example: Click as the scheduler for 150 technicians

Say a service company has 150 technicians in 5 territories. Work orders are created in its ERP, Click schedules them, and technicians use a separate mobile app. Made-up numbers to show what the inventory of Click rules looks like and where each one goes.

What Click does todayCountWhere it goes in the replacement
Skills and certifications checked before assignment34 skillsWork rules or a hard skill match; imported with each technician
Territories with their own working hours5Service territories or regions, set up one at a time
Appointment windows offered to customers4 windows a dayBooking windows in the new engine; test that the same slots appear
Priority and SLA due times3 priorities, 2 SLA tiersWeighted objectives or priority rules; emergency jobs scheduled first
Jobs needing two technicians or more than one dayAbout 1 in 20 jobsCheck that the engine supports multi-person and multi-day work before choosing it
Rules nobody can explain6Ask the dispatchers; drop or rebuild each one on purpose

Testing on one territory with two weeks of real jobs: if Click scheduled 1,400 jobs and a candidate schedules 1,380 with similar travel and no extra SLA misses, it is close enough to move on to the next territory. If it misses the two-technician jobs, it is not.

Before you buy

What to check before you buy

Good signs

  • They ask for your Click rules and objectives before showing a demo
  • A test on one territory with your real resources and two weeks of real jobs
  • Side-by-side numbers against Click: jobs scheduled, travel, SLA misses, overtime
  • Multi-day and multi-technician jobs handled, shown on your own examples
  • Dispatchers can change a rule or priority without a partner change request
  • A clear integration plan for the system that creates work orders and the one that bills them
  • A go-live date before your subscription end date, with time to spare

Red flags

  • A plan that starts only after you sign, with no date tied to your Click end date
  • "Feature parity" claimed with no list of your rules to back it
  • Optimization sold as a separate licence you only find out about late
  • Every scheduling change needs the partner or central IT
  • No way to run old and new in parallel for a territory

In Fieldproxy

Setting it up in Fieldproxy

Fieldproxy is set up around your process. For a Click replacement that means your scheduling rules first, then the integrations. Names marked e.g. are examples.

Your rules become the dispatch logic

Scheduling and dispatch run on your own rules: skills, areas, time windows and SLAs (/solutions/dispatching-scheduling). The Dispatch agent (/agents/dispatch-agent) assigns the right technician by distance, skills and certifications, inventory and cost, and AI scheduling builds the board and rebuilds the day when plans change, with a person approving every change (/ai-scheduling-dispatch-software).

Data moved, CRM kept

We move your Salesforce data (accounts, sites, assets, work order history) and keep Sales Cloud connected if you still use it. Jobs from another ERP or service desk come in through the REST API and webhooks (/developers).

Technicians on one app

The Android and iOS app works offline with your own checklists, photos, signatures and GPS check-in (/solutions/mobile-app), so the schedule and the work happen in the same system instead of two.

Changes without a ticket queue

Dispatch managers ask the Command Center (/agents/command-center) for a change in plain English (e.g. "jobs at hospital sites need a technician with site_induction") and it comes back as a confirm card with Undo.

Watch the cutover

The Watcher agent (/agents/watcher-agent) flags jobs that miss their SLA or visit window while territories move across, so problems show up the same day.

One price per company

Dispatchers, technicians and subcontractors are all on one system. Fieldproxy is one price per company with unlimited users. See /pricing.

The dates

The dates, and how sure they are

DateWhatSource and confidence
October 2019Salesforce acquires ClickSoftwareSalesforce Help notice. Confirmed.
1 January 2016Field Service Edge generally availableClickSoftware Product Life Cycle Policy (December 2023 copy). Confirmed.
31 December 2023End of life for on-premise Service Optimization 8.3Same policy page. Confirmed.
3 October 2026Salesforce publishes the Click Field Service Edge retirement noticeSalesforce Help. Confirmed. The notice gives no end date beyond each subscription's end date.
31 December 2026Field Service Edge end of life, as cited by partnersDiabsolut's FSE end-of-life guide and Solvares. Not found on a Salesforce page we could open.
30 June 2026End of life, as stated by one vendorOverIT, with no source given. Conflicts with the date above; treat as unconfirmed.

The current ClickSoftware lifecycle page was unavailable when we checked on 6 November 2026; its December 2023 copy lists Field Service Edge as subscription based with no end date. Your contract is the authority.

How switching works

Moving from Click Field Service Edge to Fieldproxy

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.

  1. Send us your Click rules and an export

    Skills, territories, windows, priorities and objectives, plus resources and a few weeks of jobs. We list what each rule becomes.

  2. We set up one territory

    Your technicians, skills and real jobs, with work coming in from the system that creates it today.

  3. Compare against Click

    Two weeks of schedules side by side: jobs scheduled, travel, SLA misses. Rules are adjusted until the numbers hold.

  4. Move the rest before your end date

    Territory by territory, with the Watcher agent flagging misses during each cutover.
Salesforce Field Service comparedMoving off Salesforce Field ServiceAI scheduling and dispatchPricing: one price per company, unlimited users

FAQ

Questions people ask

When does Click Field Service Edge reach end of life?
Salesforce's notice says it honors each subscription until its end date and gives no single public date. Partners cite 31 December 2026. Confirm your own date with your Salesforce account executive.
What happens to our data when the subscription ends?
Salesforce says access stops and all associated customer data is deleted, per its Trust and Compliance documentation. Export resources, territories, schedules and history before then.
What does Salesforce recommend instead?
Salesforce Field Service. Its scheduling engine is Enhanced Scheduling and Optimization, which Salesforce documents with its own transition steps, considerations and limits.
We only used Click for scheduling and dispatch. Do we need a full field service suite?
Not necessarily. You need something that takes work orders from your current system, schedules them by your rules, and gets the assignments to technicians. Skedulo, Dynamics 365 with Resource Scheduling Optimization, IFS PSO and configurable FSMs all do this in different ways.
How long does moving off Click take?
One Salesforce partner recommends 9 to 18 months for an enterprise transition. A scheduling-only replacement for one or two territories can be much faster, but plan the cutover well before your end date.
Can we keep Salesforce as our CRM and schedule somewhere else?
Yes. Many schedulers connect to Salesforce. With Fieldproxy, Sales Cloud stays connected and jobs are scheduled and worked in Fieldproxy.
Is 30 June 2026 or 31 December 2026 the right date?
We found 31 December 2026 in partner material and 30 June 2026 on one vendor's page, and neither on a Salesforce page we could open. Your subscription end date is the one that counts.

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.

Related

Keep reading

See it built on your workflow

Tell us how your jobs run today. We build a demo on your stages, forms and pricing before the call.

Get DemoGet Demo