Start with the readiness report
Before exporting to Smartlead, review workspace readiness for the mailbox batch. Ready rows should have active or warming status, managed MTA assignment, SMTP metadata, IMAP metadata, credential metadata, and recent smoke-test signals where required.
- Confirm the workspace and provider integration belong to the same operating context.
- Check SMTP host, port, username, encrypted credential, and password hash metadata.
- Check IMAP host, port, and username so mailbox access is not discovered after export.
Export ready rows and preserve failures
The export workflow should continue for ready rows while recording not-ready rows as per-row failures. That lets an operator remediate DNS, SMTP, IMAP, credential, or status problems without turning one bad mailbox into a full export halt.
- Persist readiness failures with a customer-safe failure type.
- Keep raw SMTP passwords, encrypted values, hashes, JWTs, and provider responses out of output.
- Re-run export only after the blocked rows have fresh readiness evidence.
Do not skip seed placement
A Smartlead export proves the account setup path reached the provider. It does not prove Gmail or Outlook inbox placement. First prospect traffic should still wait for launch-gate approval and fresh passing seed-placement evidence.