Before you start
- Export a provider-side backup when available.
- Confirm the credential can read domains and suppressions.
- Remove write permissions the import does not need.
- Review current Signal domain and suppression state for duplicates.
- Decide who will verify imported domains after the job completes.
Start an import
1
Choose the provider
Expand the source provider in Settings → Migration.
2
Enter credentials
Resend, SendGrid, Mailgun, and Brevo use an API key.
Postmark accepts an account token, a server token, or both.
3
Start
Signal validates the request and queues one background job for the active project.
4
Track progress
The job can be queued, in progress, completed, failed, or cancelled.
Open detail for per-resource processed, imported, skipped, and failed counts.
5
Verify the result
Review imported suppressions and run current Signal DNS verification for each sending domain before sending.
Credential handling
Provider secrets are sent in request headers to start the import and are not stored as project configuration. The dashboard clears the entered values after a successful start. Revoke temporary provider credentials after the job no longer needs them.Job behavior
Only one import can run for a project at a time. The import continues in the background, so you can dismiss the progress view and keep working. Repeated source records can be skipped as already imported or duplicate. Plan limits and unmappable provider data can also produce skips or failures.After completion
- Compare imported counts with the provider.
- Review every skipped or failed reason.
- Verify domain DNS under Signal’s current requirements.
- Export and compare suppression state if the migration is sensitive.
- Perform a test-mode request and a controlled real delivery.
- Keep the old provider available until reconciliation is complete.