Migrating from Agents to AI by Zapier automatically converts your agent into a Zap with a single AI by Zapier step.
Review the following practices after every migration to confirm your Zap behaves the same way your agent did.
Confirm your knowledge source type is supported
Agents and AI by Zapier do not support the exact same knowledge sources. Before you rely on a migrated Zap, check the sources not yet supported in AI by Zapier. If your agent used one of these, contact your account rep before you turn off the original agent.
Confirm all knowledge source pages loaded correctly
Spot-check pages you have not recently updated and run a few test queries against them to confirm AI by Zapier can still find them. Large or infrequently synced knowledge sources can have pages that silently fail to resolve.
If a source will not fully sync, consider splitting it into smaller, more focused sources instead of one large one. Each AI by Zapier step allows a maximum of 20 knowledge sources, so confirm your split stays within that limit before you rely on it.
Verify tool calls retrieve the same assets your agent found
Use the preview panel to run real queries against your migrated Zap and confirm it can find and return the same pages or records your agent could. Confirming the step runs without erroring is not enough. Compare the actual results to what your agent returned for the same query before you turn off the original agent.
Check source permissions and connection scope
Confirm your app connections have access to every page or section your migrated Zap needs to query. If a query does not return the results you expect, check the connected account's access before you assume the page is missing. See known knowledge source behaviors for why permission gaps can look like a data problem.
Raise the task limit to match your resource count
The default task limit can be too low for workflows that query many resources. If your Zap hits the limit partway through a run, it can silently cut off results without an obvious error. Use the task limit slider in your AI by Zapier step to raise the limit so it matches the number of resources your workflow actually queries. Learn more about task limits for AI by Zapier steps.
Review and trim unused output fields
Migrating automatically populates output fields from your prompt headers, but not every field it creates is used by a downstream step. Review your output fields and remove any fields a later step does not consume. Unused fields can add latency to the response.
Use the run log to review step-level detail
If a migrated Zap does not behave as expected, open the run in Zap history and review the AI by Zapier step. The activity log shows step-level detail, including which specific knowledge source or page was searched, which helps you confirm exactly where a run succeeded or failed.
Next steps
Working through this checklist after each migration helps you catch gaps before you turn off your original agent.
- Add tools to your AI by Zapier step: Configure tools, model tiers, and per-tool approvals for your migrated Zap.
- Use AI by Zapier to analyze and return data: Get familiar with the AI by Zapier step your migrated agent now runs on.
- AI by Zapier model tier pricing: Understand how task usage is calculated.
- Contact your account rep (Enterprise customers) or Zapier support if a migrated Zap still does not match your agent's behavior after working through this checklist.