ChatGPT
Claude
Google AI
Copilot
Platform & ArchitectureA 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 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 |
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. That page does not print a figure. Who bought the company is on what happened to clicksoftware. The connector is on integrating clicksoftware with Salesforce. Whether to move is on should I migrate from clicksoftware. The customer fee is on clicksoftware licence cost. Who to hire is on hiring for clicksoftware. This page does not rank an agency.
