Business email and collaboration setup should leave your organization in control of its domain, accounts and recovery access. Zoha can scope setup or migration around users, shared resources, existing messages and practical acceptance checks. Agree the platform, subscription responsibilities and handover before changing delivery settings or moving business information.
Updated
On this page
Establish who controls the domain and accounts
Begin with the domain registrar, current email provider and person who can approve administrative changes. An organization can struggle to move email when a former supplier holds the only recovery details. Record ownership and arrange appropriate administrative access before making changes.
Choose the platform and plan around the business requirements, including users, shared mailboxes or groups, file collaboration and account security. Subscription features and terms vary. We can discuss setup and migration work without implying a vendor partnership, resale arrangement or that every feature is included in every plan.
Inventory what the business needs to keep
| Item | Information to collect | Acceptance check |
|---|---|---|
| Users | Addresses, owners and active accounts | Each intended user can access the correct account. |
| Shared addresses | Purpose, members and delivery behavior | Messages reach the responsible team. |
| Existing mail | Accounts, folders and retention decisions | Agreed historical messages are accessible after migration. |
| Calendars and files | Owners, sharing and migration scope | Required resources and permissions remain usable. |
| Domain settings | Registrar access and current records | Authorized changes preserve the intended services. |
| Recovery | Administrator and user recovery arrangements | The business can regain access through the agreed process. |
Avoid assuming that mail migration also includes calendars, contacts, archives and shared files. List each required item and how it will be checked. Personal accounts and business-owned resources may need different handling.
Plan the change before redirecting mail
Domain verification and mail-routing changes are related but different steps. Google's official domain guide explains verification of domain control. Microsoft's domain setup guide emphasizes preparing users and mailboxes before changing mail delivery to Microsoft 365. Follow the current instructions for the actual platform and domain provider.
For a hypothetical small office, the migration plan might prepare the new accounts, move an agreed test mailbox and verify sending, receiving and access before the final change. Record the cutover contact, user communication and the route for addressing problems. Do not promise uninterrupted delivery without examining the existing system and migration method.
Set useful permissions and staff routines
- Separate ordinary use from administration where the platform supports it.
- Apply the agreed account-security and recovery settings.
- Review external sharing, group membership and shared-resource ownership.
- Test sending and receiving with representative internal and external addresses.
- Check the authentication records required for the chosen email design.
- Give staff clear instructions for sign-in, shared resources and reporting access problems.
A platform account is not a complete operating process. Someone must create and remove users, update group membership and manage recovery details. Keep those tasks with named owners, especially when staff or suppliers leave.
Leave the business with an understandable record
The handover should identify subscriptions, billing responsibility, domain ownership, administrative roles, shared addresses and the changes made. Include unresolved migration items and the agreed treatment of old accounts or retained copies. Remove temporary delivery access when it is no longer needed.
We can scope a new setup, an existing-account review or a controlled migration. Ongoing administration and support should be explicit in the arrangement. The result should be communication your staff can use and your organization can control, rather than a set of accounts dependent on an undocumented supplier login.