Provider credentials
Use a source credential with only the read access required for the imported resources.
The dashboard submits credential values to start the job and clears its input after a successful start.
They are not added as reusable project configuration.
Revoke a temporary source credential after the job no longer requires it.
Job behavior
Only one import can run for a project at a time. The job continues in the background and can bequeued, in_progress, completed, failed, or cancelled.
Progress exposes processed, imported, skipped, and failed counts per resource.
A skipped row can be a duplicate, an already imported record, a plan-bound item, or provider data that cannot be mapped.
Read the job’s actual error samples instead of inventing a cause from the count.
Domains require new verification
Imported domain metadata does not publish or validate current Signal DNS. Open every destination domain, compare the returned records, publish missing or changed values, and run Signal verification. Do not move a production From address until required checks pass.Suppressions require reconciliation
Compare source and destination counts and reasons. Keep bounce, complaint, unsubscribe, and deliberate manual blocks intact. Resolve duplicates by normalized address and reason instead of deleting the destination fence.Cutover sequence
- Export or preserve the source evidence you require.
- Run the import and review every resource result.
- Verify Signal DNS.
- Reconcile suppression counts and samples.
- Create restricted Signal credentials.
- Run test mode.
- Deliver one controlled real message.
- Move a small traffic slice and compare outcomes.
- Complete the cutover and revoke old credentials.