# Move one flow. Keep the momentum.

Bring your communications to Bird in deliberate, testable steps.

## A migration you can inspect.

Move a representative flow first, then expand from the evidence.

- ### Map the existing flow

List senders, credentials, templates, consent records, delivery events, and the application code that depends on them.
- ### Prepare Bird

Configure the workspace and eligible senders. Bring over the content and suppression or consent data your flow needs.
- ### Test the full round trip

Send to controlled recipients. Verify rendering, delivery events, incoming replies, and error handling in your application.
- ### Move traffic deliberately

Shift a limited flow, observe it, and retain a clear rollback path. Expand once the results match your requirements.[Discuss your migration](/demo)

## Start with your channel.

Use the current guide for the part of the migration you are making.

[### Migrate from SendGrid

Map an existing email flow to Bird’s sending and event model.](/docs/guides/email/migrate/sendgrid)[### Migrate from Mailgun

Move the sending application, sender setup, and delivery handling.](/docs/guides/email/migrate/mailgun)[### Migrate from Amazon SES

Plan the switch from sender configuration through delivery events.](/docs/guides/email/migrate/ses)[### Migrate from Resend

Bring your email integration into Bird with a focused migration guide.](/docs/guides/email/migrate/resend)

## Keep building.  Everything connects.

Take the next step with the tools and guides for your project.

[### Documentation

Follow a guide or inspect the API.](/docs)[### Support

Bring your integration question to the team.](/help/support)



## Related resources

- [Getting started with email](/learn/email/getting-started-with-email) (video)
- [Send your first email](/docs/get-started/send-your-first-email) (docs)
- [Build your first integration](/learn/paths/integration) (course)
- [Email](/email-api) (product)

[Get an implementation brief](/learn/workspace?topic=email)