Three service shapes, chosen for the work.
User count alone does not decide the right solution. Collaboration, administration, mobility, migration and operational responsibility matter just as much.
MrMail starts with how the organisation actually works. Each proposal states the included capabilities, access methods, responsibilities and separately scoped services.
Compare the options
From one professional mailbox to a dedicated environment.
Professional mailbox
For a professional or small organisation that needs a properly operated business address without complex administration.
Business Zimbra
For a team using shared calendars, contacts, mobility, collaboration and central administration.
Dedicated solution
For an organisation that needs its own environment, a structured migration or a particular operating model.
Always clarified
Migration method, clients, devices, quotas, capabilities and support are written into the actual quotation.
No unlimited storage, complete feature set, SLA, response time or recovery objective is promised unless it is explicitly agreed.
Decision guide
What is framed before a proposal.
Working pattern
Who needs only an individual mailbox, who plans in shared calendars, and who manages contacts or tasks as a team? These differences determine useful capability.
Shared resources are included where they support an actual workflow.Operating model
The conversation identifies who creates users, assists devices, approves policy and receives the first incident report. A dedicated environment may need different ownership from one mailbox.
Roles and escalation paths belong in the agreed scope.Transition
Existing domains, data, clients and devices affect effort and sequence. Even a small service may require a careful migration.
Source, volume and operating window are assessed before commitment.The right shape comes from work, risk and responsibility—not an invented package name.
Turning a requirement into a concrete solution.
The first conversation gathers more than mailbox count. MrMail examines domains, user groups, shared tools, mobility and which administration should remain internal, creating a solution frame that can be understood.
The quotation separates platform capability from the service actually included. It should show access methods, migration work, expected support and requests that need separate assessment.
If the organisation changes later, expansion is reassessed technically and commercially. The website therefore promises neither automatic scaling nor generic service limits.
The right solution is not the largest one; it is the one with clear capability and clear responsibility.
Practical orientation without invented tiers
| Question | Professional mailbox | Business Zimbra | Dedicated solution |
|---|---|---|---|
| Typical context | Professional or small organisation | Team with shared work | Organisation with specific requirements |
| Collaboration | According to the selected scope | Agreed calendars, contacts and team capabilities | Capabilities and policies designed to fit |
| Administration | Simple, with defined assistance | Central management and roles as needed | Project-specific administration model |
| Migration | Source and volume assessed | Users, sharing and devices inventoried | Pilot, method and cutover planned in detail |
Before choosing
Are there fixed prices?
The site avoids generic prices because users, data, capabilities and migration shape the proposal.
Can we start small and expand?
Yes where the architecture and agreement allow it. The path is assessed before commitment.
Is every Zimbra capability included?
No. Platform capability and the service ordered are deliberately kept distinct.
Choose from the real operating need.
Describe users, clients, mobility, sharing and migration constraints.