Credential scope
Create or choose a source credential with enough read access for the two imported resource types. Avoid unrelated write or account-administration permissions. Use a temporary credential where the provider supports it.Postmark
Enter at least one of the account or server token fields. An account token is appropriate for account-level domain access. A server token can scope access to one server’s relevant data. Use both only when the source layout requires both access levels.Domain verification after import
Imported metadata does not replace live DNS. Open every migrated domain in Signal, compare the current required records, publish any changes, and run verification. Do not route production traffic until Signal shows the domain as verified.Suppression reconciliation
Compare source and destination counts and review the reasons retained by the import. Keep complaint, bounce, and unsubscribe entries blocked. Resolve duplicates by address and reason rather than deleting the destination entry.Provider cutover
- Finish the import and reconcile results.
- Verify Signal domains.
- Create restricted Signal credentials.
- Run test mode.
- Deliver a controlled real message.
- Move a small traffic slice.
- Compare delivery and suppression behavior.
- Complete the cutover and revoke old credentials.