Google Workspace Split Delivery and Dual Delivery: When and Why You'd Use It

Most email migrations to Google Workspace are a clean cutover: change the MX records, everything routes to Workspace from that point forward. But a specific set of situations calls for something more gradual — routing mail to two mail systems at once, or splitting delivery by mailbox, for a defined transition period. Google Workspace supports this through split delivery and dual delivery configurations, and it's worth understanding when you'd actually reach for either, because using them when you don't need to just adds unnecessary complexity.

What Dual Delivery Actually Does

Dual delivery routes a copy of incoming mail to two separate systems simultaneously — for example, to both your old mail server and Google Workspace at the same time, for every mailbox, or for a defined subset. This is typically set up as a temporary measure during a migration window, so both systems keep receiving mail while you verify Workspace is working correctly before fully retiring the old server. It's a safety net, not a permanent architecture: nobody should be running dual delivery indefinitely, since it means maintaining two mail systems permanently instead of actually completing the migration.

What Split Delivery Actually Does

Split delivery routes different mailboxes to different systems based on rules — some addresses go to Google Workspace, others continue routing to the old mail server, based on the recipient. This is the setup for a genuinely phased migration: move the sales and marketing team to Workspace first, verify everything works cleanly for a week or two, then migrate finance and operations in a second wave, with mail correctly routed to whichever system each group is currently on throughout the transition.

When a Nepali Business Would Actually Need This

• A phased department-by-department migration for a larger organization that wants to avoid moving the entire company at once and dealing with every possible issue simultaneously.
• A business with automated systems tied to specific mailboxes on the old server — an order confirmation system, a support ticket integration — that needs more time to be reconfigured for the new mail system before that particular mailbox can fully move.
• Risk-averse migrations for businesses where email downtime has serious consequences (a business handling time-sensitive client communication, for instance), where running both systems briefly in parallel provides real insurance during the switch.
• Testing before full commitment, where a business wants to verify Workspace performs well with real mail volume before fully retiring the old server, rather than trusting it blind on cutover day.

When You Don't Need Either

For most small Nepali businesses — a team of five to thirty people moving from cPanel webmail or a free Gmail workaround to Workspace — a straightforward, well-planned MX cutover is simpler, faster, and involves less ongoing complexity than dual or split delivery. Those configurations solve a specific problem (phased migration for a larger or more operationally complex organization) and introduce genuine complexity of their own: mail routing rules that need to be correctly maintained and eventually unwound, and two systems that both need monitoring during the transition period. Don't reach for split or dual delivery just because it sounds like the more careful option; it's the right tool for a specific, larger-scale migration need, not a default best practice.

How the Technical Setup Works, Briefly

Both configurations are implemented through routing rules in the Google Workspace admin console combined with corresponding mail server configuration on the old system, rather than through DNS MX record changes alone. This is meaningfully more involved than a standard migration and genuinely benefits from being handled by someone who has configured it before — a misconfigured split delivery setup can cause mail to silently fail to route to either system for the affected addresses, which is a worse outcome than either a clean cutover or no migration at all.

A Practical Example

A mid-sized trading company with roughly 40 staff across finance, operations, and sales wanted to migrate to Google Workspace but had automated order-processing emails tied tightly to their existing mail server that operations wasn't ready to touch yet. We set up split delivery so sales and management moved to Workspace immediately, while operations mailboxes stayed on the old server for six additional weeks until their order system was reconfigured, then completed the final migration for that group without any mail being lost or delayed for either side during the transition.

Deciding Which Approach Fits Your Migration

If your business is small, straightforward, and not tied to legacy systems on specific mailboxes, a standard clean cutover to Google Workspace is almost certainly the right call — simpler, faster, and with less that can go wrong. If you have a genuine phased-migration need or systems tied to specific addresses that need more time, split or dual delivery is the correct tool, set up carefully rather than left running longer than necessary. WebsNP evaluates this as part of every Workspace migration we handle and will tell you honestly which approach your specific setup actually needs — message us on WhatsApp with a description of your current mail setup and we'll recommend the right migration path.