Overview
Before sunset, every scheduled Agent you rely on needs to be rebuilt as a Moby 2 Automation. Moby 2 has a guided Agent-to-Automation migration flow that does most of the work for you. You paste your old Agent's steps, answer a few short follow-up questions, and Moby drafts the Automation and runs a kickoff on the spot. The hardest part is the copy-paste prep.
Before you begin
Moby 2 must be enabled on your store (one-time setup). See How to enable Moby 2 on your store.
You need an account role that can create Automations.
If your Agent delivered to Slack, email, or Google Sheets, have access to re-authorize those integrations, reconnects are common during migration.
⚠ Your old Agent keeps running during migration. You're creating a new Automation alongside it, nothing in your current workflow breaks while you rebuild. The old Agent stops on its own at sunset.
Steps
Open the Agent you want to migrate. Go to Settings → Moby Tools → Agents (Moby 1) and click into the Agent.
Capture the run details from the Customize tab. Open the Agent's Customize tab. Note:
Name
Cadence and run time (e.g., first of the month at 6 a.m., weekdays at 9 a.m.)
Output destination (dashboard artifact, Slack channel, email list, Google Sheet)
Single-store or multi-store
Copy every step of the Agent into one document and label each step by its type. Open each step in the Customize view and paste it into a plain-text or Google Doc. Label each one as you paste, because Moby uses these labels when it maps the Agent:
Text to SQL: a step that queries your data.
Plain Text: a step that formats or summarizes.
Dashboard: a step that references a Triple Whale dashboard.
Preserve the step order. This compiled document is what you'll hand to Moby.
Start the migration flow in Moby. Open the Moby chat bar and send: I want to turn an agent into an automation. Moby replies: "Welcome to the agent migration flow. Please paste the old agent."
Paste the Agent body. Send the full compiled document in one message. If it's long, you can send steps one at a time or upload a text file, Moby waits until everything has arrived before moving on.
Review Moby's migration assessment. Moby tells you what maps cleanly and flags anything it can't handle, a reconnect that's expired, a file it can't find, an unsupported destination. Address each flag as Moby surfaces it.
Answer the follow-up questions, in order. Moby asks only the minimum needed to build the Automation, typically name, cadence and time, destination, scope, and any file dependencies:
Name: what should this Automation be called?
Cadence and time: what schedule should it run on?
Destination: where should the output land? Options include the in-product dashboard artifact (stays inside Triple Whale), plus Slack, email, and Google Sheets.
Scope: single-store or multi-store? (For multi-store, Moby confirms which stores to pull in: you don't drag them from a dropdown the way you did in Agents.)
Wait for Moby's proposal. Moby takes a moment to generate a proposal: scope, output format (HTML artifact by default), analysis logic, timeframe, and cadence.
Click Approve. Approving creates the Automation and immediately runs a kickoff so you can see the output live.
Review the kickoff output, then click Activate. If the output looks right, click Activate to turn on the schedule. If something's off: wrong channel, wrong cadence, wrong scope: tell Moby in the same chat and it updates the Automation in place before you activate.
Verify
The migration worked when:
The new Automation appears under Automations with the cadence you set.
The kickoff landed in your chosen destination (dashboard artifact, Slack channel, email inbox, or Google Sheet).
The Automation is showing as Active, not just created.
Your old Agent is still listed under Settings → Moby Tools → Agents (Moby 1). That's expected. It stops running on its own at sunset.
Variant: scheduled tasks (slash-command items)
Not every item in your Agents tab is a full Agent. Anything with a slash, like /MER reporting, is a scheduled task: a saved prompt with no chained steps. These are simpler to migrate:
In Moby chat, click the ⚡ lightning icon to open the scheduled task list.
Click the ✏️ pencil on the task you want, then copy the prompt.
Grab the cadence and destination from the task's Customize tab (same as an Agent).
Start the same migration flow in Moby (I want to turn an agent into an automation) and paste the prompt when asked. No step-type labelling is needed, scheduled tasks are single-prompt by definition.
If something doesn't work
Slack report isn't arriving → Slack delivery failing on a new Automation
Google Sheet isn't populating → Google Sheets output not writing for an Automation
Integration shows "Not Configured" → Automation integration shows "Not Configured"
Wrong store is running → Automation is running against the wrong store
Output looks different than the Agent's → Automation output differs from the Agent's output
Moby says a file is missing → Moby can't find a file referenced by my Agent
Related questions
How long does migrating one Agent usually take?
Do I have to disable the old Agent after migrating?
What if the kickoff output looks wrong?
Can I migrate multiple Agents in the same Moby chat?
What's the difference between Approve and Activate?
What if my Agent has a step Moby flags as unsupported?
Does migrating an Agent use credits?