ChatGPT
Claude
Google AI
Copilot
Platform & ArchitectureThe room usually agrees that the familiar document is the right one. A programme manager receives a migration quote with Apromore in the title and no process in the body. The quote lists objects, a weekend, and a fee. It does not say which work is slow, which handoff waits, or which step is done twice. She asks what happened to the product. The answer is not a loader.
That agreement is the problem. Apromore is process intelligence. It discovers how work runs, simulates a change, and optimises the path you can already describe. It is not a data-migration tool. If you cannot describe the process, a migration quote is the wrong document. The close tells you who owns the company and when the purchase completed. It does not turn a mystery process into a cutover plan. People reach for a migration because the word is familiar. Familiar is not the job.
The completion line is the sentence worth keeping in the brief, unchanged.
"Salesforce completed its acquisition of Apromore on November 3, 2025."
What follows asks whether anyone can describe the work. A good answer names a person, a document, a product, or a year. A DVD, a Reddit thread, a YouTube video, a TikTok, a course, a book, or a certification is not a source for the date, the price, or a shutdown.
| Question | Who has to answer it | What a bad answer usually means |
|---|---|---|
| What is the quote actually buying | The programme manager who received it | Objects and a weekend stand in for a process |
| Who owns Apromore, and who owns the work | Salesforce for the company; the person who can say what done means | A diagram is accepted with nobody willing to change the work |
| What does 3 November 2025 decide | Whoever is writing the timeline, from the announcement | The close is booked as a migration weekend |
| What may be written about price | Finance, with the announcement and the order form | A loader's fee is written into the acquisition cell |
| Is there a shutdown to schedule | The process owner, after the wait can be seen | A bad process and the product are given the same end date |
| What do you bring to the first meeting | The person who counted, with instances that can be opened again | A slide of boxes is treated as a baseline |
What is the quote actually buying?
The question is not whether records will move someday. It is whether this product is the thing that moves them. It is not.
Salesforce bought Apromore. The product discovers, simulates, and optimises how work runs. Customers were not given a new import wizard. They were not told to empty one org into another under this name. The close placed a way to see a process. It did not place a way to skip seeing it. A partner who sells a data load against this name has changed the product.
What you can see today is local. Some teams can open ten real cases and say where each one waited. Some teams have a slide with boxes and no timestamps. The announcement cannot see your cases, and it will not invent a bottleneck. Discovery starts from instances you can open again, with a date and a person who counted.
Separate the wait from the work. A case that sat for six days in one status is a different fact from a case that took six days of effort. The acquisition does not tell you which you have. The count does. Write the count in the brief before anyone attaches the word migration to a fee.
A good answer sounds like the programme manager saying the quote is the wrong document, that Apromore discovers, simulates, and optimises, and that no process has been named yet.
A bad answer sounds like book the weekend and load the objects. The weekend is a habit. It is not what the announcement bought.
Who owns Apromore, and who owns the work?
Salesforce owns Apromore. Salesforce completed the Apromore acquisition on 3 November 2025. Did Salesforce buy Apromore? Yes. That is not a connector you rent for a weekend move, and it is not a rumour still awaiting a close.
Who owns the process is the person who can say what done means for one instance. Salesforce owning the company does not own that definition. A discovered path that nobody accepts is a picture. An accepted path has an owner who will change the work, not only the diagram. Name that person before you name a tool.
Who owns the numbers is the person who counted. A baseline without a counter is a workshop estimate. Write the date of the count and keep the identifiers so the same kind of instance can be opened again. The brand owner is Salesforce. The process owner, and the counter, are yours.
The cited announcement does not publish a headcount, a founder note, or a jobs list. Working at Apromore after the acquisition is not answered there. A profile is not a process baseline. Do not hire from a career post and call it discovery. Why Salesforce acquired Apromore, beyond process intelligence, is not a motive you can recover from the completion line, and why the company sold is not stated there.
A good answer sounds like a named process owner who can define done, and a named counter who can open the same ten instances again, with the date of the count written down.
A bad answer sounds like the tool will find the process later, so the owner can skip this meeting. The announcement did not appoint an owner inside your company.
What does 3 November 2025 decide?
The date is 3 November 2025. Use that form in the brief. The quoted sentence uses the month-first form from the published page. Same day. It is not the day your records moved, and it is not the day a simulation became a decision.
Completion means the acquisition closed. It does not mean a migration ran. It does not mean a sandbox was loaded. It does not mean a contract line changed, unless your order form says so. Open the order form for commercial dates. The announcement has the close only.
Before that day, Apromore was a separate company doing process intelligence. On it, Salesforce completed the purchase. After it, the announcement does not invent a shutdown, a price, or a second life as a migration utility. If a later page states one of those, cite that page. Do not paint it onto this close.
A good answer sounds like the programme lead reading 3 November 2025 from the announcement, and refusing to write that date into a migration weekend.
A bad answer sounds like the records move on 3 November 2025 because that is when the company was bought. The date is the close. It is not a load.
What may be written in the price cell?
The cited announcement does not publish a price, a purchase price, or a licence fee. How much Salesforce paid, and how much Apromore was sold for, stay blank. Completion is not a consideration disclosure.
There is no free trial on the cited announcement. What you pay to run Salesforce, or to engage a partner, is on your own papers. Do not type zero. Zero would claim the deal was nothing. Do not type a migration fee into the acquisition cell either. A migration fee is a different document, and for this product it is often the wrong document.
A simulation is a question about a change you might make, not a promise the change will pay for itself. Name the change in one sentence before anyone talks about cost. More people on the queue. Fewer approvals. A different handoff. If you cannot say the change, you are not ready to simulate, and you are not ready to migrate. The time to name one process, count a baseline, and simulate one change is the work. It is not a purchase price.
A good answer sounds like the finance partner leaving the acquisition cell blank, and asking which change would be simulated before any other fee is discussed.
A bad answer sounds like put the weekend's fee in the acquisition cell so the business case has a number. That fee is not the consideration, and the announcement did not publish one.
Is there a shutdown to schedule?
No end date is published for Apromore. There is no sunset quarter, no instruction to switch the product off, and no instruction to stop a migration that this product was not doing. A search for shutdown does not create a notice.
You can stop a bad process. That is an operational decision by the process owner, taken after you can see the wait. It is not an acquisition sunset. Do not confuse "we will no longer do the work this way" with "Apromore ends on a date". The first can be true in your business. The second is not on the announcement.
On a risk register, write three lines. No end date. No published price. Not a data-migration tool. Then name the process you can actually describe. If you cannot name it, the risk is the missing description, not a hidden shutdown.
A good answer sounds like the process owner stating there is no published end date, and that any decision to stop a bad process waits until the wait can be seen.
A bad answer sounds like sunset the product next quarter so the migration has a reason to hurry. The quarter was chosen for the template. The announcement did not choose it.
What do you bring to the first meeting?
When the lines above are accepted, bring one process, a baseline with a counter and a date, and a change you might simulate. Ten instances are enough if they are real and you can open them again. Ask the partner to refuse the migration quote in writing. A pass says which process, which wait, and what they will not load. A fail sends a mapping spreadsheet and a purchase price.
A demo after the acquisition is those instances, timed, or a demo Salesforce will show you now. A roadmap is a Salesforce page read on the day you read it. Do not sketch a loader, and do not sketch an end date. Do not tell a data team that Apromore will move their records.
A good answer sounds like ten instances of one process, the person who counted them, the date of the count, and one change stated in a single sentence.
A bad answer sounds like a mapping spreadsheet, a weekend, and a purchase price. That is the quote the announcement does not support.
What to do with the answers
Read the six as a set. Specific answers mean the process has a name and a counter. General answers mean the decision rests on a migration being the familiar next step.
If the answers are specific, the next discipline is the map, set out in Apromore and process intelligence. If they are not, the useful outcome is a quote you can send back before the weekend is booked. Keep this page for the lines a finance partner will check: owned by Salesforce, completed 3 November 2025, process intelligence, not a migration tool, price not published, no end date.
