Skip to main content
Migration turns an existing node-based Workflow into an Agent. AI Marketer (Aim) reads the nodes in your Workflow and writes an Agent with equivalent instructions, tools, and outputs. Your Workflow isn’t changed, so you can compare the two and switch over when you’re ready.

​
Why migrate?

Migrate your Workflows to Agents if you want:
  • Easier updates: describe the change in the Agent’s chat and Aim makes it.
  • Triggers beyond a schedule: web monitors, Profound data changes, and app events such as Slack messages. Learn more in Triggers in Agents.
  • Flexibility with unexpected inputs and fewer broken runs: the Agent reasons through the run and works around common issues.
Migration is optional. Agents don’t affect your existing Workflows; they keep running as they are.

​
Before you migrate

  • Check the tools. Some integrations available to Workflows aren’t available to Agents as tools yet. Note the tools your Workflow uses and compare them against the list in Tools in Agents. If a tool is missing, consider running the Workflow from an Agent instead.
  • Check the credit cost. Once credit billing for Agents starts, an Agent run uses more credits than the same Workflow run, because Aim reasons through each step. Keep high-volume, fixed tasks as Workflows.
  • Save an example of good output. Use it to judge the migrated Agent’s first run.

​
Migration steps

1

Start the migration

  1. In Profound, go to Agents in the left sidebar and filter by Type to find the Workflow you want to migrate.
  2. Select the Workflow to open it.
  3. Select Migrate at the top right of the screen. In the Migrate to the new Agents experience? dialog, select Migrate.
Profound creates a new Agent and opens its page, where Aim starts the migration in the chat.
2

Review the Agent

After Aim drafts the Agent, review what it did in the settings panel and in the chat:
  • Reasoning: the Agent is Aim’s interpretation of the Workflow, so the instructions and steps won’t map one-to-one. Read Aim’s reasoning and decisions in the chat.
  • Instructions: read the new Agent instructions end to end. Check that filters, date ranges, and prompt wording from the Workflow stayed the same. Fix anything that doesn’t sound right in the instructions editor or by asking Aim.
  • Tools: Aim adds a tool for each integration it can match. If it can’t find a match, it offers workaround options.
  • Inputs and outputs: confirm the inputs are unchanged and the output type (Document, Sheet, HTML, CSV, or PDF) matches what you expect.
3

Run the Agent

Select New run and give the Agent the same inputs you’d give the Workflow. Compare the result with your saved output example. Expect differences in wording and order, because an Agent reasons through the steps instead of following nodes. Ask Aim in the same chat for changes, and run the Agent again until the output is right. Changes apply right away.
4

Add triggers

  1. In the settings panel, select Add next to Run triggers and add a Schedule trigger that matches your Workflow’s schedule, or try another trigger if it suits the task better.
  2. Make sure the switch next to Run triggers is on.
The Agent now runs on its own. When you’re ready, remove the schedule from the Workflow so the task doesn’t run twice.

​
FAQ

No. Migrate one at a time so you can check each result.
Check that the instructions state the same category, asset, date range, and filters as the original nodes. If your Workflow uses fixed calculations or tools that aren’t available to Agents yet, keep it as a Workflow, and add it to an Agent’s instructions if you want the Agent to run it as a step.
No. Migration is one-way, but it keeps your original Workflow. If the migrated Agent doesn’t work for you, keep using the Workflow.