Mail gateway migrations: planned vendor-independently

Whether it is the end of a licence, a security incident, consolidation or the move to Microsoft Defender for Office 365: replacing a mail gateway puts the entire mail flow up for review. We support migrations between mail security solutions such as Proofpoint, FortiMail, Barracuda and xorlab, as well as the replacement of bulk mail and SMS gateways, from evaluation to the shutdown of the legacy system.

Proofpoint
FortiMail
Barracuda
xorlab
Bulk Mail Gateways
SMS Gateways

Get in touch →

What a gateway change has to carry over

A mail gateway usually holds more logic than is documented: allow and block lists, exceptions for individual senders, routing per domain, TLS requirements for partners, quarantine processes, disclaimers, journaling and submission by applications. Inline gateways in the MX path and API-based solutions also hook into Microsoft 365 at different points; switching between the two models changes connectors, Enhanced Filtering and the assessment by EOP.

Services

Mail security gateways Proofpoint, FortiMail, Barracuda, Cisco Secure Email, xorlab and others: export the rule set, assess it and map it to the target system instead of carrying legacy configuration over one to one.

Move to Microsoft Defender for Office 365 Remove the upstream gateway and carry its protection features over into EOP and Defender, including policies, quarantine and allow lists.

Bulk mail gateways Sending systems for newsletters, invoices and customer communication: preserve load profile, IP reputation, SPF, DKIM, DMARC and bounce processing during the move.

SMS gateways Mail-to-SMS and SMS sending from applications: switch interfaces, sender IDs and delivery receipts to the new provider.

How an engagement runs

1 Evaluation Measurable criteria and a requirements specification instead of product brochures, when the target system is still open.
2 Rule set analysis Record every rule and exception of the legacy system and decide: carry over, replace or drop.
3 Parallel operation Part of the traffic through the new gateway, comparison of verdicts, delivery and load.
4 Cutover and decommissioning Switch MX and connectors reversibly, then remove the legacy system from DNS, SPF, allow lists and monitoring.

From comparable projects

Energy service provider ≈ 1 m invoices per year Mail hub and bulk mail infrastructure for SAP invoice delivery

2 Oct 2026 · FortiMail CVE-2026-104286: FortiMail Zero-Day Is Being Exploited - Workaround and Compromise Assessment Fortinet reports a critical, actively exploited path traversal vulnerability in FortiMail 7.2 through 8.0 (CVE-2026-104286, CVSS 9.8). A patch is not yet available. The workaround disables IBE or blocks Internet access to the management interface; indicators for assessing compromise are also available. 25 Aug 2026 · SMTP and mail flow Determining a Mail Server’s Load Profile: Bursts, Peak Rates, and Recipient Structure from Message Tracking How many emails per minute does your mail server really process, and how high are the peaks? How to use PowerShell and Exchange Message Tracking to determine the real load profile: rates per minute and hour, burst duration, recipient structure, message sizes, and common analysis mistakes. 4 Aug 2026 · SMTP and Mail Flow Guide for DNS Administrators: MX, SPF, DKIM, DMARC, and Common Pitfalls Anyone managing a zone will usually receive ready-made mail records and only needs to publish them. What regularly goes wrong: the 255-byte limit for DKIM, duplicate SPF records, the lookup limit, MX pointing to a CNAME, automatically appended zone suffixes, and policies nobody enforces anymore.

Planning something similar?

In a first conversation, we'll look at where you stand, the risks and the most sensible next step.