# ClickSoftware is Field Service

ClickSoftware scheduling was acquired in 2019 and became Field Service, now named Agentforce Field Service and Operations, with Field Service still used in places. Do not invent a scheduling formula.

**Published:** 2025-12-09
**Canonical:** https://synconai.com/clicksoftware-field-service
**Author:** SynconAI Architecture Team

## In short

ClickSoftware scheduling was acquired in 2019 and became Field Service. The help page now calls the product Agentforce Field Service and Operations, and it still uses Field Service in places. There is no optimizer formula on this page, and a quote must not invent one. A migration back into Salesforce prices a product you already run. Cost is scope, licences, people, and cutover, with no number here.

## Sources

- **The ultimate guide to Salesforce product rebrands** (retrieved 2026-10-10)
  https://gearset.com/blog/salesforce-product-rebrands/
  > Field Service Lightning, acquired from ClickSoftware in 2019, became Salesforce Field Service with the Winter ‘21 release.
- **Field Service** (retrieved 2026-10-10)
  https://help.salesforce.com/s/articleView?id=service.fs_overview.htm&type=5
  > Field Service is now Agentforce Field Service and Operations. In some cases, we still use Field Service to refer to this product area in Salesforce applications and documentation.

## What to take away

- ClickSoftware scheduling was acquired in 2019 and became Salesforce Field Service.
- The help page now says Agentforce Field Service and Operations, and still uses Field Service in places.
- Neither source publishes an optimizer formula. A slide that invents one is not a plan you can check.
- A retired product is a different quote from a renamed one. Field Service is the product you already have under the newer name.

## The guide

A dispatcher keeps a ClickSoftware workbook in a shared drive, printed once and never thrown away. A partner sees the workbook and prices a migration of that scheduling into Salesforce, with a weekend cutover and a slide that shows how the optimizer scores a job. The slide has weights. Travel sits next to skill, and a weighting says which one wins. Nobody in the room can point at a help page that states those weights. The jobs the dispatcher cares about are already on the Field Service board. The workbook is a memory. The formula is an invention. The quote has priced both as if they were a specification.

The board is not empty. Technicians already have appointments. The migration, as sold, would build a second copy of a day the organisation can already see, and would justify the copy with maths the sources do not contain.

## Two sentences, and no formula

The rebrand note names the acquisition and the release: "Field Service Lightning, acquired from ClickSoftware in 2019, became Salesforce Field Service with the Winter ‘21 release." Scheduling bought from ClickSoftware became Salesforce Field Service. Field Service Lightning is the older name in that sentence. Use it when you are explaining a search query. Do not use it as the name of a separate product you still have to buy.

The help page has moved the public name on again. "Field Service is now Agentforce Field Service and Operations. In some cases, we still use Field Service to refer to this product area in Salesforce applications and documentation." Read that slowly. The product is now Agentforce Field Service and Operations. In some places the applications and the documentation still say Field Service. Both labels refer to this product area. A quote that treats the two labels as two systems, and prices a migration from one to the other, is pricing a rename as a build. Ask them to show you the org. If the appointments are already there, the build they are selling is not a homecoming. You are home.

What the sources do not contain is an optimizer formula. They do not give you weights, a score, or a ranking of factors. This page will not invent that formula, and a partner must not invent it on a slide and call it documentation. If a design needs a weighting, the weighting is a rule you write and test in your org, not a secret recovered from ClickSoftware. A quote that depends on the secret is a quote you cannot verify. Send the slide back. Ask what they will configure that you can see on a record, and what they are only guessing.

## The workbook is not the system of record

The shared workbook feels like the product because it is what people trust when the screen confuses them. Trust is not architecture. Before anyone prices a migration, sit with the dispatcher and mark each column. Already on a Field Service record. Kept only in the workbook. Abandoned. The first set is not a migration. The second set is a decision: type it onto the records you have, or stop promising it. The third set is a deletion of a habit, which is a meeting, not a data load.

Do not call the workbook ClickSoftware if the company has not opened that system in years. Old names stick to spreadsheets. The acquisition was in 2019, and the Field Service name arrived with the release the note cites. If a server still exists, say so because someone can log in, not because the workbook header says so. A partner who wants a server extract should show you the server. If they cannot, the extract is fiction, and the price for the extract comes off.

A renamed product can still need work. Territories can be wrong. Skills can be blank. Appointments can be created by hand because nobody trusts the board. That work is configuration and data quality on Agentforce Field Service and Operations. It is not a migration from ClickSoftware unless a live ClickSoftware system is still producing the day. Say which of the two you mean in the first paragraph. The rest of the quote depends on it.

## What the cost is made of

No figure on this page. Field service programmes collect fake precision: a formula, a utilisation rate, a promised saving in kilometres. Leave the precision out until four lines are dull and true.

Scope is the records you will change: work orders, service appointments, territories, and the people assigned to them, named as objects in your org rather than as a slogan. Scope says whether the workbook's extra columns are in or out. Scope says you are not rebuilding Field Service from an empty org if the org is not empty. A rename is not scope. If the only delta is the words ClickSoftware on a contract, the scope is a contract edit.

Licences are the Field Service licences you already pay. The newer public name does not, on this page, create a second licence you must buy to "be on Agentforce". If a seller proposes an add-on, it is a separate line with a reason that is not the 2019 acquisition. You already completed the acquisition's product outcome when the scheduling ran as Field Service. Paying again so a slide can use the newest label is a purchase, not a correction. Put the current contract on the table before anyone adds a row.

People are the dispatcher, a technician who will say whether the phone matches the board, and the administrator who can open a territory. Partner hours without those people will design a day the crew will not run. Internal time on ride-alongs and on arguing with one appointment is a cost. Count it. A formula slide does not reduce that time. It moves the argument into numbers nobody can audit.

Cutover is a morning when the crew takes the day from a different place. You need it if a live external scheduler is still issuing the day and you are stopping that. You do not need it to admit that ClickSoftware became Field Service several releases ago. If the cutover plan's only system is the one you already use, there is no cutover. There is a training session on the current name, and training should be priced as training. Do not dress it as a go-live.

## What a partner points at

They open your org and point at a work order, a service appointment, and a territory without asking what Field Service means. They say Agentforce Field Service and Operations, and they are not surprised when a screen still says Field Service. They will not take on an optimizer formula. They will not take on a migration from a server they have not seen. They will not take on a promise about travel time that is not already a field you both agree to maintain.

Ask them what they will refuse in writing. The useful refusals are short. We will not invent weights. We will not quote a move from Field Service to Agentforce Field Service and Operations as if they were different estates. We will not treat the workbook as a system of record without a column-by-column check. A partner who will not write the refusals will write the formula instead, because the formula looks like expertise. Expertise here is the willingness to say the maths was not published.

A product that was retired is a different kind of quote. RelateIQ became SalesforceIQ and was then retired. There is no org of that product to implement now. Field Service is not that story. The scheduling product is still the one in the help page, under the current name. If a bidder talks about ClickSoftware as a corpse you must leave, show them [the RelateIQ guide](/relateiq-salesforceiq) and ask which sentence they think applies. The retirement sentence will not be this one. This one is a rename, twice, and the work is whatever is wrong on the board you have.

## Who is allowed to say the day is wrong

The dispatcher is. A consultant can propose a territory change. They cannot declare last winter's patch correct from a map in the proposal. Walk one real day. Pick one appointment that was late or was the wrong person. Write the record that made it so: a missing skill, a territory membership, a duration somebody guessed, a workbook column that never reached the org. Fix that class of record if you still want the work. Do not generalise one bad day into a replacement of the product.

Technicians see the mobile experience, whatever the current label is. If the quote includes the phone, say what the technician cannot do today that the product is supposed to do, and check that gap against the org before you buy around it. A gap that is a permission, a layout, or a blank field is not a reason to revive ClickSoftware as a project name. It is a reason to edit the org. Price the edit.

Contractors on the crew belong in the same conversation. If they are scheduled, they are part of the data. A quote that models only employees will look finished and fail on the first week a contractor is the person available. This page will not give you their commercial terms. It will tell you to put their working pattern on the records if you intend to schedule them. Leaving them in the workbook keeps the workbook alive, which is how ClickSoftware survives as a word.

## What to do with the proposal

| Line they wrote | What it actually is | What you send back |
| --- | --- | --- |
| Migrate ClickSoftware into Salesforce | Scheduling that became Field Service, now named Agentforce Field Service and Operations | Ask whether a live old system still issues the day. If not, drop the migration |
| Optimizer weights on a slide | A formula neither source publishes | Delete the weights. Ask which records they will change |
| Cut over from Field Service to Agentforce | Two labels for one product area | Price training or configuration, not a second estate |
| The workbook is the scope | A spreadsheet with mixed trust | Mark each column: on the record, still wanted, or dead |
| One number for the scheduling transformation | Four costs and a guessed formula | Split scope, licences you pay, people, and cutover only if the day changes address |

::: warn
Do not accept an optimizer formula as if it were documented. The acquisition note and the help page rename the product. They do not publish weights. A quote that needs those weights is inventing the mechanism it claims to implement.
:::

Give every bidder the same instruction. Use Agentforce Field Service and Operations as the product name, and expect Field Service on some screens. Do not price a migration from ClickSoftware unless you can log into ClickSoftware. Do not include a formula you cannot show in a help page. Return scope, the licences we already pay, the dispatcher and the administrator, and a cutover only if an external board is actually stopping.

The reply that passes opens the appointment you named and talks about the record. The reply that fails opens with a score. You are allowed to stop at the score. The 2019 acquisition already moved the scheduling into Field Service. The later name change did not move it out. What is left is the quality of the day on the board, and that quality is a set of records, a set of people, and a refusal to decorate the work with maths you were not given.

If someone asks for a legal reading of the old ClickSoftware contract, this page is not it. Take the paper to the people who own it. The delivery question is whether that paper still has a system behind it. If it does not, stop paying for a migration from a system you cannot start. Pay, if you pay, for the board you can already open.

## The other searches

The project quote is on [clicksoftware implementation cost](/clicksoftware-salesforce-implementation-cost). That page does not print a figure. Who bought the company is on [what happened to clicksoftware](/what-happened-to-clicksoftware). The connector is on [integrating clicksoftware with Salesforce](/integrating-clicksoftware-with-salesforce). Whether to move is on [should I migrate from clicksoftware](/should-i-migrate-from-clicksoftware). The customer fee is on [clicksoftware licence cost](/clicksoftware-salesforce-licence-cost). Who to hire is on [hiring for clicksoftware](/hire-clicksoftware-salesforce-partner). This page does not rank an agency.


## Questions

### What should a ClickSoftware data migration quote include?

It should say whether a live ClickSoftware system still produces the day, or whether you already run Field Service. It should use Agentforce Field Service and Operations as the current name and expect the Field Service label on some screens. It should list records to change, not an optimizer formula. Split scope, licences, people, and cutover. A workbook is not a system until someone proves it is.

### What is a ClickSoftware implementation cost made of?

Scope of the appointments, work orders, and territories you will change. Field Service licences you already pay. People, including the dispatcher. Cutover only if an external scheduler is actually stopping. A rename from ClickSoftware, and the later rename to Agentforce Field Service and Operations, are not a second licence and not a weekend. This page will not print a price or a formula.

### What is the Field Service optimizer formula from ClickSoftware?

Neither source on this page publishes one. ClickSoftware scheduling became Salesforce Field Service, and the help page now says Agentforce Field Service and Operations while still using Field Service in places. Weights on a slide are not that history. Do not implement a formula you cannot point at. Configure records you can open.

### How do you judge the best ClickSoftware integration agency?

Do not rank agencies, including SynconAI. A partner passes if they name Agentforce Field Service and Operations, open a real appointment, refuse an invented formula, and refuse a migration from a server they have not seen. They say what they will not take on. A scoring model is not that test.

### When should you hire a ClickSoftware consultant or implementation partner?

Hire when you know the board you have is the product, and you can name the records that make a day wrong. Hire someone who will not sell a journey from Field Service to Agentforce as a migration. If they lead with optimizer weights, do not hire them for this. The acquisition already happened. The work is the board.

### Is clicksoftware owned by Salesforce?

Yes. Salesforce bought ClickSoftware in 2019. The full account is at https://synconai.com/what-happened-to-clicksoftware.

### When did Salesforce acquire clicksoftware?

2019. Field Service Lightning became Salesforce Field Service in the Winter ’21 release.

### What happened to clicksoftware after the Salesforce acquisition?

The help page calls the product Agentforce Field Service and Operations, and still says Field Service in places.

### Should I migrate from clicksoftware to Salesforce?

The scheduler is already the field product. A “migration to Salesforce” that ignores duration, skill, and territory will rebuild the same bad day.

### What is the clicksoftware licence cost, or the price Salesforce paid?

The page this guide cites does not publish a purchase price or a licence fee. The licence read is at https://synconai.com/clicksoftware-salesforce-licence-cost.

---

SynconAI is a Salesforce Select Partner and an OpenAI Select Partner, delivering architect-led Salesforce and AI programmes across the United States and Australia. Related service: Field Service (https://synconai.com/salesforce-field-service).