Notifications

Carbon emails admins about migration progress and outcomes — useful when migrations run for hours or overnight and you do not want to watch the console.

Where to configure

Click the Notifications tab in the left navigation, then the Email settings subsection.

SMTP setup

• SMTP server — your outbound mail server hostname.
• Port — typically 587 (STARTTLS) or 25 (internal relay).
• From address — what shows in recipients' inboxes.
• Username / password — if your mail server requires authenticated relay.
• Send test email — confirms the configuration before relying on it.

What can trigger an email

Per migration job (see Migrate a VM), tick which events fire emails:

• Job started — confirms the migration kicked off. Useful for runs scheduled to start overnight.
• Per-VM milestones — when each VM in a batch transitions to "Transferring", "Converting", "Configuring target", "Complete". Off by default for batch jobs (would generate many emails); on by default for single-VM jobs.
• Per-VM failure — leave on permanently. Failed migrations require attention.
• Job summary — one consolidated email when the whole job completes (or fails) with per-VM status.

Recipients are configured per job — different migration projects can notify different teams.

What goes in each email

The email body always includes:

• Job name and ID.
• Per-VM status at time of send.
• Target hypervisor and datastore.
• For failures: the failure reason.

For completion emails, the body also includes a summary of post-migration state (new VM names, datastore consumption, total elapsed time).

See also

• Migrate a VM — where per-job notification preferences are set.
• Post-migration checks — validation after the completion email lands.

Need help? support@smikar.com.