Business & Agency Services

Domain email setup with a planned migration and handover

Home / Business & Agency Services / Business Email Setup

Business email setup connects your domain, mailboxes, users and devices to the chosen email provider. Discuss a new setup or migration with DeshTech, including existing messages and any systems that send mail using the domain.

Discuss Your Project

01 / Service fit

Where this service fits

A new mailbox setup differs from migrating historical mail. Existing calendars, contacts, archives and shared resources may require separate planning. Changing MX records alone does not migrate data or configure every device.

02 / Scope

What to plan in the scope

Mailboxes and provider

Inventory users, aliases, shared addresses, existing data and required devices. Compare provider capability and subscription requirements before changing DNS records.

Domain and authentication

Identify DNS ownership and configure the records required for the chosen provider. SPF, DKIM and DMARC play complementary roles; website forms and other legitimate senders must be considered too.

Migration and handover

Define what mail/data can be moved, the transfer method, cutover window and user setup. Document administrator ownership, account recovery and support responsibilities.

03 / Decisions

Choose the approach before the tools

Inventory every legitimate sender using the domain, including website forms and external marketing tools. Coordinate DNS changes with existing services and choose a cutover approach users understand. Keep subscription and domain ownership with clearly identified business administrators.

04 / Delivery

Move business email with a mailbox inventory

Identify the domain/DNS owner, existing provider, mailboxes and legitimate senders before changing records. Scope the target provider and transfer objects, test a representative mailbox and prepare a cutover checklist. Validate mail flow and user access before retiring the old service.

Migration objects to include or exclude

Agree separate rows for mailbox messages, folders, calendars, contacts, aliases, shared mailboxes, local archives and device setup. Record source access, transfer method, limitations and acceptance for each. An email-message transfer does not establish that calendar sharing, permissions or local archives moved successfully.

Mail-flow and access handover

Record the approved sending services, DNS changes and checks of SPF, DKIM and DMARC where applicable. Test internal/external send and receive, an agreed website sender and mailbox access without exposing private message content. Record administrator and recovery ownership, renewal information, old-service retention and the support route. Authentication checks cannot guarantee inbox placement.

05 / Budget and responsibilities

What affects the project estimate

Cost depends on mailbox count, data volume, source-provider access, required device setup and migration limitations. Provider subscriptions are recurring charges. Authentication configuration improves identification of legitimate senders but cannot guarantee every email reaches an inbox.

Provider choice, migration coverage, device assistance and retention are agreed after discovery. The Eliy Land project documents business email setup, but does not identify a provider or prove a particular migration technology. Subscriptions, transfer labour and ongoing support should be separately stated.

06 / Get ready

What to bring to the first discussion

Provide mailbox count and sizes, current provider, domain/DNS control, aliases/shared addresses, calendars, contacts, local archives and devices. List website forms, newsletters and other legitimate senders. Discuss retention and recovery needs; do not send mailbox passwords through the public enquiry.

Questions / Answers