ChatGPT
Claude
Google AI
Copilot
Platform & ArchitectureThe room usually agrees that an acquisition is a reason to move the automations. An administrator exports a list of Flows on a Friday and titles the sheet "move to Regrello". There are forty rows. Twelve of them assign a task, update a field, and stop. They have done that for two years. The business knows the outcome. The sheet treats the close as a reason to lift every automation into a new tool.
That agreement is the problem. Regrello automates complex processes. Salesforce planned to integrate that work with Agentforce and Slack. It does not replace every Flow. Customers were not told that Flow Builder had been withdrawn, and they were not told that every existing automation must be redrawn. A process that already has a right answer is the test. If a person can point at the field, the value, and the record, the step is finished work. Moving it because a company was bought creates a second writer and a new failure.
The completion line is the sentence worth keeping in the brief, unchanged.
"Salesforce completed its acquisition of Regrello on October 1, 2025."
What follows separates the keep-list from the processes that still need a design. 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 export actually for | The administrator who titled the sheet | Forty Flows are priced as one move |
| Who owns Regrello, and who owns a step | Salesforce for the company; the person who can say the step is done | Two writers are created for a field that already had one |
| What does 1 October 2025 decide | Whoever is writing the timeline, from the announcement | The close is reused as a weekend that moves every automation |
| What may be written about price | Finance, with the announcement and the separate agreements | Flow, Agentforce, and Slack are added into one total |
| Is there a shutdown to schedule | The person who can refuse to move a Flow | Flow, or Regrello, is given a quarter the announcement does not have |
| What would you actually move | The person who can mark stay or candidate on a real process | Slack is drawn as the system of record |
What is the export actually for?
The question is not how many Flows you have. It is which of them lack a right answer, because those are the only ones the acquisition gives you a reason to reconsider.
A complex process is one where the next step depends on a judgement, a wait, or a person outside the org. A simple one updates a status you already defined. The twelve rows that assign a task, update a field, and stop have done that for two years. They are the keep-list, not the backlog. What you run beyond them is local. Some orgs have a handful of Flows a single administrator can open. Some have hundreds, plus Apex, plus a process that still lives in email. The announcement cannot see that list, and it will not tell you which rows are complex.
Spend the close on the processes that do not have a right answer yet: many people, many systems, a path that changes when a fact arrives late. A quote that says "replace automation" has not made that cut.
A good answer sounds like the administrator marking the twelve finished rows as stay, and naming one process whose next step still depends on a judgement nobody has written down.
A bad answer sounds like move all forty, the company was bought on 1 October 2025. The date is real. It is not a reason to give a finished field a second writer.
Who owns Regrello, and who owns a step?
Salesforce owns Regrello. Salesforce completed the Regrello acquisition on 1 October 2025. Did Salesforce buy Regrello? Yes. That is not a partnership, and it is not a template pack that appeared inside Flow.
Who owns a process is the person who can say the step is done. Salesforce owning the product does not own your approval rules, your Slack channel, or the Flow that already writes the field. If the same field has two writers after a move, you have created an argument the acquisition did not ask for.
Who owns the decision to leave a Flow alone is the same person. Write the refusal down. "This step stays in Flow because the outcome is fixed." That sentence is a scope cut. It is also how you stop a programme from becoming a rewrite of the org. The brand owner is Salesforce. The step owner is yours.
The cited announcement does not publish a headcount, a founder note, or a jobs list. Working at Regrello after the acquisition is not answered there. A profile is not a process map. Do not staff a design from a career post. Why Salesforce acquired Regrello, beyond complex processes with Agentforce and Slack, 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 owner who can point at the field, the value, and the record for each of the twelve rows, and who has written that those steps stay.
A bad answer sounds like Salesforce owns automation now, so the Flows changed owner on the close. The company owner changed. The person who can say a step is done did not.
What does 1 October 2025 decide?
The date is 1 October 2025. Use that form in the brief. The quoted sentence writes the day month-first, as the page was published. Same day. Do not add a "Flows end" date beside it. The announcement does not have one.
Completion means the acquisition closed. It does not mean your automations moved that morning. It does not mean Slack became the system of record. It does not mean a contract line changed, unless your order form says so. Open the order form for fees and start dates. The announcement has the close only.
Before that day, Regrello was a separate company automating complex processes. On it, Salesforce completed the purchase and planned to integrate the work with Agentforce and Slack. After it, the announcement does not invent a shutdown of Flow, a price, or a rename. A plan to integrate is not a cutover date. Do not tell a team their Slack workspace will be rebuilt on the close. If a later Salesforce page states a date the announcement does not, cite that page.
A good answer sounds like the programme lead reading 1 October 2025 from the announcement, and reading any migration weekend from the project plan, labelled as a different document.
A bad answer sounds like the Flows move on 1 October 2025 because that is the completion date. The date marks the purchase. It does not mark a cutover of every automation.
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 Regrello was sold for, stay blank. A completion notice is not a consideration figure.
What you pay for Flow, for Agentforce, or for Slack is on your agreements. Those are separate products with separate contracts. Do not add them into a Regrello total. There is no free trial on the cited announcement. Do not type zero. Zero would claim the consideration was nothing, and the announcement does not say that.
The cost that matters for a build is the list of processes you are willing to move, plus the ones you refuse. That list is not a purchase price, and it does not belong in the acquisition cell.
A good answer sounds like the finance partner leaving the acquisition cell blank, with the Flow agreement, the Agentforce agreement, and the Slack agreement kept as three documents.
A bad answer sounds like one number for automation, covering the export and the close. That number mixes a consideration the announcement does not publish with products you already pay for separately.
Is there a shutdown to schedule?
No end date is published for Regrello. There is no sunset quarter, no instruction to switch the product off, and no instruction to switch Flow off. A search that includes the word shutdown has not found a notice.
Leaving a Flow in place is not a sunset. It is a decision that the step already works. You can retire a Flow when the business retires the step, with an owner and a test. You do not retire it because Regrello was acquired on 1 October 2025. Those are different calendars. Do not tell an administrator their Flow list expires in the following quarter. That sentence is not on the announcement.
On a risk register, write the blanks and the boundary. No end date. No published price. Does not replace every Flow. Then point at the twelve rows that stay. The register should produce a keep-list, not a guessed quarter.
A good answer sounds like the step owner stating there is no end date for Regrello or for Flow, and pointing at the twelve rows that stay because the outcome is fixed.
A bad answer sounds like cross Flow out, and give Regrello a sunset next quarter so the template is complete. Neither instruction is on the announcement.
What would you actually move?
When the lines above are accepted, ask which process is complex, who owns the finish, and which steps stay in Flow or Apex because they already have a right answer. Ask a partner to mark three Flows as stay, and one process as a candidate, before they name a fee. A pass can say why the three stay. A fail prices the whole export, or types a purchase price the announcement does not contain.
A demo after the acquisition is a walk through one complex process in your nouns, or a demo Salesforce will show you now. It is not a tour of forty Flows. A roadmap is a Salesforce page read on the day you read it. Do not sketch a world in which Flow has been retired by a completion notice, and do not draw Slack as the new system of record.
A good answer sounds like one complex process, the person who says it is finished, and the Flows that will not be touched, including the twelve that assign a task, update a field, and stop.
A bad answer sounds like replace the export, rebuild the Slack workspace, and retire Flow. That is three decisions the close did not take, attached to a date that only marks the purchase.
What to do with the answers
Read the six as a set. Specific answers mean the keep-list exists and the complex process has an owner. General answers mean the decision rests on an export being treated as a scope.
If the answers are specific, the next discipline is the process that does not yet have a right answer, set out in Regrello and Agentforce. If they are not, the useful outcome is a sheet whose title no longer says move. Keep this page for the lines a finance partner will check: owned by Salesforce, completed 1 October 2025, complex processes planned with Agentforce and Slack, does not replace every Flow, price not published, no end date.
