Email Templates Migration

Supabase lets you customize the emails sent to users for actions like signup confirmation, password resets, and team invitations. The Email Templates component makes sure those customizations carry over to your destination instance.

What Gets Migrated

When you select the Email Templates component, Stack2X copies:

• Confirmation email -- The template sent when a new user signs up and needs to verify their email address.
• Invite email -- The template sent when an existing user invites someone to the application.
• Magic link email -- The template used for passwordless login via email link.
• Password reset email -- The template sent when a user requests to change their password.
• Email change email -- The template sent when a user updates their email address.
• Template content -- Both the subject line and HTML body of each template are included, along with any template variables you have used.

Plan Availability

Email Templates migration is available on the Pro plan and above. This component is not included on the Free or Starter tiers.

Tips and Considerations

• Check your links. Email templates often contain hardcoded URLs pointing to your application. If your destination project has a different domain or URL, update the links inside your templates after migration. Stack2X will highlight any URLs that reference the source project.
• Template variables. Supabase templates use variables like {{ .ConfirmationURL }} and {{ .SiteURL }}. These variables resolve automatically on the destination instance, so you usually do not need to change them.
• Preview after migration. Visit the Auth Email Templates section of your destination project's dashboard to preview each template and confirm the formatting looks correct.
• Pair with Auth Config. If you have customized both your email templates and your auth settings, include both components in the same migration to keep everything in sync.
• Default templates. If you have not customized a particular template on the source, Stack2X will skip it and the destination will use Supabase's default template for that email type.