Who this is for
Any Triple Whale customer who built Agents (scheduled AI jobs) in Moby 1 and needs to rebuild them as Automations in Moby 2 before the sunset. This is the self-serve path: you don't need a CSM to walk through this with you, though support is available if you hit a blocker.
What you'll have when you're done
Moby 2 enabled on your store.
Every Agent your team depends on rebuilt as an active Automation.
A kickoff run completed for each new Automation so you've seen the output.
Your old Agents left alone, they'll stop on their own at sunset.
Prerequisites
Access to re-authorize any Slack, email, or Google Sheets destinations your Agents delivered to.
Usually 15-30 minutes per Agent, plus time to validate each kickoff output.
💡 Tip. Block the migration work across two sittings, one for enablement + inventory, one for the rebuilds. Trying to do everything in a single afternoon is where teams get stuck.
Step 1. Request Moby 2 enablement
Before anything else, Moby 2 has to be turned on for your store. Enablement is currently handled by Triple Whale Support, open a chat from the help widget and request Moby 2 for your store. Support will confirm in-chat once it's flipped on. The switch is immediate and applies to every user on the store, so give your team a heads-up first.
Once enabled, Moby 2 Threads become the default experience, and your legacy Agents move to Settings → Moby Tools → Agents (Moby 1).
→ Full walkthrough: How to enable Moby 2 on your store.
Checkpoint
The left navigation shows Automations, and Settings → Moby Tools → Agents (Moby 1) lists every Agent you'd previously built.
Step 2. Inventory your Agents
Open Settings → Moby Tools → Agents (Moby 1) and make a list. For each Agent, write down:
Name
Cadence and run time (from the Customize tab)
Destination (dashboard artifact, Slack channel, email recipients, Google Sheet)
Whether it's a full Agent or a scheduled task (anything with a slash like /MER reporting is a scheduled task, simpler to migrate)
Priority (which Agents does your team actually rely on?)
This list is your migration checklist. If your team has dozens of Agents, rank them, you'll rebuild the top-priority ones first.
Checkpoint
You have a written list of every Agent, with enough detail to hand to Moby during migration.
Step 3. Migrate one Agent end-to-end (the pilot)
Pick one mid-priority Agent (not your single most critical one, not the trivial one, something in the middle) and run the full migration flow once. This teaches you the rhythm before you scale.
In the Customize tab of the chosen Agent, copy every step into a single document and label each by type (Text to SQL, Plain Text, Dashboard).
In Moby chat, send I want to turn an agent into an automation.
Paste the compiled document when Moby asks.
Answer a few short follow-up questions (name, cadence and time, destination, scope, and any file dependencies).
Click Approve, wait for the kickoff to run, then click Activate if the output looks right.
→ Full walkthrough: How to convert your Agents to Moby 2 Automations.
Checkpoint
One Automation is live under the Automations list with status Active, and the kickoff output landed in your chosen destination.
Step 4. Work through the rest of your list
Repeat Step 3 for each remaining Agent in priority order. A few things to watch for as you scale up:
Integration reconnects are normal. Slack and Google Sheets connections don't transfer. Expect to re-authorize each one. If the reconnect fails, see the Troubleshooting hub.
Action agents need a workaround. If an Agent executed bid changes, budget updates, or campaign pauses, it can't migrate directly, open a support chat before sunset to scope an interim workflow.
Scheduled tasks are faster. Anything with a slash is a one-prompt scheduled task, click the ⚡ lightning icon in the Moby chat bar of the Agent's Insights tab, copy, and paste into the migration flow. No step labels needed.
Leave the old Agents in place. You don't need to disable or delete them. They stop on their own at sunset.
Checkpoint
Every Agent your team depends on is either (a) rebuilt as an active Automation or (b) on a written list with a known workaround.
What's next
Once your critical Automations have been running for a week, review Moby 2 Best Practices & Common Use Cases to tune prompts and consolidate overlapping reports.
If you want to explore new scheduled jobs that didn't exist as Agents, the same migration chat flow works, just describe what you want in plain language and skip the paste step.
If you get stuck
For specific error symptoms, jump into the Troubleshooting hub: Agent to Automation migration isn't working, troubleshooting.
For conceptual questions, browse the FAQ hub: Agent sunset, FAQ.
For anything else, open a support chat from the help widget in Triple Whale. Support is prioritizing Agent migration questions throughout the migration window.
Related questions
How long should I budget for migrating one Agent?
Can I migrate more than one Agent in the same Moby chat?
What if I find an Agent I forgot about after sunset?
Do I need to do anything to turn off the old Agents?
What if my Agent is more complicated than the migration flow expects?
Should I tell my team before I migrate, or after?
Where does my migrated Automation show up?