Email setup is more than an MX record
MX records route incoming mail; they do not configure every outgoing sender or move an old mailbox. A safe setup accounts for user accounts, stored messages, forms and invoicing services. CyberFixCrew coordinates these dependencies with the business owner. Subscription licenses remain separate, and authentication does not guarantee inbox placement or recover inaccessible mail.
Map mailboxes and every sender
Migration includes users, aliases, shared mailboxes, archives, devices and automated senders. An MX change controls incoming routing; it does not move historical mail or configure website notifications. Keep the old service until validation is complete.
- Inventory accounts and both providers.
- Confirm licences and recovery ownership.
- Prepare mailboxes and test senders before cutover.
- Check incoming/outgoing mail, clients and archive coverage.
Mailbox and sender acceptance checks
Scope depends on mailbox count, history size, clients and permissions. Record archive exceptions and recovery ownership. Subscriptions are client-owned third-party costs. Setup does not imply a certified partnership or guaranteed inbox placement.
| Item | Handover evidence | Dependency |
|---|---|---|
| Mailbox | Send/receive tests and timestamps | History size and export capability |
| Website | Headers and destination receipt | SMTP/API configuration |
| Shared account | Authorized users and tested access | Provider features and licences |
Example: staff email works but the website sender fails
Staff mail works after migration but a form fails because it still uses old SMTP credentials. Test the form independently before closing the task. This is an illustrative scenario, not a customer case or a promised result.