Email

Email Aliases for Domain Rebrand

Learn about Email Aliases for Domain Rebrand in WaymakerOS.

Mailbox AliasesDomain Rebrand
Last updated: January 23, 2026

Email aliases allow a single mailbox to receive email at multiple addresses across different domains. This is essential for domain migrations, company rebranding, or supporting multiple email identities.

What Are Email Aliases?

An email alias is an additional email address that delivers to an existing mailbox. Unlike email forwarding, the email is stored in the mailbox - not redirected elsewhere.

Example:

  • Primary mailbox: john@newcompany.com
  • Alias: john@oldcompany.com
  • Result: Emails to both addresses arrive in John's single mailbox

When to Use Email Aliases

Domain Migration / Rebrand

When your company changes domains (merger, rebrand, or consolidation):

  1. Set up mailboxes on the new domain (@newcompany.com)
  2. Add aliases from the old domain (@oldcompany.com)
  3. Users receive email at both addresses in one inbox
  4. Gradually transition external contacts to the new domain
  5. Eventually retire the old domain aliases

Multiple Business Identities

When employees need to appear under multiple brands:

  • consultant@agencybrand.com (client-facing)
  • consultant@parentcompany.com (internal)

Simplified Addresses

Add short or memorable aliases:

  • Primary: john.smith@company.com
  • Alias: johns@company.com

Creating Email Aliases

Using the UI (Individual Aliases)

  1. Navigate to WaymakerOne > Email > User Mailboxes
  2. Click the menu (three dots) icon next to a user's mailbox
  3. In the Email Aliases section, enter the alias local part
  4. Select the domain from the dropdown (any verified domain)
  5. Click the + button to add the alias

Using the CLI (Bulk Operations)

The CLI is ideal for bulk alias management during domain migrations.

Preview Alias Creation (Dry Run)

waymaker email aliases bulk-add \
  --domain <new-domain-id> \
  --source-domain <old-domain-id> \
  --dry-run

This shows what aliases would be created without making changes.

Execute Bulk Creation

waymaker email aliases bulk-add \
  --domain <new-domain-id> \
  --source-domain <old-domain-id> \
  --confirm

This creates aliases on the old domain that deliver to mailboxes on the new domain.

List Aliases for a Mailbox

waymaker email aliases list --mailbox <mailbox-id>

Bulk Operations for Domain Rebrand

Migration Workflow

Scenario: Migrating from oldcompany.com to newcompany.com

  1. Get Domain IDs

    waymaker domains list --json
    
  2. Preview the Migration

    waymaker email aliases bulk-add \
      --domain <newcompany-domain-id> \
      --dry-run
    
  3. Execute the Migration

    waymaker email aliases bulk-add \
      --domain <newcompany-domain-id> \
      --source-domain <oldcompany-domain-id> \
      --confirm
    
  4. Verify Aliases Created

    waymaker email aliases list --mailbox <any-mailbox-id>
    
  5. Test Email Delivery

    • Send test email to user@oldcompany.com
    • Verify it arrives in the user@newcompany.com mailbox

Removing Aliases (Domain Retirement)

When you're ready to decommission the old domain:

# Preview removal
waymaker email aliases bulk-remove \
  --domain <old-domain-id> \
  --dry-run

# Execute removal
waymaker email aliases bulk-remove \
  --domain <old-domain-id> \
  --confirm

Warning: After removal, emails to the old addresses will bounce.

Email Aliases vs Email Forwarding

FeatureEmail AliasesEmail Forwarding
DeliverySame mailboxForward to external address
StorageIn the mailboxNo storage
Reply AddressCan reply as aliasN/A (no mailbox)
Use CaseDomain rebrandAdmin addresses
ManagementWaymakerOne > User MailboxesWaymakerOne > Domains

Choose Email Aliases when:

  • Users need to receive email from old domains
  • You're migrating/rebranding domains
  • Users need multiple identities in one inbox

Choose Email Forwarding when:

  • You need administrative addresses (postmaster, abuse)
  • No mailbox should exist on the domain
  • Emails should go to external addresses

CLI Reference

See Email CLI Commands for complete command reference.

Quick Reference

# List aliases for a mailbox
waymaker email aliases list --mailbox <id> [--json]

# Bulk add aliases (preview)
waymaker email aliases bulk-add --domain <id> --dry-run

# Bulk add aliases (execute)
waymaker email aliases bulk-add --domain <id> [--source-domain <id>] --confirm

# Bulk remove aliases (preview)
waymaker email aliases bulk-remove --domain <id> --dry-run

# Bulk remove aliases (execute)
waymaker email aliases bulk-remove --domain <id> --confirm

Best Practices

  1. Always preview first - Use --dry-run before bulk operations
  2. Keep old aliases active - Don't remove until you're sure all contacts have updated
  3. Communicate the change - Notify external contacts of new email addresses
  4. Update email signatures - Ensure users update their signatures to the new domain
  5. Test before going live - Verify email delivery works as expected

Troubleshooting

Alias Not Receiving Email

  1. Verify the alias was created: waymaker email aliases list --mailbox <id>
  2. Check the source domain is still verified
  3. Ensure DNS records for the old domain are still active

"Address Already Exists" Error

The alias address conflicts with:

  • An existing mailbox
  • Another alias
  • A forwarding alias

Check both domains for conflicts.

Bulk Operation Skipping Mailboxes

The bulk add operation only creates aliases for:

  • Active mailboxes on the target domain
  • Mailboxes where the alias doesn't already exist

Check the operation output for "Skipped" entries.