Plan an email migration with your agent
Use the Loops API skill and migration guide to inventory existing sends, map contacts, events, templates, and transactional email to Loops, then work through the codebase file by file. The dedicated /migrate skill is still on the roadmap.
Inventory before you switch
List every provider, send call, template, Workflow, webhook, sending domain, suppression rule, and consent source. Mark the contacts, events, and transactional sends that must move, along with the account and DNS work that still happens in the dashboard. Keep the old provider active until the replacement path is verified.
Choose the matching guide
Use the guide for your current provider to map contacts, templates, sends, and cutover steps to Loops.
Keep the cutover reversible
Make code changes on a branch. Test contact updates, events, and transactional sends with a small audience, then move traffic in one controlled step. Remove the old package and credentials only after Loops is handling the expected sends.