Short answer
Prioritize the Agents your team depends on most, rebuild those first, test them, then work down the list. If you're stuck on a specific Agent, open a support chat in the Triple Whale help widget. Support is prioritizing migration help throughout the migration window.
Context
Any Agent not migrated before sunset stops running at sunset, the workflow goes dark until you rebuild it. Back up each Agent's prompt into a local document before sunset so you have an offline reference to rebuild from.
Some cases need a workaround rather than a direct migration. Open a support chat before sunset if any of these apply:
Pass/fail branching logic: Automations today run a single prompt on a schedule, so branched flows need to be restructured. See Agents vs. Automations: what's different? for the current gaps, and Agent migration troubleshooting for what to check first.
File-dependent Agents: Agents that read from or write to attached files don't yet have a direct Automations equivalent.
Action Agents: Standard Automations don't execute changes in ad platforms today, they surface insights and reports. If you're using an action Agent (one that updates ad budgets, changes bids, or pauses campaigns), open a support chat before sunset so we can scope the right path for you.
See also