Open-Xchange or grommunio: which one fits your team
Choose OX App Suite if you are a hosting provider, telco or ISP that needs a white-label email and groupware platform to resell under your own brand and you can operate Kubernetes. Choose grommunio if your IT team is replacing on-premises Exchange, keeps Outlook and mobile clients in place, and wants an appliance-style Exchange drop-in that runs on your own servers. The decision turns on four questions: who operates the platform, how many users sit behind each tenant, which Outlook and mobile clients must keep working, and whether your team can run Kubernetes with Istio and a distributed file system for OX App Suite v8.
OX App Suite v8 is delivered as Helm charts (Helm 3.17.0 or newer) and expects Istio, with a basic ingress-nginx option where Istio cannot be used, plus MariaDB, Redis 7.4.x and NFS or object storage for persistent data. That is a platform engineering commitment. grommunio, by contrast, ships as an openSUSE-based ISO or OVA with a setup wizard, and its Exchange migration script assumes you already run LDAP or Active Directory shared with Exchange. Confirm which Outlook connection types your users need (MAPI/HTTP, EWS, ActiveSync) and test them against your exact client versions before you commit.
On licensing, grommunio publishes per-user prices but sells licenses only through certified partners, so your real cost depends on the partner quote. OX App Suite terms are set in your license agreement, and the Operations Guide notes that some modules may carry custom packaging or separate fees. Ask Open-Xchange and any grommunio partner for the full list of modules, support tier and per-tenant or per-user basis in writing, and compare those quotes against the same scope. DeployOpen plans, implements and hardens either platform inside your infrastructure under a fixed scope agreed in writing before work starts.
Which platform fits which scenario
This table maps common buying situations to the platform that tends to fit them better, and states the condition under which each choice holds. Read each row against your own identity setup, Outlook footprint, Kubernetes capacity and contract needs before deciding.
| Scenario | Better fit | Why and the condition that makes it hold |
|---|---|---|
| A hosting provider selling white-label mail to its customers | Open-Xchange | OX App Suite is positioned as a white-label platform for hosting providers, telcos and ISPs, with on-premises, public cloud or managed OX Cloud options. This holds if you need to rebrand the suite for your own customers and resell it under your name. |
| Replacing on-premises Exchange with the Outlook clients users already run | grommunio | grommunio states it keeps existing Outlook clients working through MAPI/HTTP, EWS and Exchange ActiveSync support. This holds if Outlook desktop continuity is the main requirement and you want to avoid retraining users. |
| An existing Active Directory or LDAP estate that needs a drop-in replacement | grommunio | grommunio describes itself as a native Exchange drop-in and is compatible with LDAP and Active Directory. Its Exchange migration script also requires the same directory as Exchange, so this fit assumes your directory is already in place. |
| A team without Kubernetes skills | grommunio | OX App Suite v8 is designed for a Kubernetes cluster, delivered as Helm charts, and requires Istio or ingress-nginx. grommunio ships as an openSUSE appliance (ISO or OVA) with a setup wizard, plus manual and container options. This holds if you lack container platform staff. |
| A team that needs a vendor under contract for the suite | Open-Xchange | Open-Xchange sells support tiers for its suite and publishes a support commitment with defined release windows. grommunio's paid licenses are sold only through certified partners, so confirm partner support scope and response terms in writing for either option. |
| A team that must move off Exchange in stages | Open-Xchange | This is a judgment call that depends on your architecture. grommunio's documented script moves mailboxes from PST exports with logged, resumable runs, which suits a bulk cutover. OX App Suite suits a staged rollout if your team can run its Kubernetes stack, so confirm coexistence and migration tooling with each vendor for your Exchange version. |
How each platform is built and what that means for operations
Open-Xchange and grommunio start from different assumptions about where the suite runs and who operates it. One is a Kubernetes-delivered platform with a set of required data and service components, the other is an Exchange-compatible server that ships as an appliance. The cards below set out each component, the operational consequence and the skill your team needs before you commit.
OX App Suite v8 on Kubernetes
OX App Suite v8 is designed to run on a Kubernetes cluster and is delivered as Helm charts that reference container images, with Helm 3.17.0 or newer required. The operational consequence is that your platform team owns a cluster lifecycle, chart upgrades and image management alongside the mail service itself. Check whether your organization already runs Kubernetes at the scale and support level this implies, and confirm which Kubernetes versions your chosen release supports.
Istio or ingress-nginx routing
OX App Suite v8 requires Istio, supporting the latest Istio release plus two prior versions, and offers a basic ingress-nginx option where Istio cannot be used. Choosing Istio gives you the mesh the product is tested against, but adds a second control plane your team must upgrade on its own schedule. Choosing ingress-nginx simplifies the stack, yet you should confirm with Open-Xchange which features and supported configurations apply under that option before you commit.
Redis 7.4.x for cache and sessions
OX App Suite v8 uses Redis 7.4.x for caching and session storage, deployed by default through the littlered operator, with unmanaged or custom Redis configurations also possible. The consequence is that session availability depends on how Redis is run, so an operator-managed deployment shifts day-two work to the operator while a custom deployment leaves failover and version tracking with your team. Confirm the Redis topology your support contract covers.
MariaDB with Galera support
OX App Suite v8 uses MariaDB with the InnoDB storage engine as its primary data store, with supported versions 10.6.x, 10.11.x, 11.4.x and 11.8.x, and Galera Cluster is supported. Running a multi-node Galera cluster adds quorum management, state transfer and backup coordination that a single database node does not need. Ask for the database sizing and backup approach in a written scope, and confirm your DBA skills match the chosen version line.
Distributed file system for persistent data
OX Drive files and PIM attachments must sit on a distributed file system, which is NFS for small to mid-size deployments or object storage such as AWS S3, Ceph RadosGW or Scality RING for larger ones. Storage choice decides backup, restore and capacity planning more than any application setting. Plan the storage tier before the cluster, and confirm which option matches your expected mailbox and file volume.
grommunio appliance from ISO or OVA
grommunio ships as an appliance built on openSUSE, delivered as ISO or OVA images with a setup wizard, and it also documents manual and container installation. The appliance path reduces the number of decisions at install time, but your team still needs to own OS patching, backups and the update path of the appliance. Check how the vendor handles appliance updates in your environment before you assume the wizard covers day-two work.
Gromox groupware and protocol support
Gromox is the AGPL-3.0 groupware server behind grommunio and implements RPC/HTTP, MAPI/HTTP, Exchange Web Services, IMAP, POP3 and an SMTP local delivery agent, and it can scale out across multiple hosts. For Outlook users the practical question is which client protocols your users depend on, so test each one against your Outlook versions. Scale-out is a capability to verify with a design review, not a default you can assume.
Capability, licensing and support compared
This table compares OX App Suite and grommunio on licensing, Outlook protocol support, directory integration, deployment shape, release support and sales channel. Where the researched facts do not confirm a capability, the cell says what to confirm before you decide.
| Capability | Open-Xchange OX App Suite | grommunio |
|---|---|---|
| License and source availability | AGPL-3.0 mirrors published for appsuite-frontend and appsuite-middleware; certain modules may carry custom packaging or separate fees set in the license agreement | Gromox, the groupware server, is AGPL-3.0; confirm the license of each component (chat, meet, files and office are forks of upstream projects) |
| Outlook protocol support | Confirm which Outlook connection types (MAPI/HTTP, EWS, ActiveSync) your OX App Suite version and Outlook clients support before committing | MAPI/HTTP, EWS, RPC/HTTP and Exchange ActiveSync through Gromox and grommunio-sync; confirm Outlook version coverage with the vendor |
| LDAP and Active Directory compatibility | OpenID Connect and SAML login options are documented; confirm directory sync and Active Directory fit for your setup | Compatible with LDAP and Active Directory; the Exchange migration script requires the same directory as Exchange |
| Deployment shape | Kubernetes with Helm 3.17.0 or newer, Istio or ingress-nginx, Redis 7.4.x, MariaDB and NFS or object storage for file data | Appliance built on openSUSE (ISO or OVA with setup wizard), plus documented manual and container installation |
| Support release windows | Standard releases supported for 12 weeks; LTS releases supported until the next LTS plus six months; v8.47 (FCS 2026-03-18) is the current LTS | Confirm support windows and upgrade cadence with grommunio; manufacturer support is tied to paid packages |
| Sales channel | Sold directly by Open-Xchange and positioned for hosting providers, telcos and ISPs; confirm reseller or partner terms with them | Licenses sold only through certified partners; Community package covers up to 5 users without manufacturer support |
| Scale-out | Designed for Kubernetes clusters with distributed storage; confirm sizing for your user count with Open-Xchange | Gromox can scale out across multiple hosts; confirm the topology and database layout for your user count |
What is licensed, paid and set in the contract
OX App Suite publishes source for its user interface and middleware under AGPL-3.0, but the right to run specific modules, packaging and support is defined by the commercial agreement with Open-Xchange. The GitHub mirrors let your engineers read and build the open components, which helps with review and security analysis. They do not, by themselves, settle which features your contract covers or what you pay for.
- Source mirrors: The appsuite-frontend and appsuite-middleware mirrors are AGPL-3.0. If you modify and distribute those components, the AGPL obligations apply, so involve your legal team before changing code.
- Module rights: The Operations Guide states that the right to use certain modules or features may be subject to custom packaging, limitations or separate fees set in the license agreement. Each module you need should be named in the contract.
- Standard release window: A standard release is supported for 12 weeks, ending with the availability of the third following release. Plan upgrade cycles around that window.
- LTS window: An LTS release is supported until the next LTS release plus six months. v8.47 (FCS 2026-03-18) is the current LTS, and v8.35 is discontinued.
- Current release: The newest release in the support commitment is v8.53, with first customer shipment on 2026-09-23.
Ask Open-Xchange to list the modules, packaging limits and separate fees in writing, and to confirm which support windows apply to the version you will deploy. Review the Open-Xchange support commitment with the same question list.
grommunio uses a tiered model based on user count. A free Community package exists, but it carries no manufacturer support. Paid tiers are priced per user per month, and licenses are sold only through certified partners, so the partner is your counterparty for quotes, renewals and written terms.
- Community package: Free for up to 5 users, without manufacturer support. It fits a small test or a team that can handle its own support.
- Basic and Plus: Basic is 1.99 euros and Plus is 3.99 euros per user per month, with Plus applying from 6 users. Confirm the minimum user count for Basic with your partner, since the published thresholds for that tier are not stated in the same way.
- Business: 5.49 euros per user per month from 50 users. Crossing a threshold changes the per-user rate, so model your headcount growth before signing.
- Enterprise: Custom pricing from 1,000 users, set through a quote rather than a published list.
- Partner channel: Licenses are sold only through certified partners. Ask which partner handles support escalation and what happens to pricing at renewal.
Ask for a written quote at your exact user count, a statement of what each tier includes, and the support terms that apply to your package. The grommunio pricing page is the starting point for comparing the tiers you are considering.
Both vendors separate the software license from the support and services around it, and both price in ways that depend on your user count and contract scope. A fair comparison needs the same questions answered in writing for each vendor, using your actual headcount and the modules you plan to run. Without that, a list price comparison can hide the terms that drive the total cost.
- User count and tiers: Ask which tier applies at your current and projected headcount, and what happens to the per-user rate when you cross a threshold.
- Module entitlement: Ask each vendor to name the modules, features and packaging in your contract, and whether any carry separate fees or limits.
- Support and release windows: Ask which support windows apply to your version, who provides support, and what happens when your release goes out of support.
- Channel and counterparty: Confirm whether you buy direct or through a partner, and who is responsible for renewals, price changes and escalations.
- One-time and recurring costs: Separate license fees (recurring) from implementation, migration, hardening and training (usually one-time). Ask each party for a written scope that lists both.
Do not sign a comparison until both written quotes match the same user count, module list and support level. DeployOpen plans, implements and supports open-source platforms in the client's own infrastructure, and it can review the scope before implementation begins, but the license terms come from the vendor and partner.
What drives the running cost of each platform
The running cost of OX App Suite is mostly infrastructure and skilled labor, while grommunio's is mostly the partner license and the host it runs on. For OX App Suite v8, the platform is delivered as Helm charts that reference container images and expects a Kubernetes cluster that supports Istio, or an ingress-nginx fallback where Istio cannot be used. Redis 7.4.x and MariaDB are part of the stack, and persistent data such as OX Drive files and PIM attachments must sit on NFS or object storage. Each of these is a line item you pay for in cloud accounts, data centers or hardware, and each needs staff who can operate it. Open-Xchange's Operations Guide also notes that certain modules or features may carry custom packaging or separate fees set in the license agreement, so ask which of these apply to your user base before you compare totals.
For grommunio, the license is sold through certified partners by user tier, and the published pricing page lists per-user monthly rates for Basic, Plus and Business, plus custom Enterprise pricing from 1,000 users. The recurring cost therefore scales with headcount and tier, and the partner relationship determines who answers support tickets. Infrastructure is lighter on paper because grommunio ships as an openSUSE appliance or documents manual and container installs, but the Gromox server can scale out across multiple hosts, and mailbox volume drives the storage and backup footprint. One-time costs on both sides include design, the Exchange migration run, and hardening. For the migration, the exchange2grommunio.ps1 script depends on the same LDAP or Active Directory as Exchange and a writable shared folder, so budget the Exchange administrator's time as well as the import itself.
Upgrade effort is the cost most teams underestimate. OX App Suite publishes a standard release support window of 12 weeks and LTS releases supported until the next LTS plus six months, so a team that stays on standard releases must upgrade on a short cadence. Ask Open-Xchange and your grommunio partner for the support level, the upgrade assistance included in the quote, and which release line the price assumes. Request a written quote listing: scope and migration work, user tiers and growth assumptions, support level and response commitments, infrastructure you provide versus the vendor or partner provides, upgrade and backup assistance, and any module fees. Compare quotes on a three-year total of one-time and recurring items, not on the first-year license line.
Moving from Exchange or between the two platforms
The sequence below shows how an Exchange mailbox set moves to grommunio using the documented exchange2grommunio.ps1 flow, with logs that let you resume a partial run. It also shows what transfers automatically and what your team must rebuild or confirm before users are cut over.
Confirm the shared directory before anything else
Your directory administrator confirms that grommunio will authenticate against the same LDAP or Active Directory that Exchange uses. The documented migration script depends on this, so a mismatch stops the move before any data is touched. The directory owner should sign off in writing, and the platform team should record which domain controller grommunio will query. The step is done when a test user from the existing mailbox population can sign in to the grommunio test instance with their current credentials.
Prepare the Exchange management host
An Exchange administrator opens an elevated Exchange Management Shell on a Windows Server 2012 R2 or newer host. They create a shared folder that Exchange can write to and that the grommunio server can mount. Confirm permissions on both sides before the first run, because the export writes to that share and the import reads from it. The step is complete when a small test export writes a PST file to the share and the grommunio server can read the same file path.
Export a pilot set of mailboxes to PST
Using the exchange2grommunio.ps1 script, the Exchange administrator runs New-MailboxExportRequest against a small pilot group, typically a handful of non-critical accounts chosen by the business owner. Each mailbox is exported to PST in the shared folder. Review the export request status in Exchange and check that every PST file exists and has a plausible size. The step is done when the pilot exports report completion without errors in the script log.
Import the pilot over SSH into grommunio
The script pipes each PST through gromox-pff2mt into gromox-mt2exm on the grommunio server over SSH, which converts and loads mailbox content and metadata into the Gromox store. The platform engineer runs the pilot, then compares message counts, folder structure and calendar items against the source for a few mailboxes. The step is done when the pilot mailboxes open in grommunio with the expected folders and items, and any discrepancies are logged and explained.
Use the logs to run the full batch and resume
The script records successes and failures for each mailbox, so the team can rerun only the failed accounts without repeating completed ones. Work through the remaining population in waves, reviewing the failure log after each wave and resolving causes such as a missing directory object, a locked file or a share permission problem. The step is complete when the failure log is empty or every remaining exception has a documented owner and resolution.
Rebuild what the tooling does not carry
Plan to recreate client profiles, confirm how public folders are handled in your environment, and review every integration that calls Exchange, including mail-enabled applications, scanners, shared mailboxes, delegations and mobile device policies. Confirm each item with grommunio support or the documentation before cutover, rather than assuming it transfers. The step is done when a written inventory lists each integration with its owner, its new endpoint and its test result.
Validate Outlook, mobile and web clients
Test the pilot users on the Outlook versions you support, on iOS and Android through ActiveSync, and on webmail. Verify send, receive, calendar invitations, free/busy lookups, contacts and CalDAV or CardDAV sync where used. Record results per client type. Grommunio states that Outlook can stay in place through its MAPI/HTTP, EWS and ActiveSync support, so validate those specific protocols on your client versions. The step is done when each client type passes a written test script signed off by the pilot group.
Assess any later move separately
Moving onto OX App Suite, or moving off grommunio or Exchange later, is a separate assessment and is not covered by this sequence. Ask Open-Xchange for its current migration tooling, supported source platforms and the Kubernetes, Redis, MariaDB and object storage prerequisites in its requirements. Ask grommunio to confirm export formats and how its tooling handles any future exit. The step is complete when both vendors have answered in writing and the answers are attached to the project record.
Where implementation projects run long
The longest delays in an OX App Suite project usually come from the platform prerequisites, not from the suite itself. OX App Suite v8 is designed to run on a Kubernetes cluster and is delivered as Helm charts that reference container images, so the first decisions are whether the cluster meets the supported Kubernetes versions (N-1 and N-2), whether the team can run Helm 3.17.0 or newer, and whether Istio is available. Istio is the expected service mesh, with support for the latest release plus two prior versions. Where Istio cannot be used, a basic ingress-nginx option exists, and that choice changes the ingress design and the testing plan. Redis 7.4.x for caching and sessions, deployed by default through the littlered operator, and MariaDB with InnoDB (10.6.x, 10.11.x, 11.4.x or 11.8.x, with Galera Cluster supported) need owners and backup plans before the first install. Confirm these choices against the OX App Suite requirements early.
Storage design is the most common source of rework. OX Drive files and PIM attachments must sit on a distributed file system, NFS for small to mid-size deployments or object storage such as AWS S3, Ceph RadosGW or Scality RING for larger ones. Sizing these volumes from the expected tenant count and attachment growth is a decision to record in writing, because changing storage after onboarding is costly. For a hosting provider, tenant onboarding is also a project of its own: identity integration through OpenID Connect or SAML must be agreed per tenant, and the team should confirm which login flows each tenant needs. Upgrades add delay too, since a standard release is supported for 12 weeks and an LTS release until the next LTS plus six months, so the upgrade cadence belongs in the plan.
grommunio projects tend to stall on the directory and the client, not the server. The appliance (ISO or OVA with a setup wizard) or a manual or container install is quick to stand up, but the exchange2grommunio.ps1 migration requires grommunio to use the same LDAP or Active Directory as Exchange, so directory alignment must be finished before any mailbox moves. Outlook profile changes, mobile sync through grommunio-sync for iOS and Android, and CalDAV and CardDAV clients each need testing on the client versions your users run. Migration waves are usually slowed by unclear user lists, mailbox sizes that exceed the change window, and a shared folder that Exchange can write to and the grommunio server can mount. Ask DeployOpen or your team to confirm the user list, the wave plan and the window in writing. DeployOpen scopes implementation work of either platform in writing before work starts, so unknowns become named deliverables rather than open-ended effort.
What buyers ask before choosing between these two platforms
What does it cost to run Open-Xchange OX App Suite compared with grommunio?
Neither platform's total cost is set by its license alone. OX App Suite v8 is delivered as Helm charts on a Kubernetes cluster, requires Istio or a basic ingress-nginx option, and expects MariaDB, Redis 7.4.x and a distributed file system such as NFS or object storage. Open-Xchange sells the platform through its own commercial terms, and its Operations Guide notes that some modules may carry separate fees set in the license agreement. grommunio publishes per-user pricing on its pricing page, but licenses are sold only through certified partners. Ask each vendor for a written quote that lists license fees, support tier, infrastructure, implementation and recurring renewals, and confirm what the quote covers after the first year.
How long does an Exchange to grommunio migration take?
The duration depends on mailbox count, total mailbox size, network throughput and how many stages you run. grommunio's migration tooling exports each Exchange mailbox to PST with New-MailboxExportRequest, then imports it over SSH with gromox-pff2mt piped into gromox-mt2exm, and logs successes and failures so runs can resume. Those steps are sequential per mailbox, so large mailboxes and slow links extend the window. Prerequisites such as shared LDAP or Active Directory, an elevated Exchange Management Shell on Windows Server 2012 R2 or newer, and a writable shared folder also add setup time. No supplied figure gives a duration, so request a pilot run on representative mailboxes and ask the vendor or partner to estimate from those results.
Can an in-house team run OX App Suite or grommunio without outside help?
It depends on the skills you already have. OX App Suite v8 is a Kubernetes-based platform that needs Helm, Istio or ingress-nginx, a supported MariaDB version, Redis and a distributed file system, so the team needs container platform operations and storage expertise. grommunio ships as an openSUSE appliance with ISO or OVA images and a setup wizard, and also documents manual and container installation, which lowers the bar for a small Linux-focused team. Check the support model before deciding: grommunio's Community package excludes manufacturer support, and Open-Xchange's support commitment ties standard releases to a 12-week window. DeployOpen plans, implements, hardens, backs up, upgrades and supports self-hosted platforms in your infrastructure under a written, fixed scope, and ongoing support is available as a retainer.
Will Outlook clients keep working after moving from Exchange to grommunio?
grommunio states that organizations can keep their existing Microsoft Outlook clients, because its Gromox server implements RPC/HTTP (Outlook Anywhere), MAPI/HTTP and Exchange Web Services. Outlook fit still needs testing for your version of Outlook, add-ins, shared mailboxes, delegation and public folders. Mobile devices use grommunio-sync for Exchange ActiveSync, and grommunio-dav provides CalDAV and CardDAV. Ask grommunio to confirm the Outlook versions and add-in behavior you rely on, and run a pilot with a representative user group before any cutover. Open-Xchange's Outlook behavior should be confirmed with the vendor against your own client mix.
Are grommunio prices final for my number of users?
Only the tier and the written quote are final. The published pricing page lists a free Community package for up to 5 users without manufacturer support, Basic at 1.99 euros and Plus at 3.99 euros per user per month from 6 users, Business at 5.49 euros from 50 users, and custom Enterprise pricing from 1,000 users. Your user count determines which line applies, and tier boundaries mean that growing across a threshold changes the rate. Licenses are sold only through certified partners, so the partner quote may add services, taxes or currency terms. Confirm with your partner the tier, per-user rate, billing period, what happens when your count changes and whether support is included.
What does a hosting provider need to know about OX App Suite licensing?
Open-Xchange publishes OX App Suite source mirrors for appsuite-frontend and appsuite-middleware on GitHub under AGPL-3.0, but the mirrors do not define your commercial rights to the full product. The OX App Suite Operations Guide states that the right to use certain modules or features may be subject to custom packaging, limitations or separate fees set in the license agreement. Positioning is aimed at hosting providers, telcos and ISPs, with on-premises, public cloud and managed OX Cloud options. Before signing, ask for a written list of licensed modules, white-label rights, multi-tenant terms, support windows, and which LTS release you will track. Confirm all terms directly with Open-Xchange.
What infrastructure does each platform need to host?
The footprints differ in kind. OX App Suite v8 expects a Kubernetes cluster that supports N-1 and N-2 versions, Istio with the latest release and two prior versions (or ingress-nginx where Istio cannot be used), MariaDB 10.6.x, 10.11.x, 11.4.x or 11.8.x with InnoDB, Redis 7.4.x, and NFS or object storage for files and attachments. grommunio combines MariaDB for user metadata with SQLite for individual mailboxes, supports scale-out across multiple hosts through Gromox, and offers appliance, manual and container installs. Map both footprints against your existing hosting, backup and storage standards, and ask each vendor to confirm sizing for your mailbox count.
What should I check before choosing a provider-grade suite over grommunio?
Start with the operating model and the support you need. Choose OX App Suite when you need a white-label, multi-tenant platform for hosting customers and you can staff a Kubernetes-based stack, or buy that capability through a partner. Choose grommunio when you need an Exchange-compatible drop-in with native Outlook connectivity and a smaller operating footprint. Ask each vendor for its support commitment, release windows, licensing for your exact use, and a written migration plan with rollback steps. DeployOpen can plan, implement and support either platform in your infrastructure under a fixed scope agreed in writing before work starts, but it does not issue audit reports or certifications.
How DeployOpen helps you choose, implement or migrate
DeployOpen plans, implements, integrates, hardens, documents and supports self-hosted open-source platforms inside your own infrastructure, so the Open-Xchange vs grommunio decision can be tested against your real directory, mail flows and client mix before anything is committed. Engagements are scoped in writing before work starts.
How we scope
- Review your Outlook, mobile and webmail client mix and whether Exchange ActiveSync or MAPI/HTTP must be preserved.
- Confirm whether you need a white-label provider suite or an Exchange drop-in, and who will operate it.
- Agree deliverables, scope and timelines in writing; ongoing support is available as a retainer.
How we build
- Stand up a test environment that mirrors your LDAP or Active Directory integration and mail routing.
- Check the licensing and support terms of each edition against the features your users actually need.
- Test a pilot mailbox migration, including PST export and import steps, before any production cutover.
How we hand over
- Document the architecture, hosting footprint, client configuration and migration runbook for your team.
- Provide backup, upgrade and rollback procedures written for your own infrastructure and staff.
- Walk your administrators through daily operations, support contacts and the vendor support boundaries.
How we support
- Offer ongoing support, scheduled upgrades and continuous security testing as retainers after go-live.
- Track vendor release windows and plan upgrades against them, using the support terms you confirm with the vendor.
- Prepare evidence and controls for your compliance assessments, while independent auditors issue the actual reports.
