How Much Does Business Email Cost?
A transparent calculation for email on your domain: Mailcore's base plan, additional mailboxes, migration, and related operating costs.
Contents
- Calculating the monthly Mailcore cost
- Why a per-user price is not the full picture
- Costs that arise at launch
- Domain and DNS management
- Historical-mail migration
- Device setup and training
- Backups
- Example calculations for different teams
- A small company with five addresses
- A team with eight mailboxes
- Ten employees with an archive
- How to avoid overpaying without losing what matters
- Questions to answer before payment
- The final formula
- Sources
Business email cost depends on more than employee count. Domains and mailboxes, storage, historical-mail migration, DNS configuration, external senders, and operating requirements all affect the total. A low-cost plan can become impractical if it excludes work the company considers critical.
Mailcore's pilot plan costs UZS 59,000 per month for one domain and five 1 GB mailboxes. Each additional 1 GB mailbox costs UZS 8,000 per month. Migration is quoted separately after reviewing the source system and data volume, and the total is agreed before any DNS change.
Calculating the monthly Mailcore cost
The base package covers one domain and up to five mailboxes. Beyond that, add UZS 8,000 to the base price for each mailbox.
| Mailboxes | Calculation | Monthly cost |
|---|---|---|
| 1–5 | base package | UZS 59,000 |
| 6 | 59,000 + 1 × 8,000 | UZS 67,000 |
| 8 | 59,000 + 3 × 8,000 | UZS 83,000 |
| 10 | 59,000 + 5 × 8,000 | UZS 99,000 |
| 15 | 59,000 + 10 × 8,000 | UZS 139,000 |
This calculation applies to the stated configuration: one domain and 1 GB mailboxes. Historical migration is based on the actual archive. Before payment, Mailcore confirms the configuration and complete scope for the company's scenario.
Service addresses count too. If info@company.uz, sales@company.uz, and billing@company.uz are separate mailboxes with their own passwords and storage, they occupy package places. Aliases and groups work differently, but availability must be agreed rather than assumed.
Why a per-user price is not the full picture
Two offers with the same mailbox price may solve different problems. One leaves domain setup to the customer; another includes specialist validation. Archive migration may be included, charged by volume, or unavailable.
Compare the complete scope and boundaries:
- included domains and mailboxes;
- storage per mailbox;
- webmail, IMAP, and SMTP access;
- who prepares and validates MX, SPF, DKIM, and DMARC;
- support for CRM, website, and other senders;
- historical correspondence migration;
- tested backup and recovery arrangements;
- features confirmed for the selected configuration;
- the change-approval and error-resolution process.
Configured Mailcore mailboxes include webmail, IMAP, and SMTP. A specialist prepares and checks MX, SPF, DKIM, and DMARC, then runs control correspondence with external addresses. See SPF, DKIM, and DMARC for the role of these settings.
Costs that arise at launch
Domain and DNS management
If the company has no domain, registration and renewal are paid separately to a registrar. For a domain already hosting a website, email-record changes should not disrupt the web service, but they do require DNS access and a careful plan.
Production MX remains unchanged until approval and testing. Mailcore first confirms mailboxes and senders, prepares records, and works through checks with the client's responsible person. A premature MX change can route new mail incorrectly. See how to connect email to a domain.
Historical-mail migration
MX affects new incoming messages; it does not move old folders. Those are copied separately, commonly over IMAP. Cost depends on mailbox count, occupied storage, source-server availability, connection speed, and folder structure.
After a short inventory, Mailcore prices migration based on the actual volume, so the client does not pay for unnecessary work. Moving several small mailboxes is a different project from a multi-year, multi-gigabyte archive. Use the business email migration checklist before assessment.
Device setup and training
Once the server is ready, employees still need to sign in to webmail or configure a client. A small team may need only instructions and a control test; many devices may require internal administrator time. IMAP and SMTP explains incoming and outgoing access.
Backups
Before production launch, Mailcore agrees backup requirements, isolates copies from primary storage, and verifies recovery with a control test. Production MX is not switched until those conditions are met. The data scope and retention period are defined per connection; see our email backup guide.
Example calculations for different teams
A small company with five addresses
Suppose the company needs mailboxes for its director, accountant, sales, support, and a general contact. All five fit the base package at UZS 59,000 per month. If there is no old correspondence to move, migration may add no separate cost, subject to confirmation.
A team with eight mailboxes
Eight mailboxes require three additional places: 59,000 + 3 × 8,000 = UZS 83,000 per month. If some addresses can be aliases rather than separate mailboxes, discuss the configuration first: an alias has neither separate sign-in nor independent storage.
Ten employees with an archive
Ten mailboxes cost UZS 99,000 per month under the current formula. Migration is added after assessment. The quote needs mailbox sizes, folder counts, and reliable IMAP access to the old service. Keep the old environment until checks are complete.
These examples show the subscription. After a brief inventory, Mailcore supplies an exact recurring and one-time calculation for the company.
How to avoid overpaying without losing what matters
Distinguish people from roles. One employee may need a primary address plus several aliases, not several full mailboxes. Conversely, one shared password for five people looks cheaper but creates accountability and access-removal problems.
The 1 GB quota is designed for current correspondence. If an existing mailbox is larger, agree historical migration and storage separately instead of forcing years of data into a smaller mailbox.
Finally, identify automated senders—website, CRM, invoices, monitoring, and contact forms. Their configuration affects SPF, DKIM, and domain reputation. Adding a source after launch without review can damage delivery or create authentication failures.
Questions to answer before payment
Record:
- The exact number and quota of mailboxes.
- The final monthly total.
- Confirmed features and connection conditions.
- Required DNS records and who will change them.
- External sending systems.
- Historical-mail volume and migration cost.
- Backup scope and restore-test result.
- The test plan before and after switching MX.
This list protects both parties from different interpretations. A price becomes meaningful only together with a configuration and defined service boundaries.
The final formula
Mailcore's monthly calculation is simple: UZS 59,000 for one domain and the first five mailboxes, plus UZS 8,000 for every additional mailbox. Each mailbox has 1 GB; migration is quoted separately based on the archive.
If these parameters fit, send Mailcore the domain, mailbox count, and estimated size of old mail. Addresses, DNS, migration, and the test plan can be agreed without immediately changing MX. Start with what business email is if you need an overview.
Get a calculation for your team
Sources
Get a setup plan and exact estimate
Send us your domain, number of mailboxes and approximate archive size. We will review the current setup and agree on a safe migration before any DNS changes.