What happened to ClickSoftware

A field manager searches for the year Salesforce bought ClickSoftware, because the board on the wall says Field Service and the old contract says ClickSoftware, and the room has already agreed both labels mean a switch-off is due. Technicians already have appointments. A second search then offers a month when that board will be switched off. The agreement is easy: two names means two systems, and the older name means the jobs must move. The agreement is the problem. Both labels can be true of one product area. The year belongs in the conversation. The month does not.

The distinction that matters is between a sequence of names and a cutover. Salesforce bought ClickSoftware in 2019. Field Service Lightning became Salesforce Field Service in the Winter '21 release. The help page now calls the product Agentforce Field Service and Operations, and it still says Field Service in places. Both labels refer to this product area. A proposal that prices a move from one label to the other is pricing a rename as a build. Rescheduling a day is a later decision. It is not what the purchase did.

What follows are the questions that separate that sequence of labels from a weekend rebuild. Each has a good answer and a bad answer. The difference is whether the answer names the year, the release, the two labels, or a notice that actually ends the product. A general answer is how a rename becomes a false cutover.

A DVD, a Reddit thread, a YouTube clip, a TikTok, a course, a book, or a certification is not a source for the date, the price, or a shutdown.

#The five, and what a bad answer signals

#1. Was ClickSoftware bought, and what did the scheduling product become?

The question is not which word is printed on the workbook. It is whether Salesforce bought the company, and which product the appointments already sit on.

Yes. Salesforce bought ClickSoftware in 2019. The rebrand record says what the scheduling product became, and that sentence is quoted once: "Field Service Lightning, acquired from ClickSoftware in 2019, became Salesforce Field Service with the Winter ‘21 release."

Field Service Lightning is the older name in that sentence. It became Salesforce Field Service in the release the sentence names. Use the older name when you are explaining a search. Do not use it as a separate product you still have to buy.

The acquisition, as the records can tell it, is that 2019 purchase and the change of name through Field Service Lightning to Salesforce Field Service. It is not news that the appointments were thrown away. A workbook in a shared drive with ClickSoftware on the header is a memory of the old company. It is not, by itself, proof that a separate server is still the system of record. If someone can log in to something that is still that old system, say so because they logged in. If they cannot, the workbook is paper. The jobs people run today are the ones on the field product.

The scheduler is already the field product. A story in which ClickSoftware still sits outside Salesforce, waiting to be imported, misreads the year. The import, if people are thinking of one, already happened as a product acquisition. What remains is the name on paper, and the appointments you can already see.

A good answer sounds like the dispatcher opening the board, saying Salesforce bought ClickSoftware in 2019, and saying Field Service Lightning became Salesforce Field Service in the Winter '21 release, with the appointments already on that product.

A bad answer sounds like the workbook header still says ClickSoftware, so the jobs are on a separate server waiting to be imported. A header is paper unless someone has logged in to that old system and can say so. The 2019 purchase is not a queue of appointments still outside the field product.

#2. Which dates can you defend?

1. That is the year in the quoted record. Field Service Lightning became Salesforce Field Service in the Winter '21 release. The record does not add a month or a day to 2019. The release name is the finer mark the record does give. Do not replace it with a calendar day you cannot point at.

Searches for an acquisition date, an announcement, and a timeline get 2019, and they get that release for the Field Service name. They do not get a shutdown date, because none is published in these records.

Do not stack this year with a later rename and call both a migration. The 2019 deal and the later public name are a sequence of labels on the scheduling product. A sequence of labels is not a cutover weekend. Write the year and the release. Leave the weekend off until someone is actually changing how a job is booked.

A good answer sounds like the programme lead writing 2019 for the purchase and Winter '21 for the Field Service name, and refusing to replace the release with a calendar day or to call the later label a migration weekend.

A bad answer sounds like bought sometime before Winter '21, announced on a day we will fill in, and the new name means a cutover weekend. The year is 2019. The finer mark is the release name. A weekend is a project. It is not a second date in the sentence.

#3. Who owns it, and do the two labels mean two systems?

Salesforce owns it. ClickSoftware is not, on these facts, an independent scheduling vendor you still contract with under that name. The help page has moved the public name on again. That sentence is quoted once: "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 it 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 proposal that treats the two labels as two systems, and prices a move from one to the other, is pricing a rename as a build.

Who dispatches a technician on Monday is your organisation. Who owns the product is Salesforce. A Salesforce login does not, by itself, mean every cloud includes the scheduler. Say Field Service, or the longer current name, when you mean the product. Say ClickSoftware when you mean the company bought in 2019, or the word on the old contract.

A printed workbook is not a formula. The sources quoted here do not contain scheduling weights. Do not let a slide invent weights and call them the acquisition.

A good answer sounds like a named dispatcher showing appointments on the board, using Agentforce Field Service and Operations and Field Service as two labels for one product area, with the field contract held separately from a Sales Cloud login.

A bad answer sounds like the help page has a longer name, so we will migrate from Field Service to Agentforce Field Service and Operations, and anyone with a Salesforce login already has the scheduler. The help page says both labels are this product area. A login is not the field contract. The two words are not a from-and-to.

#4. What was paid?

The records cited here do not publish a purchase price or a licence fee. How much Salesforce paid, how much ClickSoftware was sold for, and what you pay for Field Service now are different questions. The cited records are silent on the deal value. The silence is not filled with a figure.

Your field licence is your contract. It is not printed in the rebrand sentence or the help sentence. A search for the acquisition price should stop on that silence. A headline that is not cited is not a source, even if it sounds familiar in a meeting.

Why Salesforce acquired ClickSoftware, and why the company sold, are not in the two sentences quoted above. One sentence gives the 2019 acquisition and the Winter '21 name. The other gives the current public name, and the fact that Field Service is still used in places. Neither gives a motive. A motive supplied for the slide cannot be checked against those sentences.

Impact on customers, as far as the records will say it, is the path of the name. Scheduling bought from ClickSoftware became Field Service, and the help page now also says Agentforce Field Service and Operations. Customers are not given an end date. They are not told the board they already use is a legacy system that must be rebuilt because the company was bought.

A good answer sounds like procurement stating that neither cited record prints a 2019 price, then reading the field licence off the contract the organisation holds, without turning a familiar headline into either number.

A bad answer sounds like the acquisition had a price everyone has heard, so that price is the licence, and the longer name means a new fee. The records are silent on the deal. The licence is the contract. The longer name is a label, not an invoice.

#5. Does Field Service have an end date?

The records do not give Field Service an end date. Do not invent one. The longer name is a rename of the product area. It is not a notice that the shorter name has been switched off.

The help page says that in some cases Field Service is still used in the applications and the documentation. That sentence is the opposite of a shutdown. Both labels are in use for this product area. A slide that retires Field Service because the longer name exists has retired a label, and then priced the retirement as if the appointments had to move.

Do not borrow an end date from a product that was actually retired and pin it to ClickSoftware. Social tools and a data-management platform in this set have dated endings. Field Service does not. The deals are separate.

An old contract that still says ClickSoftware can be read as paper behind the current name. Correcting the paper is not a switch-off. If a seller warns that 2019 means the board stops, ask for the notice that names the product and names the day. If they only have the rename sentences, the warning comes off. If someone asks whether customers were forced off ClickSoftware onto a new scheduler, the record describes a rename of the scheduling product, not a second build you must still enter. Forced and worth-it need the appointments you can see.

A good answer sounds like the field manager showing the board still taking appointments, quoting the help page that Field Service is still used in places, and showing that no notice names a day for this product.

A bad answer sounds like a social tool or a data platform ended on a dated notice, so the field board ends then too, because 2019 was an acquisition. Those endings name their own products. The help page kept both labels. A borrowed day does not become this product's end date.

#What to do with the answers

Read the five as a set. Specific answers mean the board stays, under the labels the help page allows. General answers mean the room has agreed that a longer name is a migration, which the help page does not say.

Open the board the dispatchers already use. If appointments are there, you are on the product the acquisition became, whatever the workbook header says. Write the two labels the help page allows: Agentforce Field Service and Operations, and Field Service where the screen still says that. They are one product area, not a from-and-to. Four lines answer the searches. Bought in 2019. Became Salesforce Field Service in the Winter '21 release. Now also named Agentforce Field Service and Operations, with Field Service still used in places. No end date and no purchase price in the cited records. Those lines do not set duration, skill, or territory. Keep ClickSoftware in a glossary if the contract still prints it. Do not let the glossary become a second system, and do not let the longer current name evict the shorter one. A board pack can carry those lines and no deal value.

The scheduler is already the field product. A migration that ignores duration, skill, and territory rebuilds a bad day under a new heading. That scope is on the ClickSoftware implementation page.