Skip to main content
Plans are a more powerful, conversational way to build multi-step processes in Mindset AI. If you’ve used Workflows or Capabilities to define how your agent handles a process, this guide explains how to move that work across to Plans.
We’re aiming to deprecate Workflows on 31 July 2026. Until then they keep working and there’s no automatic conversion, so plan to move each process over to a Plan before that date. This date is a target and may change. We’ll update it here if it does. If you’d like help with your migration, please contact your Customer Success Manager.

​
How a Plan runs a step differently

A Workflow runs each step as a set operation, such as prompting the model, fulfilling a goal, searching your knowledge, or showing content. A Plan is carried out by the agent in conversation: it reads each step as a plain-language instruction and works through it with the user, searching your knowledge and applying any attached Skills, and adapting to the person it’s talking to. The practical effect for migration is that the agent interprets each step rather than running a fixed operation. The wording usually transfers directly, so it’s worth testing each Plan and tweaking the instruction if the agent does something slightly different.

​
How Plans start

A Workflow is started explicitly, from a welcome card or triggered in code. A Plan can start those ways too, and the agent can also choose to run it when what the user says matches the Plan’s description. This is known as an implicitly triggered Plan. Give the Plan a clear description so it triggers at the right time.

​
How Plans reach an agent

To give a Workflow to an agent, you had to add it to a native MCP server first. Plans skip that step. You attach a Plan directly to an agent, in the Agent Management Studio, or through the Agents API or the Agent Sessions API. There’s nothing to wrap it in, which makes Plans simpler to set up and assign.

​
Two ways to move a Workflow across

You don’t have to do this one way. Take it case by case:
  • Map step for step. Copy each Workflow step across as a Plan step: the step name becomes the Plan step name, and the step’s prompt or goal text becomes the Plan step’s instructions. This works well when your steps are already clear instructions.
  • Describe the goal. Tell the Plan Creator Agent what the process should achieve and let it draft the steps, then compare them to your Workflow and adjust. This works well when you’d rather start from the outcome.
You can mix the two: let the agent draft, then tighten individual steps by hand. The settings a Workflow step carried, such as which model to use or exact search terms, don’t transfer, and the agent works those out from your instruction.
Before you start
  • Have your existing Workflow open so you can see its steps and what each one achieves.
  • Make sure the agent you’ll attach the Plan to is set up, with the knowledge it needs available to it.

​
Migrate a Workflow to a Plan

1

List the Workflow's steps and what each one achieves

Focus on the outcome of each step.
2

Create a new Plan

In the Agent Management Studio, go to Plans and select New plan. Either copy your steps across or describe the process to the Plan Creator Agent. See Create a Plan for the full walkthrough.
3

Set each step

Copy the Workflow step’s name and its instruction text into a Plan step, or adjust the steps the agent drafted for you.
4

Set the name, handle, and description

The description is how the agent decides when to run the Plan, so be specific about the scenario that should trigger it. Keep the handle unique across your Plans and Skills.
5

Choose strict step order

Turn it on if the agent must follow every step in order, or off if it can skip a step it already has the answer for.
6

Assign the Plan to your agent

A Plan only runs for the agents it’s assigned to.
7

Test it

Run the process and check the agent reaches the same outcome the Workflow did.
8

Optionally, add a Skill

You can capture a piece of knowledge the process relies on, such as a framework, a set of guidelines, or reference material, as a Skill and attach it to the Plan to enhance it. See Create a Skill.

​
Migrating a Capability to a Plan

A Capability is a pre-set prompt and set of steps on an agent, often shown to users as a welcome card or in the prompt menu. Capabilities move to Plans too, and this is the simplest migration of all.
1

Copy the Capability

Open the Capability and copy its prompt or its steps.
2

Create a new Plan

In the Agent Management Studio, go to Plans and select New plan.
3

Let the Plan Creator Agent draft it

Paste the prompt or steps into the Plan Creator Agent and let it create the Plan for you.
4

Review the result

Check the name, handle, description, and steps, and adjust anything you want. See Create a Plan.
5

Turn on the welcome card if the Capability had one

If the Capability was shown as a welcome card, turn the welcome card on for the Plan so users still see it.
6

Assign and test

Assign the Plan to your agent and test it.

​
Start moving over soon

You can migrate one process at a time. Plans and Workflows run side by side, so you can move a process across, test it, then come back for the next one. Your Workflows keep working until you migrate them. Workflows will be taken offline, though, currently targeted for 31 July 2026. The sooner you start moving processes over and testing them as Plans, the more room you give yourself before that date, and the sooner you get the benefit of Plans: a more natural, conversational experience and processes you can update in plain language. Once you’re confident a Plan does what the Workflow did, you can stop using that Workflow.

​
Next steps

Create a Plan

The full walkthrough.

Create a Skill

Capture knowledge for your Plans.