One domain, two email systems — routed correctly.

Yes. We review the current service, agree what needs to move and plan the change to reduce interruption. The migration scope is confirmed in writing.

This storefront is quote-led because no approved local catalogue is published for this service. We will not invent a converted price; you receive the actual scope and price in writing.

TK WebHosts provides the agreed technical support. Your written proposal explains what is included, what your team controls and how to request help.

Split email delivery routes incoming messages for a single domain to two different email systems based on the recipient. Mail arrives at a primary server first; recipients who live on the second platform are passed straight through to it.

Email routing is the umbrella: rules that decide where a message goes. Split delivery sends each recipient to exactly one of two systems; dual delivery copies messages to both systems at once, which is common during migrations and testing.

Yes — that is the classic split delivery case. Sales can live in Gmail while operations stays in Outlook, all on the same addresses at your domain.

Done carelessly, it can — a second hop can hard-bounce mail from strict-SPF senders. We design the routing so authentication survives both paths, and we verify it with real senders before handover.

No. Migrations are one use, but plenty of businesses run it permanently — to keep premium licences for a few users, to give departments different platforms, or to meet retention rules for one team only.

Not in a correct setup. The primary server has an explicit rule for every recipient, unknown addresses are rejected predictably, and we test both paths before anything goes live.

It is scoped and quoted in writing — the design depends on your platforms and mailbox count. In most cost-optimization setups the routing pays for itself by reducing per-seat licence spend.